Can't connect to emby server outside home network

[jstewart72 1]

okay so i changed it , its 192.168.100.116

 put the rule in for 8096 and for 8920

 went to can you see me, failed

turned off windows firewall

can you see me -failed

[jstewart72 1]

EBR: if I use my phone that is on the local network (same network as server) and i put the 192 number in the browser with 8096  it does connect

[Carlo 4331]

Sounds like maybe it's your ISP filtering this.  Based on something you said earlier, let's try this:

In Emby set:

local port number 80

local https port number 443

 

In router:

80 on the WAN IP address to 192.168.100.116 port 80

443 on the WAN IP address to 192.168.100.116 port 443

 

Now what do you get?

 

PS also try this from a browser in your network:

http://192.168.100.116

https://192.168.100.116

do both of those work?

[jstewart72 1]

on my router it only allows me to put one ip in

[Carlo 4331]

You are only using one IP.

[jstewart72 1]

using port 80 on my router when I try to access from phone, site cant be reached

[Carlo 4331]

Are you sure you are setting up port forwarding in your router?  Routers will almost always allow you to setup multiple different forwards to different IPs. 

 

Can you give us a screen shot of the router setup where you are setting these Emby port forwards?

[jstewart72 1]

[Carlo 4331]

That does not look like the correct place to set forwarding as it's not even asking for the correct information.

 

What router brand is it?

[jstewart72 1]

d link dir878

[Carlo 4331]

Ahh, dlink, ok.

 

That does look ok.

 

Assuming your external IP is 100.100.100.100

With your current setup what happens when you open http://100.100.100.100 from a browser inside your network?

 

Obviously use your real external IP address here.

[Carlo 4331]

https://www.manualslib.com/manual/1184667/D-Link-Dir-879.html?page=87#manual

 

dlink might be a tad different.  Checkout the link above.  This uses the virtual server tab instead of port forwarding.  This setting allows you to set both the external and the internal ports.

 

Remove the port forwards and try setting both 80 and 443 or the defaults of 8096 and 8920 back up (adjust emby Advanced menu to match).

Does this work?

[jstewart72 1]

you mean the real ip? the one that would be on the wan access

[jstewart72 1]

already have the virtual set up as well 

[Carlo 4331]

You don't want both setup.  Remove the port forwarding and only use the virtual server as a test.

 

If this is working then from inside your network you should be able to open a browser on a computer type http://modemIP and it will open your Emby assuming you are using port 80.

 

http://modemIP should work the same as http://192.168.100.116 for you if the forwarding is working correctly.  If not there is something else that needs checking.  Do you see now why I said TeamViewer would be the easier way?  Any chance you would be up for that?

 

modemIP in that context is your real Internet IP address.

 

Carlo

Edited October 10, 2018 by cayars

[jstewart72 1]

i deleted the port forwarding. I cant do a team viewer till after 330 est closer to 4

[Carlo 4331]

OK, if we can't resolve it by then.

 

So what happens now when you open a browser and enter http://modemIP  where the modemIP is your actual internet ip address?

[jstewart72 1]

it brings up what looks to be my cable modem log in

[Carlo 4331]

A quick teamviewer session and it appears the cable modem router is not passing external packets to his internal router where he has been making the changes.

 

@@jstewart72 is going to look up/get the credentials for the "external" modem/router and then we can set this up to pass through the external traffic.

[jstewart72 1]

Problem solved. Everything was set up right. We figured out it was my cable modem that was blocking the incoming. Once I went into the settings and changed it to bridge instead of routing, The server was instantly accessible. Thank you everyone for the help and HUGE thanks to cayars for helping and narrowing down what the problem was

[Guest asrequested]

I was going to ask if you've bridged the modem. This is one of the reasons that I use my own stuff. No weird config stuff I have to work around. Comcrap are terrible for that, especially with their new gigabit modems. They suck the big one!

[Luke 37231]

Thanks cayars.