I have the following Nginx config:

# HTTP redirect all traffic to HTTPS
server {
        listen 80 default_server;
        listen [::]:80 default_server;
        # server_name;
        if ($scheme = "http") { # Only redirect if not using SSL
        #       return 301 https://$server_name$request_uri;
                return 302 https://$host$request_uri;

# HTTPS — proxy all requests to the Node app
server {
    # Enable HTTP/2
    listen 443 ssl http2;
    listen [::]:443 ssl http2;

    # Use the Let’s Encrypt certificates
    ssl_certificate /etc/letsencrypt/live/;
    ssl_certificate_key /etc/letsencrypt/live/;

    # Include the SSL configuration from
    include snippets/ssl-params.conf;

    location / {
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-NginX-Proxy true;
        proxy_pass http://localhost:5000;
#        proxy_pass;
        proxy_ssl_session_reuse off;
        proxy_set_header Host $http_host;
        proxy_cache_bypass $http_upgrade;
        proxy_redirect off;

And a Docker container that I run using docker run -p 5000:5000 -d -e NODE_ENV=production containername:tagname

The container is running properly and the Node server listens on 5000 like so:

if (process.env.NODE_ENV === 'production') {
	server = app.listen(process.env.PORT || 9145, function () {'Production Server listening on port ' + process.env.PORT || 9145);
		process.env.DOMAIN = '' + process.env.PORT;

For some reason when I go to I get ERR_TOO_MANY_REDIRECTS and when I navigate to the IP and Port directly ( I get ERR_CONNECTION_CLOSED. This was all working before I added the Nginx layer (for SSL/RP) and it all works locally where I don’t run the Nginx server and just access localhost:5000 directly.

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

disabling this line proxy_set_header Host $http_host; ended up fixing it.