Hi,
I have nginx running on a server on my lan.
My router currently forwards ONLY port 443 to the nginx server which does its reverse proxy thing to the back end services.
I use remote subdomains for access and my own domain.
Remotely, you have to therefore do https://subdomain.example.com to get access, if you leave off the https, you cant connect.
As a test, in nginx I have added a reroute on port 80 to change to ssl :
server {
listen 80;
server_name _;
return 301 https://$host$request_uri;
}
And now if I open port 80 and redirect it to the nginx server, remote users can just key in subdomain.example.com and they get in fine.
Questions :
Is it a good idea to allow port 80 like this ? Is it safe ?
Is there a way in the router instead to do this redirect so i dont have the packets heading inside my lan ?
I have skynet, absolution installed if that helps.
Thanks.
I have nginx running on a server on my lan.
My router currently forwards ONLY port 443 to the nginx server which does its reverse proxy thing to the back end services.
I use remote subdomains for access and my own domain.
Remotely, you have to therefore do https://subdomain.example.com to get access, if you leave off the https, you cant connect.
As a test, in nginx I have added a reroute on port 80 to change to ssl :
server {
listen 80;
server_name _;
return 301 https://$host$request_uri;
}
And now if I open port 80 and redirect it to the nginx server, remote users can just key in subdomain.example.com and they get in fine.
Questions :
Is it a good idea to allow port 80 like this ? Is it safe ?
Is there a way in the router instead to do this redirect so i dont have the packets heading inside my lan ?
I have skynet, absolution installed if that helps.
Thanks.