Cannot access Ubuntu web server site from outside network
So I've set up a LAMP web server on Ubuntu 14.04 server distro and installed owncloud as well as wordpress on it. It's connected to the web via ethernet and connectivity is good as far as I can tell (it can ping sites and pull in updates just fine). While I am connected to the wireless network from the router to which the server is connected (same network), I can access wordpress and owncloud just fine. However, the problem comes when I try to access it from a different network location (like from back at my apartment). The session just times out.
I checked the port forwarding (ZyXEL PK5001Z-CenturyLink router) for both port 80 and 443 as instructed by http://portforward.com/english/routers/port_forwarding/ZyXEL/PK5001Z-CenturyLink/Apache.htm. I've tried pinging each of those ports at the server's IP address with no luck.
I'm pretty new to programming and networking, so this is probably an easy fix, I just don't know where to look. Any suggestions would be greatly appreciated. The information for the server and addresses is listed below. Thank you in advance.
IP: 192.168.0.170
URL: fernweh.ddns.net "/wordpress" or "/owncloud"
dynamic ip assigned through noip.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
UPDATE
Okay, so I configured noip2 as suggested and still no luck. I also set up port forwarding on a couple higher ports (as suggested as well), still nothing.
I then checked to see what ports were actually open using
'nmap -v -sT local'
Which found 1000 ports, only 2 of which were not filtered
'80/tcp http open
443/tcp https closed'
Do I need to open up more ports using
'iptables -A INPUT -p tcp --dport "port number" -j INPUT'
Or is this irrelevant?
networking server dns wordpress owncloud-server
add a comment |
So I've set up a LAMP web server on Ubuntu 14.04 server distro and installed owncloud as well as wordpress on it. It's connected to the web via ethernet and connectivity is good as far as I can tell (it can ping sites and pull in updates just fine). While I am connected to the wireless network from the router to which the server is connected (same network), I can access wordpress and owncloud just fine. However, the problem comes when I try to access it from a different network location (like from back at my apartment). The session just times out.
I checked the port forwarding (ZyXEL PK5001Z-CenturyLink router) for both port 80 and 443 as instructed by http://portforward.com/english/routers/port_forwarding/ZyXEL/PK5001Z-CenturyLink/Apache.htm. I've tried pinging each of those ports at the server's IP address with no luck.
I'm pretty new to programming and networking, so this is probably an easy fix, I just don't know where to look. Any suggestions would be greatly appreciated. The information for the server and addresses is listed below. Thank you in advance.
IP: 192.168.0.170
URL: fernweh.ddns.net "/wordpress" or "/owncloud"
dynamic ip assigned through noip.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
UPDATE
Okay, so I configured noip2 as suggested and still no luck. I also set up port forwarding on a couple higher ports (as suggested as well), still nothing.
I then checked to see what ports were actually open using
'nmap -v -sT local'
Which found 1000 ports, only 2 of which were not filtered
'80/tcp http open
443/tcp https closed'
Do I need to open up more ports using
'iptables -A INPUT -p tcp --dport "port number" -j INPUT'
Or is this irrelevant?
networking server dns wordpress owncloud-server
1
It is very likely that your ISP blocks incoming connections to port 80, the default web port. Because of this, you'll have to configure your web server to listen on another port and forward that instead of 80. Leave 443 alone.
– TheWanderer
Oct 6 '15 at 23:55
1
^ See that. I would stay away from anything below 2000 unless you know what you're doing.
– Daniel
Oct 7 '15 at 0:21
I also had similar problem, I read somewhere that it's a bug in my router's firmware that is not allowing to port 80.
– kenn
Oct 7 '15 at 8:55
add a comment |
So I've set up a LAMP web server on Ubuntu 14.04 server distro and installed owncloud as well as wordpress on it. It's connected to the web via ethernet and connectivity is good as far as I can tell (it can ping sites and pull in updates just fine). While I am connected to the wireless network from the router to which the server is connected (same network), I can access wordpress and owncloud just fine. However, the problem comes when I try to access it from a different network location (like from back at my apartment). The session just times out.
I checked the port forwarding (ZyXEL PK5001Z-CenturyLink router) for both port 80 and 443 as instructed by http://portforward.com/english/routers/port_forwarding/ZyXEL/PK5001Z-CenturyLink/Apache.htm. I've tried pinging each of those ports at the server's IP address with no luck.
I'm pretty new to programming and networking, so this is probably an easy fix, I just don't know where to look. Any suggestions would be greatly appreciated. The information for the server and addresses is listed below. Thank you in advance.
IP: 192.168.0.170
URL: fernweh.ddns.net "/wordpress" or "/owncloud"
dynamic ip assigned through noip.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
UPDATE
Okay, so I configured noip2 as suggested and still no luck. I also set up port forwarding on a couple higher ports (as suggested as well), still nothing.
I then checked to see what ports were actually open using
'nmap -v -sT local'
Which found 1000 ports, only 2 of which were not filtered
'80/tcp http open
443/tcp https closed'
Do I need to open up more ports using
'iptables -A INPUT -p tcp --dport "port number" -j INPUT'
Or is this irrelevant?
networking server dns wordpress owncloud-server
So I've set up a LAMP web server on Ubuntu 14.04 server distro and installed owncloud as well as wordpress on it. It's connected to the web via ethernet and connectivity is good as far as I can tell (it can ping sites and pull in updates just fine). While I am connected to the wireless network from the router to which the server is connected (same network), I can access wordpress and owncloud just fine. However, the problem comes when I try to access it from a different network location (like from back at my apartment). The session just times out.
I checked the port forwarding (ZyXEL PK5001Z-CenturyLink router) for both port 80 and 443 as instructed by http://portforward.com/english/routers/port_forwarding/ZyXEL/PK5001Z-CenturyLink/Apache.htm. I've tried pinging each of those ports at the server's IP address with no luck.
I'm pretty new to programming and networking, so this is probably an easy fix, I just don't know where to look. Any suggestions would be greatly appreciated. The information for the server and addresses is listed below. Thank you in advance.
IP: 192.168.0.170
URL: fernweh.ddns.net "/wordpress" or "/owncloud"
dynamic ip assigned through noip.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
UPDATE
Okay, so I configured noip2 as suggested and still no luck. I also set up port forwarding on a couple higher ports (as suggested as well), still nothing.
I then checked to see what ports were actually open using
'nmap -v -sT local'
Which found 1000 ports, only 2 of which were not filtered
'80/tcp http open
443/tcp https closed'
Do I need to open up more ports using
'iptables -A INPUT -p tcp --dport "port number" -j INPUT'
Or is this irrelevant?
networking server dns wordpress owncloud-server
networking server dns wordpress owncloud-server
edited Oct 9 '15 at 23:47
Lord Julian
asked Oct 6 '15 at 23:46
Lord JulianLord Julian
112
112
1
It is very likely that your ISP blocks incoming connections to port 80, the default web port. Because of this, you'll have to configure your web server to listen on another port and forward that instead of 80. Leave 443 alone.
– TheWanderer
Oct 6 '15 at 23:55
1
^ See that. I would stay away from anything below 2000 unless you know what you're doing.
– Daniel
Oct 7 '15 at 0:21
I also had similar problem, I read somewhere that it's a bug in my router's firmware that is not allowing to port 80.
– kenn
Oct 7 '15 at 8:55
add a comment |
1
It is very likely that your ISP blocks incoming connections to port 80, the default web port. Because of this, you'll have to configure your web server to listen on another port and forward that instead of 80. Leave 443 alone.
– TheWanderer
Oct 6 '15 at 23:55
1
^ See that. I would stay away from anything below 2000 unless you know what you're doing.
– Daniel
Oct 7 '15 at 0:21
I also had similar problem, I read somewhere that it's a bug in my router's firmware that is not allowing to port 80.
– kenn
Oct 7 '15 at 8:55
1
1
It is very likely that your ISP blocks incoming connections to port 80, the default web port. Because of this, you'll have to configure your web server to listen on another port and forward that instead of 80. Leave 443 alone.
– TheWanderer
Oct 6 '15 at 23:55
It is very likely that your ISP blocks incoming connections to port 80, the default web port. Because of this, you'll have to configure your web server to listen on another port and forward that instead of 80. Leave 443 alone.
– TheWanderer
Oct 6 '15 at 23:55
1
1
^ See that. I would stay away from anything below 2000 unless you know what you're doing.
– Daniel
Oct 7 '15 at 0:21
^ See that. I would stay away from anything below 2000 unless you know what you're doing.
– Daniel
Oct 7 '15 at 0:21
I also had similar problem, I read somewhere that it's a bug in my router's firmware that is not allowing to port 80.
– kenn
Oct 7 '15 at 8:55
I also had similar problem, I read somewhere that it's a bug in my router's firmware that is not allowing to port 80.
– kenn
Oct 7 '15 at 8:55
add a comment |
1 Answer
1
active
oldest
votes
192.168.0.170 is a private IP address which the server uses in your private LAN. It may be used by anyone, and is for that reason never routed to the internet. To access the internet, you specified your router as the default gateway. You know that already, because you enabled port-forwarding on the router.
When I ping your DDNS address fernweh.ddns.net
it resolves to your internal IP
$ ping fernweh.ddns.net
PING fernweh.ddns.net (192.168.0.170) 56(84) bytes of data.
That cannot work for reasons stated above.
I suppose you're already running the NoIP client?. If yes, reconfigure it
sudo /usr/local/bin/noip2 -C
If not, download and install it like described. Since it is not good style to give a link and nothing else:
Download the source tarball to e.g your home folder and unpack
cd ~/Downloads
wget http://www.no-ip.com/client/linux/noip-duc-linux.tar.gz
tar xf noip-duc-linux.tar.gz
cd noip-2.1.9-1/
Switch to root: sudo -s
and install
make install
Finally, you need to either run noip2
or make it a service so it runs at boot time. (See the README.first
in the source folder)
It will compile the binaries and lead you through configuration.
Furthermore:
- You cannot ping a port.
ping
works by sending ICMP packages. Unlike TCP/UDP, ICMP has no concept of a port. It might well be, that your router and/or ISP block pings to you. - As @Zacharee1 and @Daniel already mentioned in the comments, it may also well be, that your ISP blocks well-known ports like HTTP(S). Run your webserver an a high port. That way you also gain a very slight protection against attacks, since a full port-scan is needed to discover the running web server. Note, that this is not a sufficient security measure! Keep your WordPress and OwnCloud installations up-to-date.
Wow, thank you. I am running the noip client, but I haven't configured it in the way that you describe; I'll definitely try that.--- I had read about forwarding on high ports as opposed to port 80, but the instructions I had said to use it. I figured since I'm so new at this that I should follow them to start with. ---As for the "ping" bit, I knew that wasn't the right term, but when I was troubleshooting, one suggestion had me test the ports remotely or something like that...sorry about the confusion. Thanks again; I'll be sure to post the results!
– Lord Julian
Oct 8 '15 at 0:20
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f682353%2fcannot-access-ubuntu-web-server-site-from-outside-network%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
192.168.0.170 is a private IP address which the server uses in your private LAN. It may be used by anyone, and is for that reason never routed to the internet. To access the internet, you specified your router as the default gateway. You know that already, because you enabled port-forwarding on the router.
When I ping your DDNS address fernweh.ddns.net
it resolves to your internal IP
$ ping fernweh.ddns.net
PING fernweh.ddns.net (192.168.0.170) 56(84) bytes of data.
That cannot work for reasons stated above.
I suppose you're already running the NoIP client?. If yes, reconfigure it
sudo /usr/local/bin/noip2 -C
If not, download and install it like described. Since it is not good style to give a link and nothing else:
Download the source tarball to e.g your home folder and unpack
cd ~/Downloads
wget http://www.no-ip.com/client/linux/noip-duc-linux.tar.gz
tar xf noip-duc-linux.tar.gz
cd noip-2.1.9-1/
Switch to root: sudo -s
and install
make install
Finally, you need to either run noip2
or make it a service so it runs at boot time. (See the README.first
in the source folder)
It will compile the binaries and lead you through configuration.
Furthermore:
- You cannot ping a port.
ping
works by sending ICMP packages. Unlike TCP/UDP, ICMP has no concept of a port. It might well be, that your router and/or ISP block pings to you. - As @Zacharee1 and @Daniel already mentioned in the comments, it may also well be, that your ISP blocks well-known ports like HTTP(S). Run your webserver an a high port. That way you also gain a very slight protection against attacks, since a full port-scan is needed to discover the running web server. Note, that this is not a sufficient security measure! Keep your WordPress and OwnCloud installations up-to-date.
Wow, thank you. I am running the noip client, but I haven't configured it in the way that you describe; I'll definitely try that.--- I had read about forwarding on high ports as opposed to port 80, but the instructions I had said to use it. I figured since I'm so new at this that I should follow them to start with. ---As for the "ping" bit, I knew that wasn't the right term, but when I was troubleshooting, one suggestion had me test the ports remotely or something like that...sorry about the confusion. Thanks again; I'll be sure to post the results!
– Lord Julian
Oct 8 '15 at 0:20
add a comment |
192.168.0.170 is a private IP address which the server uses in your private LAN. It may be used by anyone, and is for that reason never routed to the internet. To access the internet, you specified your router as the default gateway. You know that already, because you enabled port-forwarding on the router.
When I ping your DDNS address fernweh.ddns.net
it resolves to your internal IP
$ ping fernweh.ddns.net
PING fernweh.ddns.net (192.168.0.170) 56(84) bytes of data.
That cannot work for reasons stated above.
I suppose you're already running the NoIP client?. If yes, reconfigure it
sudo /usr/local/bin/noip2 -C
If not, download and install it like described. Since it is not good style to give a link and nothing else:
Download the source tarball to e.g your home folder and unpack
cd ~/Downloads
wget http://www.no-ip.com/client/linux/noip-duc-linux.tar.gz
tar xf noip-duc-linux.tar.gz
cd noip-2.1.9-1/
Switch to root: sudo -s
and install
make install
Finally, you need to either run noip2
or make it a service so it runs at boot time. (See the README.first
in the source folder)
It will compile the binaries and lead you through configuration.
Furthermore:
- You cannot ping a port.
ping
works by sending ICMP packages. Unlike TCP/UDP, ICMP has no concept of a port. It might well be, that your router and/or ISP block pings to you. - As @Zacharee1 and @Daniel already mentioned in the comments, it may also well be, that your ISP blocks well-known ports like HTTP(S). Run your webserver an a high port. That way you also gain a very slight protection against attacks, since a full port-scan is needed to discover the running web server. Note, that this is not a sufficient security measure! Keep your WordPress and OwnCloud installations up-to-date.
Wow, thank you. I am running the noip client, but I haven't configured it in the way that you describe; I'll definitely try that.--- I had read about forwarding on high ports as opposed to port 80, but the instructions I had said to use it. I figured since I'm so new at this that I should follow them to start with. ---As for the "ping" bit, I knew that wasn't the right term, but when I was troubleshooting, one suggestion had me test the ports remotely or something like that...sorry about the confusion. Thanks again; I'll be sure to post the results!
– Lord Julian
Oct 8 '15 at 0:20
add a comment |
192.168.0.170 is a private IP address which the server uses in your private LAN. It may be used by anyone, and is for that reason never routed to the internet. To access the internet, you specified your router as the default gateway. You know that already, because you enabled port-forwarding on the router.
When I ping your DDNS address fernweh.ddns.net
it resolves to your internal IP
$ ping fernweh.ddns.net
PING fernweh.ddns.net (192.168.0.170) 56(84) bytes of data.
That cannot work for reasons stated above.
I suppose you're already running the NoIP client?. If yes, reconfigure it
sudo /usr/local/bin/noip2 -C
If not, download and install it like described. Since it is not good style to give a link and nothing else:
Download the source tarball to e.g your home folder and unpack
cd ~/Downloads
wget http://www.no-ip.com/client/linux/noip-duc-linux.tar.gz
tar xf noip-duc-linux.tar.gz
cd noip-2.1.9-1/
Switch to root: sudo -s
and install
make install
Finally, you need to either run noip2
or make it a service so it runs at boot time. (See the README.first
in the source folder)
It will compile the binaries and lead you through configuration.
Furthermore:
- You cannot ping a port.
ping
works by sending ICMP packages. Unlike TCP/UDP, ICMP has no concept of a port. It might well be, that your router and/or ISP block pings to you. - As @Zacharee1 and @Daniel already mentioned in the comments, it may also well be, that your ISP blocks well-known ports like HTTP(S). Run your webserver an a high port. That way you also gain a very slight protection against attacks, since a full port-scan is needed to discover the running web server. Note, that this is not a sufficient security measure! Keep your WordPress and OwnCloud installations up-to-date.
192.168.0.170 is a private IP address which the server uses in your private LAN. It may be used by anyone, and is for that reason never routed to the internet. To access the internet, you specified your router as the default gateway. You know that already, because you enabled port-forwarding on the router.
When I ping your DDNS address fernweh.ddns.net
it resolves to your internal IP
$ ping fernweh.ddns.net
PING fernweh.ddns.net (192.168.0.170) 56(84) bytes of data.
That cannot work for reasons stated above.
I suppose you're already running the NoIP client?. If yes, reconfigure it
sudo /usr/local/bin/noip2 -C
If not, download and install it like described. Since it is not good style to give a link and nothing else:
Download the source tarball to e.g your home folder and unpack
cd ~/Downloads
wget http://www.no-ip.com/client/linux/noip-duc-linux.tar.gz
tar xf noip-duc-linux.tar.gz
cd noip-2.1.9-1/
Switch to root: sudo -s
and install
make install
Finally, you need to either run noip2
or make it a service so it runs at boot time. (See the README.first
in the source folder)
It will compile the binaries and lead you through configuration.
Furthermore:
- You cannot ping a port.
ping
works by sending ICMP packages. Unlike TCP/UDP, ICMP has no concept of a port. It might well be, that your router and/or ISP block pings to you. - As @Zacharee1 and @Daniel already mentioned in the comments, it may also well be, that your ISP blocks well-known ports like HTTP(S). Run your webserver an a high port. That way you also gain a very slight protection against attacks, since a full port-scan is needed to discover the running web server. Note, that this is not a sufficient security measure! Keep your WordPress and OwnCloud installations up-to-date.
answered Oct 7 '15 at 8:48
NephenteNephente
3,79611020
3,79611020
Wow, thank you. I am running the noip client, but I haven't configured it in the way that you describe; I'll definitely try that.--- I had read about forwarding on high ports as opposed to port 80, but the instructions I had said to use it. I figured since I'm so new at this that I should follow them to start with. ---As for the "ping" bit, I knew that wasn't the right term, but when I was troubleshooting, one suggestion had me test the ports remotely or something like that...sorry about the confusion. Thanks again; I'll be sure to post the results!
– Lord Julian
Oct 8 '15 at 0:20
add a comment |
Wow, thank you. I am running the noip client, but I haven't configured it in the way that you describe; I'll definitely try that.--- I had read about forwarding on high ports as opposed to port 80, but the instructions I had said to use it. I figured since I'm so new at this that I should follow them to start with. ---As for the "ping" bit, I knew that wasn't the right term, but when I was troubleshooting, one suggestion had me test the ports remotely or something like that...sorry about the confusion. Thanks again; I'll be sure to post the results!
– Lord Julian
Oct 8 '15 at 0:20
Wow, thank you. I am running the noip client, but I haven't configured it in the way that you describe; I'll definitely try that.--- I had read about forwarding on high ports as opposed to port 80, but the instructions I had said to use it. I figured since I'm so new at this that I should follow them to start with. ---As for the "ping" bit, I knew that wasn't the right term, but when I was troubleshooting, one suggestion had me test the ports remotely or something like that...sorry about the confusion. Thanks again; I'll be sure to post the results!
– Lord Julian
Oct 8 '15 at 0:20
Wow, thank you. I am running the noip client, but I haven't configured it in the way that you describe; I'll definitely try that.--- I had read about forwarding on high ports as opposed to port 80, but the instructions I had said to use it. I figured since I'm so new at this that I should follow them to start with. ---As for the "ping" bit, I knew that wasn't the right term, but when I was troubleshooting, one suggestion had me test the ports remotely or something like that...sorry about the confusion. Thanks again; I'll be sure to post the results!
– Lord Julian
Oct 8 '15 at 0:20
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f682353%2fcannot-access-ubuntu-web-server-site-from-outside-network%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
It is very likely that your ISP blocks incoming connections to port 80, the default web port. Because of this, you'll have to configure your web server to listen on another port and forward that instead of 80. Leave 443 alone.
– TheWanderer
Oct 6 '15 at 23:55
1
^ See that. I would stay away from anything below 2000 unless you know what you're doing.
– Daniel
Oct 7 '15 at 0:21
I also had similar problem, I read somewhere that it's a bug in my router's firmware that is not allowing to port 80.
– kenn
Oct 7 '15 at 8:55