Unable to connect

[jonselin 0]

I'm unable to connect to my emby server from outside of my local network, using emby connect either through browser or phone app.

-Ports are open in firewalls

-Ports are forwarded in the router

 

My isp does not have routable IPv4 addresses from outside the network, does emby connect not support IPv6?

[markm83 0]

Same here.  I cannot connect either.  my server shows up on the list.  but it wont connect.

 

I'm using a VPN.  but, Plex still lets me use it from outside my network.....  can anyone help me?  I dont want to switch...  I like emby MUCH better

[Luke 42079]

Yea a lot of people here use vpns. can you be more specific?

[jonselin 0]

I am not using a VPN. When using the android app for example I am able sign into emby and I can see my server in the list, but when I tap on it it just spins for a while then says "We're unable to connect to the selected server right now. Please ensure it is running and try again."

 

When connecting through my local network it works just fine.

[Ponyo 22]

Sounds like you didn't configure port forwarding on your router or your firewall is blocking incoming connections.

 

Sent from my HTL23 using Tapatalk

[ebr 16184]

Please see the troubleshooting section here and let us know where you hit trouble.

[jonselin 0]

-I have inbound & outbound rules for ports 8096 and 8920 in the firewall on the computer.

-8096 and 8920 are forwarded to the right computer in the router.

 

My isp does not have routable IPv4 addresses from outside the network, does emby connect not support IPv6?

 

In-network connections work fine.

External connection (like the app on the phone) I can log in to emby connect, see my server in the list but when I tap on it I get a spinner for a while and then it says "We're unable to connect to the selected server right now. Please ensure it is running and try again."

 

I feel like I'm just repeating the exact same information using different words, is there any other information that you need? I have lifetime emby premier.

[ebr 16184]

So, when you tested your external address it worked from something like canyouseeme.org?

[dcook 299]

At your location if you browse to: canyouseeme.org

 

It should automatically fill in your ip address, right below that you can enter a port, if you enter 8096 and then click on Check Port it will let you know if your port is reachable.

[jonselin 0]

No, I canyouseeme.org does not work because as I've stated in multiple previous posts my ISP does not have routable IPv4 addresses, I do however have routable external IPv6 address.

[ebr 16184]

On what OS is your server running?

 

I think we have IPv6 working on Windows only right now.

[AgileHumor 123]

@jonselin Are you on AT&T uverse for your home router?

[jonselin 0]

I'm on Webpass, the emby server is running on a windows 10 machine.

[ojmalik 0]

It may not be your problem, but i had a similar experience. Turns out i had selected "Report https as external address" in advanced options. I'm assuming Connect didnt like the self-signed certificate and refused to connect. Maybe with a trusted CA certificate it would work.

 

What does it show on your main dashboard page for remote access? Have you tried accessing emby from an outside network using said address? For example:

 

Version 3.1.24.0

Emby Server is up to date

Running on http port 8096, and https port 8920.

Local access: http://192.168.10.15:8096

Remote access: http://xxx.xxx.xxx.xxx:8096

 

Having never used Emby through IPv6 only, just curious what your dashboard will display for the address?

Edited June 15, 2016 by ojmalik

[Luke 42079]

It may not be your problem, but i had a similar experience. Turns out i had selected "Report https as external address" in advanced options. I'm assuming Connect didnt like the self-signed certificate and refused to connect. Maybe with a trusted CA certificate it would work.

 

What does it show on your main dashboard page for remote access? Have you tried accessing emby from an outside network using said address? For example:

 

Version 3.1.24.0

Emby Server is up to date

Running on http port 8096, and https port 8920.

Local access: http://192.168.10.15:8096

Remote access: http://xxx.xxx.xxx.xxx:8096

 

Having never used Emby through IPv6 only, just curious what your dashboard will display for the address?

 

It's not connect but rather it depends on the app/device you're trying to connect from, and whether or not it allows us to configure it to accept the self-signed cert. If this is a browser-based app, then it's something you have to handle within the device/browser  yourself, assuming that it's possible.

[Guest asrequested]

I am not using a VPN. When using the android app for example I am able sign into emby and I can see my server in the list, but when I tap on it it just spins for a while then says "We're unable to connect to the selected server right now. Please ensure it is running and try again."

 

When connecting through my local network it works just fine.

 

I have this problem, too. I can't connect using Emby Connect on my phone (AT&T), but when manually type in my remote access IP, it works just fine.

Edited June 17, 2016 by Doofus

[jonselin 0]

My main dashboard just shows a IPv4 IP that isn't actually my router's IP but rather one of the ISP's routers further down, and that router won't forward to me. As I said, no routable IPv4 addresses on this ISP.

[Guest asrequested]

My main dashboard just shows a IPv4 IP that isn't actually my router's IP but rather one of the ISP's routers further down, and that router won't forward to me. As I said, no routable IPv4 addresses on this ISP.

 

Have you actually tried entering the remote access IP? 

[jonselin 0]

Yes. Probably a 100 times over the last 6 months as I've been trouble shooting this issue. Is there something about "My ISP does not have routable IPv4 addresses" which is hard to understand? I've stated the same thing 4-5 times in this thread now.

[Guest asrequested]

Yes. Probably a 100 times over the last 6 months as I've been trouble shooting this issue. Is there something about "My ISP does not have routable IPv4 addresses" which is hard to understand? I've stated the same thing 4-5 times in this thread now.

 

Hey, I was just asking. I apologize if that bothered you.

[dcook 299]

If you can't route ip traffic properly then I don't see how you are going to be able to communicate with Emby Connect

 

I understand your router may not have an IP4 address but your ISP must be doing some kind of IP4 to IP6 translation or you would not be able to get to 99% of the internet that is using IP4.

 

Very few services or servers connected to the Internet would be setup with IP6 alone 

Edited June 17, 2016 by dcook

[AgileHumor 123]

If your using AT&T Uverse for your home Emby Server internet connection, please check out this thread for a potential network: http://emby.media/community/index.php?/topic/34503-cannot-login-to-emby-connect-while-on-mobile-network/

 

If your NOT using AT&T Uverse, the above thread won't apply to your problem.

Edited June 17, 2016 by AgileHumor

[jonselin 0]

The ISP (assuming they're using some kind of hardware NAT) works fine with Chrome VPN (in/out), perforce, streaming to/from twitch, remote connecting to home automation through echo/insteon/harmony and a host of other online applications. The only thing that is not working is emby connect.

Edited June 18, 2016 by jonselin