Emby Connect - We're unable to connect to the selected server error

[moriandrizzt 1]

I was on one of the versions 4.7.x.x before upgrading to 4.8.8.0 and since then my emby connect has been throwing me the error "We're unable to connect to the selected server right now. Please ensure it is running and try again." I upgraded to a beta version 4.9.0.30 this morning to see if it would make a difference and it is still throwing this same error. I have tried removing the emby connect from my account on the server and re-adding it. I've also rebooted. I was originally running this on ubuntu 18.04 Gnome and now am using Mint Cinnamon (I forget the version but should be the latest).  Everything was fine up until I upgraded emby this past Monday to 4.8.8.0. Almost forgot to mention that It is detecting my public ip just fine in emby.

I'd like to downgrade to version 4.7.x.x but I can't find a download link for debian. I usually keep my debian files but somehow I've misplaced the last one.

Thanks in advance!

[moriandrizzt 1]

Forgot to add that I'm only having the issue through emby connect. I have zero issues with local connections on my LAN from my android, roku, or browser. I have tested and verified that it's not that https vs http issue. I've dealt with that in the past and have tested for that in the web browser on a computer outside my network.

[moriandrizzt 1]

Last night I uninstalled and reinstalled all of the various versions from 4.7 to 4.9 that are available. It is still not able to be seen from outside of my network and works fine internally. I'm wondering if there is an update the mint pushed that messed up the firewall.

[moriandrizzt 1]

Looks like my router needed the IP forwarded. This seems like a no brainer but let me explain. I have had this server in my basement for over 4 years. I have had the Mac address reserved in DHCP all of this time. I have had the port forwarded to the local IP all this time. I have not touched that. I found that my server still has the same IP address I've been using for the past 4 years. The weird part is that I've been able to remotely connect until sometime in the past week or two. I'm realizing I cannot reliably say when it stopped but I do know I have used it within the last month. Sigh. I have no idea how my server can get a MAC address that is completely different than what I have reserved in DHCP. Either way I'm glad it wasn't a software issue and I still feel quite dumb. Thanks for listening to me figure this out on my own. Haha. 

Edited September 7, 2024 by moriandrizzt
Spelling due to bad autocorrect

[Luke 42077]

Thanks for following up !