Node.js HTTPS Issue in Docker

Sounds like you’re in a bit of a pickle! Dealing with HTTPS and Docker can be tricky sometimes. Here are a few things you might wanna check:

1. SSL Certificates

Double-check that your SSL certificates are correctly set up. Make sure that the paths to the keys and certs are correct in your code and that they are accessible in your Docker container. If you see certificate errors, that could be a sign.

2. NGINX Reverse Proxy

If you’re using NGINX as a reverse proxy, make sure you’ve got the configuration right. Your server block should look something like this:

server {
        listen 443 ssl;
        server_name your.domain.com;

        ssl_certificate /path/to/your/certificate.crt;
        ssl_certificate_key /path/to/your/private.key;

        location / {
            proxy_pass http://your-node-app:your-port;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;
        }
    }

3. Mixed Content Warnings

The mixed content warnings mean you are trying to load resources (like images or scripts) over HTTP instead of HTTPS. Check your HTML and make sure all your resource links start with “https://” or “//”. Look out for hardcoded “http://” URLs. It would help to check where your assets are being loaded from.

4. Docker Networking

Make sure your Docker networking is set up correctly. Sometimes services can be isolated in their networks, and things might not route as expected. You may need to check your Docker compose file or your Docker network settings.

5. Force HTTPS

Consider adding a piece of middleware in your Node.js app to enforce HTTPS:

app.use((req, res, next) => {
        if (req.secure) {
            next();
        } else {
            res.redirect(`https://${req.headers.host}${req.url}`);
        }
    });

Hopefully, one of these tips will help you get things sorted! Good luck!