Playing with HTTP ports

[dcruff 15]

I'm trying to go online with a new Emby Server hosted on Unraid.  Everything is set up but I wanted to leave my legacy Windows server up until everyone was switched over.  I seem to get everything working and then it isn't any more.  I'd like it to be relatively seamless for my clients (family and friends).  I've played with the HTTP ports and changed the ports on my legacy Windows Emby server to 8097 and set my new Unraid Emby server to 8096. I made the changes to both the Local http port number as well as Public http port number.  Do I need to change the https port address (8920) also to make them different?  Once I make the change, does it take time to propagate?  DNS servers and or Emby data bases?  Again, I'd like to be able to use the Emby app on all of the clients instead of instructing them to key in an IP address.

 

Now I have none of them accessible, either by directly keying in their IP address (24.11.34.107:8096) or through the Emby app on my android phone.  I've tried selecting the specific server listed in the app as well as 'Add Server' and keying in the IP address and port.  All I get is errors: Connection Failure

When using my Rocku and my Apple TV on my Wifi, they get right in to my new Unraid Server using the respective apps.

Edited January 21, 2022 by dcruff

[Happy2Play 9780]

Sounds like you did not change your router port forwarding so correct ports are forwarded to correct ip.

Have you verified a site like canyouseeme.org shows Emby ports open?

[Q-Droid 989]

DNS records can take some time to propagate. Ports are not part of that and changes are immediate.

Map it out on paper then plug the values in your router and Emby Network settings. DNS can be the same, WAN IP can be the same, public port has to be different between servers and can match the local port on its server, usually does. Remember to include the External domain name in the Emby settings.

DNS -> WAN IP <--> WAN IP:port (router forwarded to) <--> LAN IP:port (emby1 https)
- In Emby server Network     ^public port number                                ^local port number

DNS -> WAN IP <--> WAN IP:port (router forwarded to) <--> LAN IP:port (emby2 https)
- In Emby server Network     ^public port number                                ^local port number

IF you're also allowing HTTP (probably shouldn't) then do the same for the HTTP ports.
 

[Carlo 4561]

Hi, what's the overall objective?

Do you want to have them both online at the same time?

Are you planning on switching/flipping them so the new server becomes the default server everyone uses?

Are you using Emby Connect for any users?