diff --git a/doc/overleaf-rc.md b/doc/overleaf-rc.md
index 0505c15..ffc32a8 100644
--- a/doc/overleaf-rc.md
+++ b/doc/overleaf-rc.md
@@ -26,6 +26,8 @@ Sets the path to the directory that will be mounted into the main `sharelatex` c
 
 Sets the host port that the container will bind to. For example, if this is set to `8099`, then the web interface will be available on `http://localhost:8099`.
 
+When used in conjunction with the [TLS Proxy](tls-proxy.md), the `proxy_pass` port in [nginx.conf](config/nginx/nginx.conf) also needs to be changed.
+
 - Default: 80
 
 
diff --git a/doc/tls-proxy.md b/doc/tls-proxy.md
index 29ab477..40c5863 100644
--- a/doc/tls-proxy.md
+++ b/doc/tls-proxy.md
@@ -6,4 +6,6 @@ The toolkit is initialised with a sample private key in `config/nginx/certs/over
 
 A default config for NGINX is provided in `config/nginx/nginx.conf` which may be customised to your requirements. The path to the config file can be changed with the `NGINX_CONFIG_PATH` variable.
 
-By default the https web interface will be available on `https://localhost:443`. The port can be changed via the `TLS_PORT` variable. 
+When the [SHARELATEX_PORT](overleaf-rc.md#sharelatex_port) variable is set, the port in the `proxy_pass` statement in `nginx.conf` needs to be changed to match.
+
+By default the https web interface will be available on `https://localhost:443`. The port can be changed via the `TLS_PORT` variable. 
\ No newline at end of file
diff --git a/lib/config-seed/nginx.conf b/lib/config-seed/nginx.conf
index ea9c02b..26b2ac9 100644
--- a/lib/config-seed/nginx.conf
+++ b/lib/config-seed/nginx.conf
@@ -57,7 +57,7 @@ http {
         client_max_body_size 50M;
 
         location / {
-            proxy_pass http://sharelatex:80; # change to whatever host/port the docker container is listening on.
+            proxy_pass http://sharelatex:80; # The port must match the value of SHARELATEX_PORT.
             proxy_set_header X-Forwarded-Proto $scheme;
             proxy_http_version 1.1;
             proxy_set_header Upgrade $http_upgrade;