Description
Not really an issue as such...
but I've been trying to configure NGINX so I can access this remotely and just can't get it working. I currently have it working locally on port 8080 with the following config:
server {
listen 8080;
listen [::]:8080;
location /tile/ {
proxy_set_header Host $http_host;
proxy_pass http://127.0.0.1:20008;
}
location /datasource/ {
proxy_set_header Host $http_host;
proxy_pass http://127.0.0.1:20008;
}
location / {
proxy_set_header Host $http_host;
proxy_pass http://127.0.0.1:20009;
}
}
When I try and access this remotely the tiles are all broken since they all have an address starting with 127.0.0.1:2008 (which, I gather, is taken from listenHost in lib/config.defaults.json), and that address makes no sense on a remote machine. I can't simply put my public IP address in since for various reasons I won't be able to open ports 20008 and 20009 (or, at least, I will be working in an environment where I can only work with ports 80 and 8080 for HTTP).
So, have you, or are you aware of somebody who has, got this working remotely? Basically, I'd like to throw this up on a CLI-only AWS instance and then access it remotely... and I'd like to use NGINX. Any tips you have would be most appreciated.
Cheers