Hi Bobby,

I’m currently having a very similar issue but that doesn’t seem to resolve it for me.

When I try to access my Admin panel, it throws this error:

Mixed Content: The page at 'https://mydomain.dev/admin' was loaded over HTTPS, but requested an insecure resource 'http://XX.XXX.XX.XXX/admin/init'. This request has been blocked; the content must be served over HTTPS.

I’ve gone through the guide and edited strapi.conf:

server {
    # Listen HTTP
    listen 80;
    server_name mydomain.dev;

    # Redirect HTTP to HTTPS
    return 301 https://$host$request_uri;
}

server {
    # Listen HTTPS
    listen 443 ssl;
    server_name mydomain.dev;

    # SSL config
    ssl_certificate /etc/letsencrypt/live/mydomain.dev/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/mydomain.dev/privkey.pem;

    # Proxy Config
    location / {
        proxy_pass http://strapi;
        proxy_http_version 1.1;
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Server $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;
        proxy_set_header Host $http_host;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "Upgrade";
        proxy_pass_request_headers on;
    }
}

upstream.conf:

# Strapi server
upstream strapi {
    server mydomain.dev:1337;
}

and Strapi’s server.js:

module.exports = ({ env }) => ({
  host: env('HOST', '0.0.0.0'),
  port: env.int('PORT', 1337),
  url: 'https://mydomain.dev',
  admin: {
    auth: {
      secret: env('ADMIN_JWT_SECRET'),
    },
  },
});

along with the existing .env file just in case:

NGINX_URL=https://mydomain.dev

I restarted nginx, Strapi, and the droplet itself but it’s still throwing the same mixed content error