Despite hosting on nginx works fine in local web, it does not work with external ip
up vote
0
down vote
favorite
I have configured .net and nginx on ubuntu and it works in local web perfectly. I have static external ip, I have configured port forwarding on my router (I had done it for postgresql and it works fine from external web so I think I have done it properly) When it comes to nginx and when i type my ip f.e: xx.xx.x.xx:80 in url on computer in another web site is unreachable.
I have opened ports in firewall on linux:
sudo apt-get install ufw
sudo ufw allow 22/tcp
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp
sudo ufw enable
Here is my nginx config:
server
listen 80;
server_tokens off;
location /
proxy_pass http://localhost:5000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection keep-alive;
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
nginx hosting
New contributor
add a comment |
up vote
0
down vote
favorite
I have configured .net and nginx on ubuntu and it works in local web perfectly. I have static external ip, I have configured port forwarding on my router (I had done it for postgresql and it works fine from external web so I think I have done it properly) When it comes to nginx and when i type my ip f.e: xx.xx.x.xx:80 in url on computer in another web site is unreachable.
I have opened ports in firewall on linux:
sudo apt-get install ufw
sudo ufw allow 22/tcp
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp
sudo ufw enable
Here is my nginx config:
server
listen 80;
server_tokens off;
location /
proxy_pass http://localhost:5000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection keep-alive;
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
nginx hosting
New contributor
What is the error? Do the logs say anything?
– Shawn C.
Nov 10 at 14:57
Now I have tried to install only nginx and make it's default website accesible from external ip. I forwarder port 80 on router and it's the same. There must be something I missed.
– Zygmax
Nov 10 at 15:47
I have nothing in error.log. Access.log has another entry when I type my server ip in local web and see nginx default web but anything besides it
– Zygmax
Nov 10 at 15:53
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have configured .net and nginx on ubuntu and it works in local web perfectly. I have static external ip, I have configured port forwarding on my router (I had done it for postgresql and it works fine from external web so I think I have done it properly) When it comes to nginx and when i type my ip f.e: xx.xx.x.xx:80 in url on computer in another web site is unreachable.
I have opened ports in firewall on linux:
sudo apt-get install ufw
sudo ufw allow 22/tcp
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp
sudo ufw enable
Here is my nginx config:
server
listen 80;
server_tokens off;
location /
proxy_pass http://localhost:5000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection keep-alive;
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
nginx hosting
New contributor
I have configured .net and nginx on ubuntu and it works in local web perfectly. I have static external ip, I have configured port forwarding on my router (I had done it for postgresql and it works fine from external web so I think I have done it properly) When it comes to nginx and when i type my ip f.e: xx.xx.x.xx:80 in url on computer in another web site is unreachable.
I have opened ports in firewall on linux:
sudo apt-get install ufw
sudo ufw allow 22/tcp
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp
sudo ufw enable
Here is my nginx config:
server
listen 80;
server_tokens off;
location /
proxy_pass http://localhost:5000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection keep-alive;
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
nginx hosting
nginx hosting
New contributor
New contributor
New contributor
asked Nov 10 at 13:34
Zygmax
1
1
New contributor
New contributor
What is the error? Do the logs say anything?
– Shawn C.
Nov 10 at 14:57
Now I have tried to install only nginx and make it's default website accesible from external ip. I forwarder port 80 on router and it's the same. There must be something I missed.
– Zygmax
Nov 10 at 15:47
I have nothing in error.log. Access.log has another entry when I type my server ip in local web and see nginx default web but anything besides it
– Zygmax
Nov 10 at 15:53
add a comment |
What is the error? Do the logs say anything?
– Shawn C.
Nov 10 at 14:57
Now I have tried to install only nginx and make it's default website accesible from external ip. I forwarder port 80 on router and it's the same. There must be something I missed.
– Zygmax
Nov 10 at 15:47
I have nothing in error.log. Access.log has another entry when I type my server ip in local web and see nginx default web but anything besides it
– Zygmax
Nov 10 at 15:53
What is the error? Do the logs say anything?
– Shawn C.
Nov 10 at 14:57
What is the error? Do the logs say anything?
– Shawn C.
Nov 10 at 14:57
Now I have tried to install only nginx and make it's default website accesible from external ip. I forwarder port 80 on router and it's the same. There must be something I missed.
– Zygmax
Nov 10 at 15:47
Now I have tried to install only nginx and make it's default website accesible from external ip. I forwarder port 80 on router and it's the same. There must be something I missed.
– Zygmax
Nov 10 at 15:47
I have nothing in error.log. Access.log has another entry when I type my server ip in local web and see nginx default web but anything besides it
– Zygmax
Nov 10 at 15:53
I have nothing in error.log. Access.log has another entry when I type my server ip in local web and see nginx default web but anything besides it
– Zygmax
Nov 10 at 15:53
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
I hope, I find solution but still I don't know why it works this way. I have changed listen port to 9000 or any different instead 80 in nginx config and in my router forwarding. Now everything works fine, why port 80 does not work?
New contributor
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I hope, I find solution but still I don't know why it works this way. I have changed listen port to 9000 or any different instead 80 in nginx config and in my router forwarding. Now everything works fine, why port 80 does not work?
New contributor
add a comment |
up vote
0
down vote
I hope, I find solution but still I don't know why it works this way. I have changed listen port to 9000 or any different instead 80 in nginx config and in my router forwarding. Now everything works fine, why port 80 does not work?
New contributor
add a comment |
up vote
0
down vote
up vote
0
down vote
I hope, I find solution but still I don't know why it works this way. I have changed listen port to 9000 or any different instead 80 in nginx config and in my router forwarding. Now everything works fine, why port 80 does not work?
New contributor
I hope, I find solution but still I don't know why it works this way. I have changed listen port to 9000 or any different instead 80 in nginx config and in my router forwarding. Now everything works fine, why port 80 does not work?
New contributor
New contributor
answered Nov 10 at 16:46
Zygmax
1
1
New contributor
New contributor
add a comment |
add a comment |
Zygmax is a new contributor. Be nice, and check out our Code of Conduct.
Zygmax is a new contributor. Be nice, and check out our Code of Conduct.
Zygmax is a new contributor. Be nice, and check out our Code of Conduct.
Zygmax is a new contributor. Be nice, and check out our Code of Conduct.
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53239492%2fdespite-hosting-on-nginx-works-fine-in-local-web-it-does-not-work-with-external%23new-answer', 'question_page');
);
Post as a guest
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
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
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
What is the error? Do the logs say anything?
– Shawn C.
Nov 10 at 14:57
Now I have tried to install only nginx and make it's default website accesible from external ip. I forwarder port 80 on router and it's the same. There must be something I missed.
– Zygmax
Nov 10 at 15:47
I have nothing in error.log. Access.log has another entry when I type my server ip in local web and see nginx default web but anything besides it
– Zygmax
Nov 10 at 15:53