Hey all! I'm attempting to set up Emby to run externally. However, whenever I attempt to connect with my Android device in either Chrome or the Emby app, I can see the server but get the message "We're unable to connect to the selected server right now. Please ensure it is running and try again."
I've been doing a fair bit of research on this issue and haven't been able to find anything that has solved the problem (though plenty of others with similar issues).
I've gone through the entire Connection Troubleshooter with no luck. I'm uncertain if my router is blocking traffic and how to check if so.
I'm on AT&T U-verse. The combined modem/router that AT&T gave us should be in bridge mode, and I'm using my own router for WiFi and ethernet connections.
I've set up a static IP for my PC that's running Emby Server. I've also set up port forwarding on my router for 8096 and that static IP address. Now it shows up as the local address. The remote address, however, is different:
I can connect to the local one from inside my network, no problem there. Still having problems connecting remotely.
I've tried both signing in with Emby Connect (the server shows up but gives me the error message when I attempt to connect) and adding a server manually for both the remote and in-home addresses (same message) on my Android from both Chrome and the Emby app. canyouseeme.org is showing my public IP address at port 8096 is not connecting ("Connection refused").
I suspect the problem is due to the difference between the two IP addresses, possibly due to the AT&T U-verse modem. I am unable to use that IP address, however, in my port forwarding (my router insists upon 10.166.*.*, which is different from the public IP). I did set "External domain" to the same IP as the In-Home (LAN) access just for kicks and that didn't seem to work either.
The attached log file does have an "error processing request" but I don't know if it's related.
I did some digging on the forum, on port forwarding in general, and so forth, and now I'm here. Has anyone else run into this particular problem when connecting remotely? Thanks.
Edited by mrdaneeyul, 18 January 2018 - 09:02 AM.
Removed image showing public IP address