All Activity

How would I manage to get that happening, when I don't know when this may occur next ?

Well, this is not a solution. Not for everyone. Personally I don't like 3rd-party apps.

I think a debug log is the best next step.

I have started re-assessing plugin needs anyway - first one autobox sets - failure - so that is being removed -

FYI - I am happy to kill all api keys and reset those apps, plus I am happy to kill all manually added plugins for a fresh system, I was just looking at an order of which is more likely to be the culprit.

As to what happens when it stops working, the first time, I got calls from a few friends, but as I was away, I just did a remote restart. The second time I was watching it myself and just got the spinning disk, and then calls from others, and EVEN the Emby console was not responding - refresh in the browser and timeouts. I again restarted the docker container and all good again. I just checked the jellyseer logs and it is going to do a full Emby sync in 15 hours - I will be in bed then. I don't think it's that as it runs every 24 hours and this issue was at 7:10PM. To rule it out however, I just kicked off a manual full Emby sync. Checked Emby logs and processes - no impact and little log activity. With regards to external access - I have check log files for the same timeframe for jellystat, seerr, Nothing else does any sort of sync. My API keys are thus - Any idea what order, or what below may be the culprit for removal from the plugins -

I definitely have a VegaOS device. I'm running Emby on all my FireTV devices. It's just this new one that was having a problem. No worries, though, I'm able to see my server now using Astra.

3.5.58 Fix When "autoplay next episode" is off, the app still prevents screen from going off Core UI Changes from 26.0.23 to 26.0.25 Various spotlight fixes for older devices General slideshow fixes Support mousewheel for horizontal sections in TV display mode Improve spotlight design Fix text not visible in screensavers

Emby for Android 3.5.58 Released Changes 3.5.58 Fix When "autoplay next episode" is off, the app still prevents screen from going off Core UI Changes from 26.0.23 to 26.0.25 Various spotlight fixes for older devices General slideshow fixes Support mousewheel for horizontal sections in TV display mode Improve spotlight design Fix text not visible in screensavers

Hi, can you please try 3.5.58+ and let us know how that compares? Thanks !

Hi, can you please try 3.5.58+ and let us know how that compares? Thanks !

Hi, can you please try 3.5.58+ and let us know how that compares? Thanks !

Hi there, please attach the complete emby server log file. thanks.

Thanks for following up.

Please ignore this. Problem solved: DNS error! Cheers, John

Per the attached log file, I tried searching the guide for shows containing the word "Task" which fails to generate any results. A couple minutes later the port mapper generates an error, after which my search for "Task" suddenly works and generates some results. embyserver_2026-09-15.txt

26.0.25 Various spotlight fixes for older devices General slideshow fixes Support mousewheel for horizontal sections in TV display mode

Emby Web App Update: Version 26.0.25 The Emby Web app has been updated to version 26.0.25 Go and try out: https://app.emby.media/ Changes 26.0.25 Various spotlight fixes for older devices General slideshow fixes Support mousewheel for horizontal sections in TV display mode

@nospotifyhas this helped?

Hi, this is on our to do list. Thanks.

Yikes released this to main branch? Man

That's not a Vega device... But we are definitely in the normal Fire OS app store - twice, in fact. What part of the world?

Thought it might be useful (or not) to be able to add some form of note to the above, so if there's an address or three I can say somehow which address belongs to which user. Maybe a separate row of ID's per address, or a way to have in the filter stuff in quotes, as in "Colin='131.294.265.265, or something.

OK, are you trying to connect to your own Emby Server, or someone else's server?

If you can get it to happen again with debug logging enabled then that may tell us more.