Svar

Can't access website from the hosted machine.


HI there,

Please pay attention to the local IPs I am referring.

I have a machine/computer hosting my website. It has a local IP 192.168.0.10: 8080. And I have a port forward rule for all request from post 80 be forwarded to 192.168.0.10: 8080 in the router config. It is fine and working.

EXCEPT from THE machine/computer (192.168.0.10) . If I `ssh 192.168.0.10` and `curl -v example.com` it returns `connect to 2.108.***.*** port 80 failed: Connection timed out`.

My another computer (192.168.0.11) returns perfectly fine response. But if I host the same website in this (192.168.0.11) machine. And change the port forwarding config to point to this machine (192.168.0.11). Now I can't access the website from this machine (192.168.0.11) but is accessible from the previous (192.168.0.10) machine.

In brief, The machine hosting a website can't access the website. Is it something to do with the firewall. Or am I missing something here?
icon

Bedste svar af Slangefar 24 september 2018, 22:41

You seem to use the router Sagemcom 3890 from YouSee. There is a bug in the software on the router. If you use a "port forward" the computer with the IP in question seems to be isolated (a bit like put in DMZ). As far as I remember you need to access the computer through the WAN IP address. There is regular updates, but I have no idea, when there is a fix for this bug.

Se original

6 Kommentarer

Omdømme 7
Badge +7
You seem to use the router Sagemcom 3890 from YouSee. There is a bug in the software on the router. If you use a "port forward" the computer with the IP in question seems to be isolated (a bit like put in DMZ). As far as I remember you need to access the computer through the WAN IP address. There is regular updates, but I have no idea, when there is a fix for this bug.
What do you mean?
"As far as I remember you need to access the computer through the WAN IP address."

Lets assume
Domain : example.com
Public IP : 10.10.10.10
Server Local IP : 192.168.0.10
Port : 8080

Current Setup
example.com has DNS setup to point 10.10.10.10. My router has port forwarding config to forward all traffic from port 80 to 192.168.0.10: 8080.

So what should I change?
Omdømme 7
Badge +7
WAN IP is what you call public IP. Acces the computer on your LAN through 10.10.10.10 and not 192.168.0.10.
It is not about accessing my computer. Accessing the computer is fine. The problem is I can't access my website. Let me explain to you again.

Lets assume
Domain : example.com
Public IP : 10.10.10.10
Server Local IP : 192.168.0.10
Port : 8080

Current Setup
example.com has DNS setup to point 10.10.10.10. My router has port forwarding config to forward all traffic from port 80 to 192.168.0.10: 8080.

Can't access the website from 192.168.0.10
$ ssh 192.168.0.10
$ curl example.com
connect to 10.10.10.10 port 80 failed: Connection timed out

Can access website from another computer
$ ssh 192.168.0.11
$ curl example.com
**SOME HTML**


Now you might be thinking there is something wrong with 192.168.0.10's network config. But if I flip the whole setup and host the website on 192.168.0.11 and change the port forwarding rule.

Let's assume I host the website to a new computer, a new setup
Domain : example.com
Public IP : 10.10.10.10
Server Local IP : 192.168.0.11 (Another compoter)
Port : 8080

Changed port forwarding
example.com has DNS setup to point 10.10.10.10. My router has port forwarding config to forward all traffic from port 80 to 192.168.0.11: 8080.

Somehow I can access the website from 192.168.0.10 (Old computer where I was not able to access the website)
$ ssh 192.168.0.10
$ curl example.com
**SOME HTML**

But can't access the website from this computer (Which was working before)
$ ssh 192.168.0.11
$ curl example.com
connect to 10.10.10.10 port 80 failed: Connection timed out
Is your router Sagemfast 3890? It is known to have buggy behavior. This sounds to be one of those bugs. A couple of weeks ago they began rolling out new firmware to fix some of the bugs (some regarding port forwarding), but they rolled it back, because the new one was even buggier. :)
So I will wait until they fix the bugs :)

Besvar

    • :D
    • :?
    • :cool:
    • :S
    • :(
    • :@
    • :$
    • :8
    • :)
    • :P
    • ;)