The dreaded "This site can’t be reached"

[wilcoson 1]

After removing prior docker container and creating a new one, I can't log in locally. I have 2 emby instances running at home on 2 different servers so I had to use a custom port 8097/8921 for this one. Haven't had issues before but now I can't log in. I've disabled my server fw to no avail. Tried restarting server, different installs, etc. All come back with same error message. Logs attached but don't really show much. I'm at a loss.

Thanks,

Mike

_emby_logs.txt

[wilcoson 1]

embyserver.txt

[wilcoson 1]

I note that my router keeps showing the following port forwarding rule that I didn't request:

UPnP     IGD    8096   TCP  192.168.1.68   8096   Always

[wilcoson 1]

Well, I rebooted my router and the port forwarding rule disappeared but I still can't log on. Note: The page loads if I use default port 8096 but it walks me thru setting up as a new instance, so something's not right.

[Luke 42231]

hi, did you configure the public router port number in emby server network settings?

[wilcoson 1]

7 hours ago, Luke said:

hi, did you configure the public router port number in emby server network settings?

Hello, I believe that was set some time ago, before I lost access, that is. I've had this running for several years until re-creating a new container.

[wilcoson 1]

Hello, I figured it out by editing the default ports in the config/system.xml file and restarting server. Thought I had tried that already but was unsuccessful, hence the post. Maybe I didn't do it right the first time, dunno. Thanks tho