Jump to content

Server Unreachable when trying to access remotely


Philsutera

Recommended Posts

Philsutera

My server has a LAN connection to the internet and was working perfectly until May 24th. Since then I was no longer able to connect remotely however I have had no issues connecting while on my wifi. I am running Version 3.0.5621.4. Any suggestions? 

Link to comment
Share on other sites

AmericanCrisis

Are you using a static IP address?  How long have you been using Emby?  Your IP address might have changed if it's set to get it dynamically. 

Link to comment
Share on other sites

jordy

if you have rebooted/restarted your modem/router then it is likely that your external IP has changed. you need to set up a dynamic DNS account. there are a number of free & paid ones out there. IPUpdater is free and works very well for me.

Link to comment
Share on other sites

Philsutera

I have been using emby for about 3 weeks. I did have a dynamic IP but when it stopped working I read on other posts to set up a static IP so I did that and it has not fixes the problem.

Link to comment
Share on other sites

AmericanCrisis

It seems to me that it's not really a "problem" as it is doing what it is supposed to do. If you are able to access locally and not remotely then you need to set up a static ip address properly then worry bout dynamic DNS. Do it in that order.

 

Set up static ip address in the machine you have emby installed on.

 

Reserve that ip address on the router.

 

Make sure you're able to access remotely.

 

Now set up with NOIP. Most modern routers have this under their advanced tab in the control panel.

 

Tell emby dashboard what your address is.

Link to comment
Share on other sites

Chomicz

I'm having the same problem.  Emby no longer works externally.  I thought it was a firewall setting I have however my server is no longer displaying my correct external IP address and I have no idea how to configure.  I'm currently running version 3.0.5621.4.  Any advice?

Link to comment
Share on other sites

AmericanCrisis

Ok guys again this isn't an Emby problem the server is unreachable because your IP address changes unless you set up a static IP address:

 

1.  Reserve an IP address on the machine running Emby, here is how for Netgear routers.

 

2.  If using Emby on Windows (if on another platform Google it... after all Google is your friend) set up a static IP address.  Here is how.  

 

3.  Now, if you have a Netgear router, you can set up NO-IP by going to the Advanced Setup / Dynamic DNS.  IIRC I was prompted to sign up for the account through the control panel but it ultimately brought me to their website where I created an account etc.  

 

4.  Now that you have a static IP address and have reserved that address with the router and finished it off with getting a Dynamic DNS... Login to the dashboard and update your remote access bar.

  • Like 1
Link to comment
Share on other sites

Philsutera

Thanks

I set up a static IP and dynamic dns with no ip. I can now access it remotely but only of I enter my hostname into my browser. Emby connect is not working niether on my computer nor Android app

Link to comment
Share on other sites

check the external address that is displayed on the server dashboard. that is what emby connect uses. if that is not correct you can update it manually in advanced -> hosting. Or if you just made the change then you can also wait as Emby Connect will refresh itself several times per day.

  • Like 1
Link to comment
Share on other sites

Philsutera

When I type the address (with :port#) into a web browser it works fine. The problem is I can't connect with emby connect. On the server dashboard my local access is http:// IP address:8096 and remote access is https:// hostname:8920. 

Link to comment
Share on other sites

When I type the address (with :port#) into a web browser it works fine. The problem is I can't connect with emby connect. On the server dashboard my local access is http:// IP address:8096 and remote access is https:// hostname:8920. 

 

you've enabled https reporting? it could be https related.

Link to comment
Share on other sites

AmericanCrisis

When I type the address (with :port#) into a web browser it works fine. The problem is I can't connect with emby connect. On the server dashboard my local access is http:// IP address:8096 and remote access is https:// hostname:8920. 

 

Hmm that's strange.  My local access is the http://IPaddress:8096 and the remote access is http://servername.domain.com:8096 

 

I wonder why you have https.  Luke asked if you enabled https reporting... I have never heard of that before I wonder if you can disable it. 

Link to comment
Share on other sites

Philsutera

I got it working. I had report https as external address checked and had https in my external WAN address. I checked the box and deleted the s from the external WAN address and it started working. Thanks!

  • Like 1
Link to comment
Share on other sites

  • 3 months later...
techworld

How come I can connect to my host directly, but can't via Emby Connect?

I'm using https.

Connection Failure
We're unable to connect to the selected server right now. Please ensure it is running and try again.
Edited by techworld
Link to comment
Share on other sites

diaz1510

 

How come I can connect to my host directly, but can't via Emby Connect?

I'm using https.

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

I've been getting his same error message.  I thought it was a port forwarding issue, but I'm forwarding the ports and it still doesn't do anything.  Not sure whats changed recently but I had been able to access emby connect in the past without having to make all these router/IP type changes...

 

I haven't been able to figure out how to get access remotely using emby connect for awhile now and still haven't figured it out

Link to comment
Share on other sites

 

How come I can connect to my host directly, but can't via Emby Connect?

I'm using https.

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

 

You need to specify what app you're trying to connect with because it makes a big difference in relation to https support.

Link to comment
Share on other sites

The error occurred on Google Chrome, and Safari.

I've tried it both on computer and iPhone.

 

what url did you use for the online web client? did you use https?

Link to comment
Share on other sites

storyhack

Ok I'm having a similar problem. Last week I set everything up and was able to log in remotely from my laptop and an android phone. I used duckdns to handle my ip address. 

 

Since that time, the location where my server is located, there was a power outage, and I think emby might have updated. I am now running Version 3.0.5724.6.

 

I can access the server from the computer where emby is hosted via localhost:8096 and via <mylocalip>:8096. However, if I try from another computer on the lan to use <theembyserverip>:8096 I get an error. And of course if I try to go over the internet using both my router's ip and the duckdns host name, I get that same error. I know I have my router configured correctly, because I can start up another type of server and forward to it just fine.

 

I looked over my windows firewall settings, and they are set to allow traffic over port 8096. 

 

What am I missing? What else could be blocking access from other computers?

Link to comment
Share on other sites

techworld

I don't know whether its the router/modem or Emby HTTPS connection issue...

But I found out that remote access via Emby Connect required both HTTP & HTTPS ports forward in the router.

In addition, Remote Access in Manage Server should in the https://url:8920.

 

If I only port forwarding HTTPS, then Emby Connect refused to connect to my server.

If I connect directly via my URL, then it works fine.

Link to comment
Share on other sites

it's probably just that there is more work to be done in certain situations with https and emby connect.

Link to comment
Share on other sites

storyhack

Okay, I set up both ports 8096 and 8902 to forward via the router, but no joy.

 

So, my latest thought is that it might be a configuration thing within emby.

 

I can ping the emby serving machine (I'll call it #1) from within the lan just fine. If I fire up a web server on #1, I can see the served webpages from other computers on the lan and can access it remotely with the port forwarding on my router.

 

I can access emby from a browser on #1, but not anywhere else. I've attached a screenshot from my windows firewall, and pixelated out the unrelated entries.

 

560d62e4dfe8f_screenshot.png

 

So where do I go from here? Is there a way to roll back to the last version of emby to see if the problem is in the newest version? 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...