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?

  • @nutomicMA
    3•2 years ago

    How did you install Lemmy? And are you using pictrs for images? Because that is normally available through Lemmy (same domain).

      • @nutomicMA
        1•2 years ago

        Can you link your instance, and the url where the error happens?

        • @suspendedOP
          1•2 years ago

          Can you link your instance…

          If you mean federate, then we aren’t comfortable doing that.

          • @nutomicMA
            3•2 years ago

            No, thats not necessary.

            • @suspendedOP
              2•2 years ago

              OK. Thanks for taking the time to try and resolve this. I appreciate it.

              • @nutomicMA
                1•2 years ago

                Hmm, then did you configure www.beehaw.org in some other place? Because Lemmy certainly doesnt add that.

                • @suspendedOP
                  1•2 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