Can't Connect via LAN
-
Howdy --
I've set up Emby and everything is working fine except that while I can access the server from an external IP, I can't connect to it within the LAN. I've tried connecting to the server's IP/port number through a browser and through the FireTV app. The FireTV app isn't finding the server automatically and it doesn't like the IP/port numbers I'm giving it manually. Same is true via browser, however the browser works when using the domain name because I modified the hosts file to make that work.
Any idea what I'm missing?
Thanks, in advance.
-
Howdy --
I've set up Emby and everything is working fine except that while I can access the server from an external IP, I can't connect to it within the LAN. I've tried connecting to the server's IP/port number through a browser and through the FireTV app. The FireTV app isn't finding the server automatically and it doesn't like the IP/port numbers I'm giving it manually. Same is true via browser, however the browser works when using the domain name because I modified the hosts file to make that work.
Any idea what I'm missing?
Thanks, in advance.
-
Howdy --
I've set up Emby and everything is working fine except that while I can access the server from an external IP, I can't connect to it within the LAN. I've tried connecting to the server's IP/port number through a browser and through the FireTV app. The FireTV app isn't finding the server automatically and it doesn't like the IP/port numbers I'm giving it manually. Same is true via browser, however the browser works when using the domain name because I modified the hosts file to make that work.
Any idea what I'm missing?
Thanks, in advance.
-
@Ropyro Does your router support hairpin nat ? See https://docs.cloudron.io/troubleshooting/#hairpin-nat
-
@Ropyro Ah ok, that's the root of the issue. I too had a situation in the past where my router didn't support hairpin nat. The issue roughly is that the domain name (emby.myserver.com) points to an external IP. What you have to do is to somehow make a setup where it points to your internal IP when DNS requests are made in your internal network.
In my case, my router was also my DNS server. I could simply add an entry emby.myserver.com there and point it to my internal server IP and that was it.
-
@Ropyro Ah ok, that's the root of the issue. I too had a situation in the past where my router didn't support hairpin nat. The issue roughly is that the domain name (emby.myserver.com) points to an external IP. What you have to do is to somehow make a setup where it points to your internal IP when DNS requests are made in your internal network.
In my case, my router was also my DNS server. I could simply add an entry emby.myserver.com there and point it to my internal server IP and that was it.
-
Hey! do you have found a solution for that ? i have tried so many things that my brain explode...
"What you have to do is to somehow make a setup where it points to your internal IP when DNS requests are made in your internal network." my issue, i dont know how to make that...
-
Hey! do you have found a solution for that ? i have tried so many things that my brain explode...
"What you have to do is to somehow make a setup where it points to your internal IP when DNS requests are made in your internal network." my issue, i dont know how to make that...
