We're unable to connect to the selected server right now. Please ensure it is running ad try again

[electricwildflower 17]

A few hours ago i changed the name of my emby server from emby to Midnight (name of my cat) and it went ok, i created a new user for a friend of mine and linked him up to an emby connect account and it went ok, i tested the user in a web browser via emby connect and it connected seeing the emby server. About an hour or so after, emby had an update i installed and restarted the server. The issue i face now is every time i log into emby connect on the web browser via phone/computer for any user with an emby connect account it shows the server Midnight but when i click on it i am greeted with.

"We're unable to connect to the selected server right now. Please ensure it is running and try again."

In the web browser on the pc i chose Add server and typed in the server address with the correct port and it logged me in, i log out and try logging back in with emby connect and it worked fine selecting Midnight. I thought great it might have solved it so got the friend to try logging back in and again and again i was greeted with the issue.

Has a name change buggered up the connection to the emby server via emby connect or was it the update?

It's a little frustrating. 

Thank you in advance. 

[ebr 16184]

Hi.  Make sure the update didn't cause your firewall rules to change and also that the IP address shown on the server dashboard is correct for accessing your server (both LAN and WAN).

[electricwildflower 17]

I forgot to add that i added a new router to my network which everything is now connected to, the setup i have is

Sky hub (internet comes in) - Netgear R6120 (connected via Wan port with Ethernet cable) - Freenas (connected to Netgear) - Emby (on Freenas)

Connecting remotely work briefly and then cut off and as the Netgear has internet coming into it from the Sky hub i didn't think adding a new router to the equation has put a spanner in the works for a few programs i use. The question is should Emby just continue to work as the nets coming in or do i need to do some kind of port forwarding on both routers.

I have done port forwarding before (never needed to do it for Emby on Sky router as it just worked remotely). 

 

[ebr 16184]

Yes, I imagine that is the issue.  Does canyouseeme.org find your port open?

[electricwildflower 17]

I checked on portcheckers.com and it came up with 

192.168.1.3 ➡
Port 24 lmtp

Port Closed

I have opened ports before on my Sky hub so know a little basics but port forwarding through two routers is a mystery i'm trying to grasp, watching tons on youtube videos and reading websites but getting no where so far. So in terms of power forwarding on two routers, do i have to port forward on 1 router and then repeat on the second router? or is there another way of doing it?

Short question? on the Emby dashboard under network it states.

Local HTTP port number: 8093 The TCP port number that Emby's HTTP server should bind to.
Local HTTP port number: 8920 The TCP port number that Emby's HTTP server should bind to.

Little confused which one is used for port forwarding or are either or one important? 

I also noticed earlier when i factory reset my Netgear (messed up a setting) the Emby IP changed and for a second i couldn't get in through the web browser and was wondering why till i checked the Netgear attached devices and seen it had changed. Can i set a static IP for Emby?

Cheers for the response

[Luke 42079]

@electricwildflower 

Quote

Can i set a static IP for Emby?

Emby doesn't have an IP, rather your network card in the server machine has an IP, so that's where you'd want to set the static IP. Does this help?

[Carlo 4561]

@electricwildflower have you got this figured out yet?

If not you may want to read up on "Bridge Mode" and see if you can do that with your equipment.