My site certificate only supports non-www addresses. So, when we try to access an image uploaded to the site we are getting a bad certificate warning because there is a ‘www’ in the address. Is there a solution for this?

      • @suspended@lemmy.mlOP
        link
        fedilink
        12 years ago

        Here are the server blocks of my nginx conf file:

        server {
        	if ($host = beehaw.org) {
        		return 301 https://beehaw.org$request_uri;
        	} # managed by Certbot
        	
        	listen 80;
        	listen [::]:80;
        	server_name beehaw.org www.beehaw.org;
        	location /.well-known/acme-challenge/ {
        		root /var/www/certbot;
        	}
        	location / {
        		return 301 https://$host$request_uri;
        	}
        
        }
        
        server  {
        	listen 443 ssl http2;
        	listen [::]:443 ssl http2;
        	server_name beehaw.org www.beehaw.org;
        	ssl_certificate /etc/letsencrypt/live/beehaw.org-0001/fullchain.pem; #managed by Certbot
        	ssl_certificate_key /etc/letsencrypt/live/beehaw.org-0001/privkey.pem; #managed by Certbot
        
        • @nutomic@lemmy.mlM
          link
          fedilink
          12 years ago

          Its possible that certbot messed up something in your nginx config, but i dont see how that would affect the html sent by the server. Did you previously have www.beehaw.org set in docker-compose.yml? Maybe its still using the old setting.

          Otherwise i cant think of anything.

          • @suspended@lemmy.mlOP
            link
            fedilink
            22 years ago

            Did you previously have www.beehaw.org set in docker-compose.yml? Maybe its still using the old setting.

            I may have. I don’t know how it could retain the old setting. Strange. Thanks for helping.