Remote Connection lost since upgrade to 4.9.1.80

[Ezamorano 3]

On 10/31/2025 at 2:51 PM, sa2000 said:

can you also check server settings for the user account to see that it is linked to the Emby Connect user account.

If it is linked to the email address in user settings, you could try removing the link saving the change and accepting the prompt and then adding it

you should get emails for the linking

After this, exit the emby app and relaunch and try again with sign into through emby connect

 

Already tried this. It does not work thru Emby connect or manual config.

[sa2000 674]

10 hours ago, Ezamorano said:

Already tried this. It does not work thru Emby connect or manual config.

Can you get the embyserver log files for the period when you went through those steps 

[Ezamorano 3]

On 11/9/2025 at 1:47 AM, sa2000 said:

Can you get the embyserver log files for the period when you went through those steps 

It has nothing to do with that. 

I installed the latest version, and Emby won't even start anymore. Meanwhile, Plex is working fine.

I've been using Emby for five years with almost no issues. It is no longer working. I've been providing logs, but have not recieved any support that has resolved the problems.

[sa2000 674]

4 hours ago, Ezamorano said:

I installed the latest version, and Emby won't even start anymore

If it is not starting anymore then that is different from the times for which you provided server logs - 14th and 18th October.

Maybe there is database corruption. If it is not launching anymore, you could get the contents of the logs folder directly and zip and send to me privately as the logs would not be sanitized 

The logs are in this folder

/Users/xxxxx/.config/emby-server/logs

where xxxxx being your macOS user name

4 hours ago, Ezamorano said:

It has nothing to do with that. 

Not sure why you say that. I was trying to establish if the attempt to connect to the server can be seen in the embyserver log - when we know exactly what time you did a specific connection test and can then see what is in the log. And when supplying logs best to cover the time from when the emby server was launched. If that was too long ago (logs get purged after 3 days) then best to relaunch emby server and do a test on fresh logs.

The 14th October log did show what looks like a remote connection getting through 

2025-10-14 13:51:06.712 Info SyncService-0HNGBC6JSFGHC:00000004: http/1.1 POST http://emby_remote_ip:8096/emby/Sync/data. Source Ip: emby_remote_ip, UserAgent: okhttp/4.12.0
2025-10-14 13:51:06.723 Info SyncService-0HNGBC6JSFGHC:00000004: http/1.1 Response 200 to emby_remote_ip. Time: 11ms. POST 



2025-10-14 13:58:51.890 Info SyncService-0HNGBC6JSFGIA:00000003: http/1.1 POST http://emby_remote_ip:8096/emby/Sync/data. Source Ip: emby_remote_ip, UserAgent: okhttp/4.12.0
2025-10-14 13:58:51.891 Info SyncService-0HNGBC6JSFGIA:00000003: http/1.1 Response 200 to emby_remote_ip. Time: 1ms. POST http://emby_remote_ip:8096/emby/Sync/data. 

The raw log files would have shown which remote IP address these came from

Some observations from the logs you provided already - one may be relevant:

One of the logs show both wifi and ethernet active - on IP addresses 192.168.68.51 and 192.168.68.58. The automatic port mapping for port 8096 could have been to either - it would have been random - whichever Emby Server saw first. This means that your mac needs to always have both of these interfaces active because you do not know which of the two the auto port forward was done for. Of course it is also important that these IP addresses are dhcp reserved in the router so that they do not change. If the one that has the port forward drops off then emby server would try to switch it to the remaining network interface - but we have a 1 week lease for the port forward and the router won't allow a change to the port forward to a different IP address until that 7 day period expires.

So make sure both these IP addresses are active on the mac. On windows we have a product like upnp wizard which lets you view the port forwards that are active - so you can see which local ip address has the 8096 port forward 

Other observations:

There are loads of errors logged relating to the "Iconic Image Enhancer 2.7.1.0" plugin. You could remove it and bring it back later in a controlled test

You are running with a DB Cache of 2Gb (2048 Mb) - in Emby Server 4.9.x we now have multiple db connections and having a massive cache size would not be appropriate. Suggest you switch that to the default size of 128Mb

 

[Ezamorano 3]

On 11/27/2025 at 1:56 PM, sa2000 said:

The raw log files would have shown which remote IP address these came from

Some observations from the logs you provided already - one may be relevant:

One of the logs show both wifi and ethernet active - on IP addresses 192.168.68.51 and 192.168.68.58. The automatic port mapping for port 8096 could have been to either - it would have been random - whichever Emby Server saw first. This means that your mac needs to always have both of these interfaces active because you do not know which of the two the auto port forward was done for. Of course it is also important that these IP addresses are dhcp reserved in the router so that they do not change. If the one that has the port forward drops off then emby server would try to switch it to the remaining network interface - but we have a 1 week lease for the port forward and the router won't allow a change to the port forward to a different IP address until that 7 day period expires.

Thank you. However, this is irrelevant. At the time, I was troubleshooting wifi vs. ethernet (to see if that had any effect on the Emby issues--it didn't). Normally, I have the wifi deactivated on the server machine. It has been turned off, using only ethernet, since mid-October. Since then (and before Oct 14) I use static IPs bound to the machine's ethernet MAC address. The router settings have DHCP reservations for the proper ethernet IP addresses (internal and external) and proper port forwarding. 

[Ezamorano 3]

On 11/27/2025 at 1:56 PM, sa2000 said:

Other observations:

There are loads of errors logged relating to the "Iconic Image Enhancer 2.7.1.0" plugin. You could remove it and bring it back later in a controlled test

You are running with a DB Cache of 2Gb (2048 Mb) - in Emby Server 4.9.x we now have multiple db connections and having a massive cache size would not be appropriate. Suggest you switch that to the default size of 128Mb

 

I had already disabled/reinstalled Iconic Image Enhancer. Disabling and uninstalling it had no effect on connectivity.

Okay, I changed the db case size as recommended. Will re-start everything and test again. I don't see how that would effect only external connection, however. 

I also downloaded the latest Emby build. Will also try that after restarting Emby server with recommended db cache . 

[Ezamorano 3]

On 11/27/2025 at 1:56 PM, sa2000 said:

You are running with a DB Cache of 2Gb (2048 Mb) - in Emby Server 4.9.x we now have multiple db connections and having a massive cache size would not be appropriate. Suggest you switch that to the default size of 128Mb

Okay, thank you! Changing the db cache size appears to have resolved the issue with Emby not working locally. Still couldn't connect remotely, though.

Then installing the latest build seems to have resolved the issue with remote connections.

I'll try to using ssl next.

[Luke 42077]

@Ezamoranohas that helped?