All Activity

Did it. Had to rewrite half my firewall rules. It works directly on Roku. The odd thing is every other device I have works through the proxy except the Roku devices which are on my TV's. Cell Phone remotely works fine and on local network, Laptop Works fine, Apple TV works fine, tablets work fine. As stated in my previous post almost seems like a regression somewhere.

Any thoughts or feedback so far?

@Luke Any update is this is going to be fixed? (Also the request I had sent you in PM about being able to see upcoming shows and the dates like you could in Emby For Android TV so you do not need to go to the 3 dots, then all the way to the bottom, then select up comming, just to get the list. It would be nice to have it it visible.) Thanks

Thanks, that worked

four times now I have experienced Emby For Android 3.5.44 doing occasional 3 to 5 second freezes. If I go back to the TV's home screen then back to Emby the issue disappears for awhile before starting again. embyserver.txtffmpeg-transcode-5508b0db-2c9e-468a-aa4c-816fc43cad56_1.txthardware_detection-63925141975.txt

Hello @soderlund I apologize for making your day more stressful then needed as I might not be the best tech savvy person lol! I will play with this more to hopefully not be too much of bother... and report back later and thank you.

Hi The API key you created under Advanced → API Keys is correct. The documentation refers to an older Emby UI. If both Scrob and Emby are running in Docker on your Synology, the most likely issue is the "server URL" in Scrob. If you entered localhost or 127.0.0.1, Scrob is trying to connect to itself rather than the Emby container. Try using your Synology's LAN IP instead, for example: http://192.168.X.X:8096 Alternatively, if both containers are on the same Docker network, you can use the Emby container/service name: http://emby-container-name:8096 What URL are you currently using in Scrob?

Latest update the app goes black if the network changes from WiFi to Data. So, if I’ve had it running in the background on WiFi, if I later open the app on data, all I get is a black screen. I have to force close and then it works. I’m not entirely sure it’s because of a data switch (that’s just what I’ve run into) it’s possible it’s if the app has been running in the background for a while.

Yes, but somehow this would be consistent.

4 times, not 45 times! I can't seem to edit that post.

Older posts showing this issue with Fire OS. Do these apply to the setup in question? https://uk.amazonforum.com/s/question/0D54P00007XfYtRSAV/firetv-stick-4k-wont-remember-show-progress-or-update-recent-showsapps Also asking AI gets a detailed response. Apparently this is a known issue. There might be an up to date comment, somewhere on Amazon FireOS support. I don't think this failure is that surprising with FireOS. I can imagine a built in timeout to not continue a remote data link after a certain amount of time, because perhaps something has to be stored in cache to make sure the timeline location can work and this may cause other conflicts with FireOS data traffic or cause a stuck process. So, designing in a time to forget for a remote connection might be a built in choice for FireOS. - Just a guess.

Hello rob51, ** This is an auto reply ** Please wait for someone from staff support or our members to reply to you. It's recommended to provide more info, as it explain in this thread: Thank you. Emby Team

I'm trying to decide if I want to move my Emby server install from a regular Windows install to a Docker container within Windows. The only reason would be to limit further intrusion if my Emby server were compromised from the Internet. I created a separate non-admin user and run Emby Portable as that user via a service (created with NSSM). Ideally that user will have full permissions to C:\Emby, write permissions to a transcoding temp folder, and read-only permissions to my media. The biggest issue with compartmentalizing my "EmbyServer" user with those permissions is... I cannot. Even if I only give EmbyServer read permissions to my media, it still has write permissions because of the dynamic Authenticated Users group. See attached photos. I can't just willy-nilly start removing that permission from folders (especially roots of drives) because that will break some other programs. So as it stands now, if my server is compromised, even that basic user EmbyServer can cause some damage. This can be fixed if I move to Docker, but I'd really rather not. I'm a new Emby user having come over from a decade+ of Plex. Has anyone had their Emby server compromised? If so, was it a bug or something you did or didn't do with your home firewall? ----------------------- Further info: I front Emby app with pfSense. I use my own domain and SSL is managed with ACME. Emby is piped through a reverse proxy haproxy with very curated permissions. Requests have to match my https://embyserver.mydomain.com exactly, or they are denied. Run it on a high port If any IP tries to login more than 45 times in a few minutes, I block them. Prevent long URL path hunting and more

I vote against it... Now I'm CONSTANTLY changing it because I do lots of playlist type double features and constantly testing and this is no good. To me it's like some programing ethics or the beginning of commercialized junk. Users should have control, and the option to change it should be right on the choices such as SUGGESTIONS, FOLDERS etc ... maybe you right click it on and choose default. When you realized the option to change a setting is cumbersome, you fix it instead of eliminating it.

Christian Kane(I) is the current imdb name for this actor. There is also a Christian Kane(III), but not a (II) (2). Imdb is also listing identical actor names with talent from earlier years, who have passed by adding their brith and death dates. John Smith(1931-1995) Maybe the actor look up code needs to be tweaked to work with these changes at imdb and other sites. Just a guess.

Short, Did you notice the media that is already on the server is listed as media poster right above on the actor page? I understand you might like have a link in the text list, but you are showing info that is already listed on the page. That is a bad practice choice. It complicates the page with additional code, which makes the page load a little slwer, strains the server to process the links and is another feature that can break and need dev time to fix. Everytime some member opens an actor's page, this extra processing drags the speed down of the server. These reasons are why it is a better practice to process info only once for any query per page.

It just happened again (I've not been using the standard version), nothing in the logs showing any issue, just corrupt video output. Closed the app and went back in, worked fine.

Also I clicked on an item in the spotlight. then pressed the back button to return to the home screen, and got this: 2026-09-16 23.03.18_avc.mp4.mp4

Sorry..for me it still did the same thing after 5 mins it went to Screensaver and then the show started to play again in the background.

I'm seeing the same thing, but with a translucent backdrop for the first spotlight item over the top of everything.

@ebrNo I use a Zidoo. I think the change you made in version 2.1.55 works perfectly, except when the video is in stereo. What do you want me to do ?

May I ask where? Do you have a link?

But you could create whichever rows you want for whichever libraries you want. Therefore, you could make it be just like Latest. You could also utilize the plugin that changes your added dates to the release dates if you really wanted to. However, don't your user's care when new media is added - even if it isn't "new" it is new to your server. Won't they want to know that you finally added that 4K cut of "The Godfather"...? I also see now that you are setting this up in an unsupported way. Not sure if that is relevant but probably.

Thank you. Will try the install and see what happens.

All your logs are empty. I've never seen that before. Do you have a custom ROM on your device or something?