Inquiry regarding the client-side automatic server IP and port recognition feature.

[sunmagic 2]

Here is my situation: I have a proxy server at 192.168.0.3:8085 and an Emby server at 192.168.0.3:8096. Currently, when I add 192.168.0.3:8095 in the client, it automatically detects and switches to 192.168.0.3:8096 upon the next login, which is not what I intend.
Therefore, I would like to ask if it is possible to configure the client to prevent it from automatically detecting the IP and port, or if the server can be customized to avoid this behavior.

Thank you for your assistance.

[ebr 16445]

Hi.  You can already configure this in the server settings:

[sunmagic 2]

Thank you for your reply.

I have tried this configuration. Changing the port here directly replaces the service port. For example, if I set it to 8098, the client will also detect 8098 and automatically change to 8098, instead of the 8095 I want.

[ebr 16445]

9 minutes ago, sunmagic said:

if I set it to 8098, the client will also detect 8098 and automatically change to 8098, instead of the 8095 I want.

If you want 8095 then that's what you would set it to...

[sunmagic 2]

Port 8095 is already bound to the proxy server.

[Neminem 1742]

48 minutes ago, sunmagic said:

Port 8095 is already bound to the proxy server.

Change that You should be able to change that in the config of you Reverse proxy.

[ebr 16445]

Sorry, this is what you want to set to 8095.

[Luke 42580]

@sunmagicI think what you're looking for is the ability to use a different address from a different device, so you need to be able to enter it manually and then prevent the app from getting updated address info from the server, right?

[sunmagic 2]

@LukeYes, that's exactly what I wanted to ask. I manually set the proxy IP and port before, but the app would automatically overwrite them with the updated address fetched from the server.

Edited June 11 by sunmagic

[Luke 42580]

OK this has come up increasingly lately so it's certainly a possibility.

[Clackdor 110]

On 12/14/2025 at 2:04 PM, sunmagic said:

Here is my situation: I have a proxy server at 192.168.0.3:8085 and an Emby server at 192.168.0.3:8096. Currently, when I add 192.168.0.3:8095 in the client, it automatically detects and switches to 192.168.0.3:8096 upon the next login, which is not what I intend.
Therefore, I would like to ask if it is possible to configure the client to prevent it from automatically detecting the IP and port, or if the server can be customized to avoid this behavior.

This happens because the emby server is advertising it's local HTTP IP:port to clients, and clients seem to always favor this for local connections.

On 6/16/2026 at 12:57 PM, Luke said:

OK this has come up increasingly lately so it's certainly a possibility.

Does this mean that we will finally be getting the option to fully customize the IP or domain that the emby server advertises to devices on the local network via the discovery service? If so that should allow admins to force HTTPS connections for local apps too. HTTP connections should only ever be needed for local DLNA devices that require it assuming everything is setup correctly. A large number of people use their domain internally with a local DNS server or hairpin NAT as well as mixed internal/external reverse proxies. 

It would be nice to not have to choose between forcing HTTPS connections by blocking ports on the server (assuming the OS & network environment even allows for it) & simpler local device setup via the built-in discovery service.