Remote Connections not working with Emby 4.10.0.40 Server Update

[Bradum 15]

Hello,

I have my users configured through Emby Connect, and up until recently have been able to connect remotely to the server without issues. Immediately after my server updated itself to version 4.10.0.40 it was no longer possible to connect remotely to the server. The server shouldn't be going through my VPN (I have split tunneling turned on where it will only include programs I select), but just in case I tried turning my VPN off entirely and still no dice. No other changes were made to the server or VPN, it just stopped working exactly when the update happened. Any idea what might be going on?

[Luke 43099]

Hi there, what exactly happens when you try to connect?

[Bradum 15]

Hi Luke, thanks for the quick response!

When I start up Emby remotely it tries to connect to the server, then boots me back to the "select a server" screen. If I click on the server from the "last used" option I get the "Unable to reach <server>" message. If I try and use Emby Connect it will prompt me to sign in, then just send me back to the select server screen. The server doesn't show any attempted connections.

Edited Saturday at 01:03 PM by Bradum

[Aldursil 17]

I had a similar issue though I am not sure it's the same. Someone suggested I go into the Admin > Devices page and then remove the device from the list that was not able to connect.

Once I did this I was able to re-authenticate and connect to my server again.

Maybe try this and see if it helps?

[ebr 16708]

Hi.  It is possible that during the update process your IP address changed.  Can you confirm the address on the dashboard is correct?

[Bradum 15]

3 hours ago, ebr said:

Hi.  It is possible that during the update process your IP address changed.  Can you confirm the address on the dashboard is correct?

Just confirmed the IP shown in Emby Server is the same as my actual IP.

[ebr 16708]

On 9/12/2026 at 9:00 AM, Bradum said:

The server doesn't show any attempted connections.

This is the major clue that something in your network environment has changed.  Public IP, port forwarding, firewall rules, router security software... etc.

[Bradum 15]

4 hours ago, ebr said:

This is the major clue that something in your network environment has changed.  Public IP, port forwarding, firewall rules, router security software... etc.

It happened immediately after the update (they finished the episode they had buffered, and was unable to connect to the server). I am certain there were no changes to the network at that time; no internet reconnects or router/network settings changed. I can't think of any reason why my public IP or ports would have suddenly changed on their own while still connected.

Edited 39 minutes ago by Bradum

[Luke 43099]

When the VPN is on vs when it is off, wouldn't that require a different remote address to be used?

[Bradum 15]

10 minutes ago, Luke said:

When the VPN is on vs when it is off, wouldn't that require a different remote address to be used?

Emby server is not going through the VPN. I have split tunneling enabled in "include" mode which means only applications I select go through the VPN. Several days after the fact I turned the VPN off to confirm it did not affect my public IP for Emby Server, and that it wasn't causing issues in some unexpected way. They are unable to connect with the VPN on or off. Also, no VPN settings were changed when the issue occurred; they were able to connect and watch episodes while the VPN was on, and when the update occurred they were suddenly unable to load the next episode or reconnect to the server.

The VPN is running locally on my machine, not network wide or configured through the router.

I am also able to confirm that my public IP matches what Emby Server is showing an it is not possible to connect to the server remotely.

Edited 29 minutes ago by Bradum