Option to disable automatic server discovery

[ng4ever 39]

Just now, Happy2Play said:

Only guess on failed connection is maybe device cached info.  If you remove the server are you able to readd it and connect?

No.

[ng4ever 39]

This is on my iPad

[Happy2Play 9449]

All I can say is on my iPhone I delete all servers, disabled WiFi and added the server via WAN address with discovery port 7359 disabled without issue.  So can only guess device cached info.

[ng4ever 39]

Just now, Happy2Play said:

All I can say is on my iPhone I delete all servers, disabled WiFi and added the server via WAN address with discovery port 7359 disabled without issue.  So can only guess device cached info.

 

Ok.

 

Guess it was not meant to be. It is ok though. I will figure out something

 

Maybe just use Jellyfin for me. idk.

 

[ng4ever 39]

Never mind I think I got it had to change local and remote port for it to work. (To connect)

 

Weird.

[ng4ever 39]

On 8/29/2022 at 11:42 PM, Happy2Play said:

Pretty sure is the only way is blocking the UDP port right now as it should already exist in your firewall rules.

Example from Windows

 

Sorry but how would this work or be possible if I wanted to block/disable automatic server discovery with two Synology Emby servers instead ? With only doing it to one of them.

Is it possible?

If so how?

 

 

 

[Luke 40121]

8 hours ago, ng4ever said:

 

Sorry but how would this work or be possible if I wanted to block/disable automatic server discovery with two Synology Emby servers instead ? With only doing it to one of them.

Is it possible?

If so how?

 

 

 

What are you trying to accomplish?

[ng4ever 39]

1 hour ago, Luke said:

What are you trying to accomplish?

To completely hide one synology Emby server unless you manually enter the details to add it.

Edited June 9, 2024 by ng4ever

[Clackdor 92]

Adding my vote for this feature as my request was a duplicate.

My personal use case is to run multiple emby instances on the same server while only advertising one or some of them locally. I only have one or two emby instances that I allow local http access. The others go through a reverse proxy and are located on the same windows machine.

Currently since port 7359 is open for the main emby instances (and there is no way to turn off the emby itself on this port), all emby instances on that machine will show up to clients on the same subnet, even if the http/s ports aren't actually open.

Windows firewall makes it possible to block the connection at the OS level, but it's probably more convoluted on other platforms to do the same. 

Effectively I think a toggle to disable emby advertising itself on the network via this port would be useful in quite a few situations/configurations outside of my own.

Id image people who access their server exclusively through a reverse proxy would also want to enable this too since the proxy only needs to communicate with emby's local http/s ports.