All Activity

Bad actors. This is why we cannot have nice things. Because people can fake their server credentials. You may not remember. In the years before Emby was 100% open source. But because of costs of implementating things rose it became necessary to close source and monetize certain features. Emby went closed source to keep the project going in the current direction. These other guys first created an Emby-unlocked branch. The unlocked branch would spoof active premiere licenses and try to fake official Emby apps into validating with the spoofed credentials. It became necessary for the apps to also check the validity of the premiere key that the Emby server it is connected to actually exists. Then no longer could the Emby-unlocked branch exist. It was pointless. The official Emby apps were now onto them and denied their spoofed server. They had to move. So they renamed it to JellyFin and started to claim the reason their branch existed was to keep it open source. When really it was created to allow pirate servers to have an unlimited amount of applications/clients/devices that could play from their unlocked-Emby server. So pretty much you can blame JellyFin why your LG Emby app must validate the credentials directly rather than trust the servers own determination.

Hi. I split this out to its own topic. Thanks.

That's strange. Will look into it. Possible for you to grab a log ?

I have now made a simple test, and it seems to be working without issues on the beta. I have NOT tested all functionality, but i don't see any reason why it shouldn't work.

HI there, what makes you think you made it worse?

There was an issue with our release notes automation yesterday but I'll put a new build up today.

Installed, restarted Emby, but now Emby isn't coming back online, when I press run on my Synology NAS, after a few moments it says Manually Stopped ...

2026-09-08 07:02:27.786 Info Server-0HNOCNNMM76IL:00000001: http/1.1 Response 404 to host20. Time: 0ms. GET http://host3/RDWeb. 2026-09-08 07:02:31.028 Info Server-0HNOCNNMM76IO:00000001: http/1.1 Response 404 to host20. Time: 0ms. GET http://host3/Remote. 2026-09-08 07:02:32.100 Info Server-0HNOCNNMM76IP:00000001: http/1.1 Response 404 to host20. Time: 0ms. GET http://host3/RDWeb/Pages/en-US/login.aspx. 2026-09-08 07:02:46.305 Info Server-0HNOCNNMM76IR:00000001: http/1.1 Response 404 to host21. Time: 0ms. POST http://host3/wsman. 2026-09-08 07:04:06.867 Info Server-0HNOCNNMM76J1:00000001: http/1.1 GET http://host3/api/sonicos/auth. Source Ip: host22, Host=115.70.108.233, User-Agent=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36, Accept-Encoding=gzip, X-Real-IP=74.207.240.7, X-Forwarded-For=74.207.240.7 2026-09-08 07:07:17.412 Info Server-0HNOCNNMM76J9:00000001: http/1.1 Response 404 to host23. Time: 0ms. GET http://host3/+CSCOT+/oem-customization?app=AnyConnect&type=oem&platform=..&resource-type=..&name=+CSCOE+/portal_inc.lua. 2026-09-08 07:07:44.435 Info SyncService-0HNOCNNMM76JB:00000002: http/1.1 POST http://192.168.0.2:8096/Sync/Data?TargetId=116f23d7-a0de-6360-ea5c-6686e8076f78. Source Ip: host1, UserAgent: EmbyMedia.13848C33ED80B/2.322.2.0 2026-09-08 07:07:44.435 Info SyncService-0HNOCNNMM76JB:00000002: http/1.1 Response 200 to host1. Time: 1ms. POST http://192.168.0.2:8096/Sync/Data?TargetId=116f23d7-a0de-6360-ea5c-6686e8076f78. 2026-09-08 07:08:01.248 Info Server-0HNOCNNMM76JC:00000001: http/1.1 Response 404 to host23. Time: 0ms. GET http://host3/.env. 2026-09-08 07:08:46.035 Info Server-0HNOCNNMM76JD:00000001: http/1.1 Response 404 to host23. Time: 0ms. GET http://host3/.ftpconfig. 2026-09-08 07:09:27.432 Info Server-0HNOCNNMM76JE:00000001: http/1.1 Response 404 to host23. Time: 0ms. GET http://host3/.git/config. 2026-09-08 07:10:07.256 Info Server-0HNOCNNMM76JF:00000001: http/1.1 Response 404 to host23. Time: 0ms. GET http://host3/.idea/WebServers.xml. 2026-09-08 07:10:52.461 Info Server-0HNOCNNMM76JG:00000001: http/1.1 Response 404 to host23. Time: 0ms. GET http://host3/.remote-sync.json. 2026-09-08 07:11:36.450 Info Server-0HNOCNNMM76JH:00000001: http/1.1 Response 404 to host23. Time: 0ms. GET http://host3/.vscode/ftp-sync.json. 2026-09-08 07:12:13.134 Info Server-0HNOCNNMM76JI:00000001: http/1.1 Response 404 to host23. Time: 0ms. GET http://host3/.vscode/sftp.json. They were throwing everything but the kitchen sink at you. Trying to exfiltrate data too. Not just hack but entirely pwn.

Hello folks, long time Synology NAS installed base, old DS-418 play unit, completely up-to-date, DSM-wise. Also Emby up to date with premiere from a few years ago, I was trying to fix an HTTPS issue fiddling with the DSM reverse proxy to fully publish Emby to the internet to share it with some friends and I think I made it worse, now I can only use Emby local within my LAN. At least before the changes, I could use it via the app on my android phone, but not anymore now. How can I start to ask for help?

As i thought.. I uploaded another version to the catalog v5.60.0.5. That should work correctly.

embyserver.txt

Link works but issue is still there. I need to spam play button several times until after a few min I get tons of "get premier" pop ups so that I can then start a playback

Having this exact same issue -- glad you guys are on it (and thanks for the workaround suggestion below).

2026-09-08 07:00:47.861 Info Server-0HNOCNNMM76IC:00000001: http/1.1 Response 404 to host17. Time: 0ms. GET http://host3/version. 2026-09-08 07:00:48.958 Info Server-0HNOCNNMM76ID:00000001: http/1.1 Response 404 to host17. Time: 6ms. GET http://host3/api/v1/pods. 2026-09-08 07:01:46.528 Info Server-0HNOCNNMM76IG:00000001: http/1.1 POST http://host3/v1/statement. Source Ip: host18, UserAgent: python-urllib3/2.7.0 2026-09-08 07:01:46.529 Info Server-0HNOCNNMM76IG:00000001: http/1.1 Response 404 to host18. Time: 1ms. POST http://host3/v1/statement. 2026-09-08 07:02:09.291 Info Server-0HNOCNNMM76IH:00000001: http/1.1 Response 404 to host19. Time: 0ms. GET http://host3/dana-na/nc/nc_gina_ver.txt. 2026-09-08 07:02:10.235 Info Server-0HNOCNNMM76II:00000001: http/1.1 Response 404 to host19. Time: 0ms. GET http://host3/dana-cached/hc/HostCheckerInstaller.osx. 2026-09-08 07:02:11.264 Info Server-0HNOCNNMM76IJ:00000001: http/1.1 GET http://host3/dana-na/auth/url_default/welcome.cgi. Source Ip: host19, Host=115.70.108.233, User-Agent=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) It is this. Somebody is trying to hack you hoping you are running a reverse proxy, vpn, or something and take control. They are trying to run exploits against your server. It isn't coming from Emby but being shoveled down Emby's port you have opened facing the internet. It doesn't look like they can do anything. But they can likely send "casting" commands and cause incorrect media to play and other shenanigans. If they gain access to your correct user with admin they can delete things. The IP shown on the one sending the welcome.cgi appears to be from Superloop (Australia) Pty Ltd. Find the corresponding IP to match Host3 in your unsantized logs. You will have the offending IP. Ban it. Ban its subnet.

@ebrWhere are we at with this? I see someone has downloaded the server logs, but you haven't downloaded the DM'd app logs, so I'm not sure where we stand.

@LukeWhy has there been an update with no thread or update notes?

You're right @ebr. It's "Emby for Android" on an Android TV.

Please give me a log of Emby trying to start with embyicons installed. I just fixed a problem in EmbyCredits that might be the same thing wrong here, i just want to be sure about the issue.

No problem.

It's ok now, thank you

Thank you for your contribution on this, I would desperately want this fixed and its refreshing to see someone more technical put so much effort into helping do so. Hopefully @Lukecan get this fixed soon. Coming up to one year with this feature being broken sadly!

Well, that's interesting, because this is an indication for the problem not even being on the Emby side! It's a problem with your setup and/or hardware in some way. We can help narrowing it down if you wish.

Try version 2.9.0.5 beta in the catalog.

Hi. That's not Emby for Android TV. That is Emby for Android. Until this is addressed in that app, you could try installing "Emby for Android TV" from the store.

Try shutting down the server and removing device.txt again. This will cause you to need to re-connect any Connect accounts.