Jump to content

Unable to Connect Off-Network


Go to solution Solved by feerlessleadr,

Recommended Posts

Posted (edited)

Hi.

 

I'm at work, so I don't have log access at the moment, but I'm not sure they're relevant (I will add if requested when I get home).

 

Here's the trouble I'm having...

 

I have two Emby servers right now; one running on Windows which I intend to decommission when I get my new one working properly, and a new installation on a docker in unRAID.

 

The unRAID system is behaving wonderfully... when I'm on the same network. For some reason, whenever I try to access it on any user from off of my home network, I get the error "We're unable to connect to the selected server right now. Please ensure it is running and try again."

 

My other server, the one on Windows, has no problem at all when accessing off-network.

 

There is no port-forwarding active, however, I'm thinking it may be due to them running on the same port in the local network. Does that seem likely? If so, how can I correct?

 

Where should I start with troubleshooting this?

 

Thanks very much.

 

EDIT: The more I think about this, the more I think it's a port issue. I'm not sure how to approach it. I'd really like to have the new one replace the old one so the new one should be on 8096... do I just stop the old one from running?

post-479-0-36944400-1506005400_thumb.png

Edited by Netbug
  • Solution
feerlessleadr
Posted

Since you don't have port forwarding set up at the router, I'm assuming you are using some sort of upnp fo automatically map your internal port to your external port on your router?

 

I don't believe that you can have 2 services running on the same external port, so the first step to try would be to have your docket emby run on a different port.

  • Like 1
Posted

Since you don't have port forwarding set up at the router, I'm assuming you are using some sort of upnp fo automatically map your internal port to your external port on your router?

 

I don't believe that you can have 2 services running on the same external port, so the first step to try would be to have your docket emby run on a different port.

 

I'm pretty sure that's what's going on. I'll have to see about changing the port when I get home. I'm not sure if it will be the container settings or in the Emby settings. I'll check and report back.

 

Thanks.

Posted

Thanks guys. It was the port and the port forwarding. I set them both up, restarted the emby docker, and it works beaut. :)

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...