All Activity

I think that is coincidental because in your provided log example, no nfo files were written during that time.

OK please run a library scan and then attach the emby server log. Thanks.

Hi, yes it does.

http(s)://app.emby.media

@LukeYou may be right, but every now and then another pops up, and now it is happening here and there in TV Series. Not sure what you mean by 'already queued' but can't see after all this time a 'queued' image is getting created. Which begs the question, how do you kill the queue?

Can you please clarify what you mean by the hosted web interface? I access my server via the web and see this issue, so not 100% sure what you mean.

OK - let have one example of a drive path that changed and the media is now elsewhere and that you have removed that old folder path from the library definition and did a scan after that. Would like to know which library, which folder path and which media file still trying to use the old path and a server log covering the time of this happening

Thanks We can ignore everything before you deleted and re-added season 15 - because the test was to see what happens when you add the season The provided log covers the time period from midnight on the 16th March to 17:37:11. The log shows: At 17:27 Season 15 was removed At 17:30 Season 15 was re-added At 17:32:28 intro markers were available from the server The only evidence of any playback for call the midwife was prior to all this - at 17:08 using Emby for Kodi Next Gen/KodiPi to play S15 E07 and E08. As we have no evidence/logs for the time the episodes were added/scanned before 17:08, we need to concentrate on what happened after you removed and addedd season 15 and the logs show that the markers were created and in place by 17:32:28 and provided you did a fresh launch of a client app after this, then the markers should be present The server runs at GMT-4 and your post with the log shows me a time of posting as 21:39 GMT which would be 17:39 your time. The emby server log was captured just after 17:37. So should be ok. What happened in the previous scan of Season 15 we don't know but with this new scan after removal and adding the season, it appears to be ok

I think you are all talking against each other. All hes asking is for a way to not have to have the webpage running when using the apps anyway. I soooooort of a agree, having a website running that you don't need or want is just a security risk no matter how well made. Not having the site would at least hide it better from unwanted guests. I don't think we need the ability to turn it off though.

the 32700 to 32700 in the support article example was for the case when they were both routers and on the 2nd router you forward 32700 to 8096 You said you made the deco access point - so the network and DHCP is now served by the eero, If you want to use 32700 as the public port, on the eero you forward 32700 to 8096 for the the emby server local IP address - because the deco is now just an extension to the existing eero network Does the eero port forward allow you to have a different public port from the local port i.e. 32700 to 8096 or does it only allow the same port number? if it has to be the same, then you should go back to forwarding 8096 to 8096 on the eero to the local IP of the emby server - assuming you are keeping the deco operating as an Access Point

Does the ldap plugin still work with the current emby server version

I think it depends if you care more for the room aesthetics or if it’s the audio setup and hobby part you’re interested in. Also are you able to place speakers in your ceiling for Atmos? This is only advice from my experience but when budgeting I would spend the most on the subwoofer, next the AVR amp, the front stage and finally the rear surrounds and atmos speakers. I’m sure others have a different idea but this is what I think. For most people this is quite difficult to achieve starting out so you have to make compromises and do this in stages. But what I wouldn’t compromise on is the AVR amp. Choose one which has the connections you need, with some future proofing with speaker connections (5 bed layer, 4/6 atmos, multiple subs, pre-outs). The amp should be good for at least 5-7 years so with that in mind buy some speakers second hand for now. Or just use what you already have and build it up.

This is a known bug in this version; it is fixed in the hosted web interface, so you can use that meanwhile. Paul

The apps use HTML as well - you want them to work, right?. So what on earth are you worrying about? Paul

Since the update to 4.10.0.6, I have noticed a behaviour (which is hard to screenshot) that if I edit a Home Screen section, the 'View Type' is empty/blank in the drop-down menu. I have restarted the server, but the behaviour persists. I have attached a screenshot, but like I said, it doesn't quite show the output, but I am sure you will understand what I mean. Happy to post logs if required, but it's not a reproducible issue at a specific point in time; it's persistent.

You should be more concerned about opening a port without SSL than admin features that no one can even access anyway.

it was posted herein the emby forums a wee or so ago, then it disappeared - it can be found at https://github.com/firestaerter3/emby-xtream?tab=readme-ov-file - not sure if the mods removed it from here or the developer did. There's a sub-reddit regarding it too, which appears to have gone a bit quiet. Last update on the plugin was 14 March 26

I already had the deco system when I upgraded the internet to ont, it came with eero. We have a lot of devices. It works. I tried the steps. On the deco, I made it an Access Point and enabled Smart DHCP. On the eero interface, I port forwarded the deco with 32700-32700, previously I had 8096-8096. As of now, it does not work remotely, still.

Again, the administrative features are not confined to any particular interface. Then none of them have access to the admin features and you have no issue to try to resolve here. It's a part of your server. Whether you access it or not.

Why? The Eero is also a mesh system.

Okay, actively trying the process now.

It's an eero Max 7, they refer to it as a modem/router. Along with it, I have a deco mesh system.

ribtherobot@RIB:~$ ls -lah "/mnt/hde4TB_4/Filme/Animações/[2025] Zootopia 2" total 6,7G drwxrwxrwx 1 1000 1000 0 mar 17 16:23 . drwxrwxrwx 1 1000 1000 68K mar 17 16:23 .. -rwxrwxrwx 1 1000 1000 6,7G mar 17 16:26 '[2025] Zootopia 2.mkv' ribtherobot@RIB:~$ namei -l "/mnt/hde4TB_4/Filme/Animações/[2025] Zootopia 2/[2025] Zootopia 2.mkv" f: /mnt/hde4TB_4/Filme/Animações/[2025] Zootopia 2/[2025] Zootopia 2.mkv drwxr-xr-x root root / drwxrwsrwx ribtherobot ribtherobot mnt drwxrwxrwx 1000 1000 hde4TB_4 drwxrwxrwx 1000 1000 Filme drwxrwxrwx 1000 1000 Animações drwxrwxrwx 1000 1000 [2025] Zootopia 2 -rwxrwxrwx 1000 1000 [2025] Zootopia 2.mkv ribtherobot@RIB:~$

Thanks, I'll take a look in the next day or two

I am reading everything If HTML access is not a thing and is not needed, why can we not disable the HTML interface? What is the point of having it running if not needed. For example if I setup a Apache server, and by default its listening on port 80 (http) but my site only uses https (port 443) so the correct thing to do is to disable port 80, there is no reason to have it listening on port 80. None of my users have admin access The point is, why do I have to expose to the internet the HTML web interface (which includes the Admin Dashboard because its not separated on its own port) when 100% of my users are using the apps. If 100% of my users are using apps, there is no reason to have the HTML web interface available just sitting there waiting