Timeout Problem

[Poetess 2]

Please create a topic in the community.

• Okay.

Describe the problem in your own words, including what you're trying to accomplish, and where you're getting stuck. Please mention some specific examples.

• The app quits suddenly, usually after only a few seconds. After a restart, it operates normally. I was trying to accomplish watching a TV show. 

In your description, be very specific about the steps you took and what happened with the system.  Describe it like you are talking to a blind person - because you are. We cannot see what you did or what happened so be as specific as possible.

• Sometimes, the app quits moments after start. Sometimes it quits moments after selection of a show page. 

If you saw error messages, please tell us what they were. If the problem is difficult to explain, please include screenshots that demonstrate the issue.

• Sometimes, there's a red message box saying something about connection failure. After it goes away, the app operates normally. 

Please attach the server log from the time frame the activity occurred. 

• Done. Error reports are near the top of the file. 

I don't know if this matters, but the problem began after a power problem that smoked the UPS for the server computer. So, the server lost power without a normal shutdown. 

embyserver.txt

[ebr 16169]

Hi.  This sounds like potentially a network issue.  What kind of signal does the device have on the network?  Local or remote?

Where (what time) in that log did the problem occur?

[Poetess 2]

26 minutes ago, ebr said:

This sounds like potentially a network issue.  What kind of signal does the device have on the network?  Local or remote?

I'm sure it's network related. The Roku uses WiFi 6 and it is on a local network. 

I just realized this could be due to our use of a range extender. We added one because of a weak signal from the access point. This improved the speed but may have introduced delays. So far, the Emby app is the only one we know of that's complaining. 

26 minutes ago, ebr said:

Where (what time) in that log did the problem occur?

This is one of the errors in the log: 

Quote

2025-10-31 00:46:51.276 Error PortMapper: Error in GetSpecificMappingAsync
    *** Error Report ***
    Version: 4.9.1.80
    Command line: C:\Users\[user-name]\AppData\Roaming\Emby-Server\system\EmbyServer.dll
    Operating system: Microsoft Windows 10.0.26200
    OS/Process: x64/x64
    Framework: .NET 8.0.20
    Runtime: C:/Users/[user-name]/AppData/Roaming/Emby-Server/system/System.Private.CoreLib.dll
    Processor count: 8
    Data path: C:\Users\[user-name]\AppData\Roaming\Emby-Server\programdata
    Application path: C:\Users\[user-name]\AppData\Roaming\Emby-Server\system
    MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (192.168.50.1:42471)
     ---> System.Net.Http.HttpRequestException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (192.168.50.1:42471)
     ---> System.Net.Sockets.SocketException (10060): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

 

[Poetess 2]

7 minutes ago, Poetess said:

I just realized this could be due to our use of a range extender. We added one because of a weak signal from the access point. This improved the speed but may have introduced delays. So far, the Emby app is the only one we know of that's complaining. 

I switched it to the access point (bypassing the range extender) to see if that makes a difference. It hasn't. 

Edited November 1, 2025 by Poetess

[speechles 2055]

3 hours ago, Poetess said:

I switched it to the access point (bypassing the range extender) to see if that makes a difference. It hasn't. 

It almost looks like the connection isn't secure (using https) and something is being upset about that fact. The Roku app can use https if you are using port 443 as the connection point and have your own certificate that isn't self generated. And handle the port redirect from 443 to your Emby port and all that jazz. The Roku will reject self signed certificates with https.

It is likely something monitoring your network. Some virus programs include firewalls and they might not be smart enough to understand that Emby isn't a problem. You may have to add rules to them to allow Emby to be left alone. Using http isn't an issue normally unless virus software starts to become agressive.

It may not be your virus/firewall and might just be from the latency on the WiFi when it causes unacceptable wait times. I would look at other causes first especially if it happens within the first few seconds of playing. If you can safely browse and it leaves you alone but when you play something it gets angry and cuts you off definitely sounds like something else getting in the way.

At what point is it failing? What is happening at that time? Video playback, just browsing, when trying to connect?

Edited November 1, 2025 by speechles

[ebr 16169]

6 hours ago, Poetess said:

This is one of the errors in the log: 

That error is unrelated to your issue.

Exactly what time in the log did you experience the problem?

[Poetess 2]

9 hours ago, speechles said:

At what point is it failing? What is happening at that time? Video playback, just browsing, when trying to connect?

It starts to play and within seconds exits Emby and returns to the Roku home screen. Then, when starting again, it runs normally. 

Also... I previously ment6ioned the range extender. I bypassed it and the problem is the same. 

[Poetess 2]

7 hours ago, ebr said:

Exactly what time in the log did you experience the problem?

The problem isn't predictable, so I'll have to note the time the next time it happens and send another copy of the log file. I understand you also need eastern time. I'll do that tomorrow. 

[Poetess 2]

14 hours ago, ebr said:

Exactly what time in the log did you experience the problem?

2025-11-02 02:23:09.946 

That's when I tried to play S01E31 of Perry Mason. The Emby client crashed shortly after the progress indicator passed 13%. I saved the log file a few minutes after the crash. 

It usually crashes at the first playback attempt and works normally after restarting the app. Sometimes it crashes when the app is first started, so it happens at other times than at playback. It also sometimes loads images on the home screen slowly or not at all. 

This is a local network only. The Roku network connection check reports 'excellent' signal strength with Internet download speed of 351 Mbps. The Emby server (192.168.50.154) has a gigabit Ethernet connection to the router (192.168.50.1) and the Roku (192.168.50.146) is connected to the router via WiFi 6. 

I haven't changed any network settings until just now when I unchecked 'Allow remote connections to this Emby Server.' I doubt I'll ever need remote connections. 

 

embyserver.txt

Edited November 2, 2025 by Poetess

[ebr 16169]

Thanks.  Nothing obvious in the server log - just the Roku disappearing after starting playback.

Go to your settings in the Roku app now and turn on "Debug Options".  Then, the next time this happens, restart the app and immediately  follow the instructions to send a log from the app.  You'll already have the debug options on so just go to the user menu and send the log.  Thanks.

 

 

[Poetess 2]

21 hours ago, speechles said:

If you can safely browse and it leaves you alone but when you play something it gets angry and cuts you off definitely sounds like something else getting in the way.

That's a good description. Just now, I added the server using the IP address instead of the name. I didn't try to do anything. It crashed from the home screen within about 15 seconds. There was no warning. 

I'm thinking this must be a network problem. Something is slowing it, but I don't know what's causing it. The router's management utility is so slow it's unusable. Apparently, Emby is the most sensitive to it. That's my best guess at this point. 

[Luke 42077]

You may want to try rebooting your router and see if that helps.

[Poetess 2]

I believe I found the problem. It was the Ethernet cable between the router and the access point. I replaced it with a new one and that cleared up the problem. By that time, I had tried several things like rebooting the router and checking space on system drive. I just got lucky when I decided to replace the cable. I thought it was Emby because that's the only app that had a problem. Everything else seems to be working better now, though. So, it's time to mark this as solved. 

Thanks for the help. 

Edited November 2, 2025 by Poetess