This repository was archived by the owner on Jan 11, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 8
Troubleshooting
MrHid6 edited this page Aug 5, 2022
·
1 revision
upstream ssm {
server <SSM IP>:3000;
}
server {
root /var/www/html;
index index.html index.htm index.nginx-debian.html;
server_name <WEBSITE HOSTNAME>;
location / {
proxy_pass http://ssm/;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Fowarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Fowarded-Proto $scheme;
proxy_cache_bypass $http_upgrade;
}
add_header Strict-Transport-Security "max-age=31536000" always; # managed by Certbot
listen 80;
}
Getting a EACCES on http://0.0.0.0:3000 on Windows?
First open powershell as a admin and check to see if windows has allocated the port using the following command:
netsh interface ipv4 show excludedportrange protocol=tcp
You will get a response simular to the one below:
Start Port End Port
---------- --------
1587 1686
1787 1886
1987 2086
2931 3030
50000 50059 *
As you can see the 2nd to last record windows has allocated ports 2931-3030 for something this conflicts with SSM default port of 3000
To fix this run the following commands:
net stop winnat
netsh int ipv4 set dynamic tcp start=49152 num=16384
netsh int ipv6 set dynamic tcp start=49152 num=16384
net start winnat