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?
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?
How did you install Lemmy? And are you using pictrs for images? Because that is normally available through Lemmy (same domain).
I installed using these instructions: https://join-lemmy.org/docs/en/administration/install_docker.html
# address where pictrs is available pictrs_url: "http://pictrs:8080"
Can you link your instance, and the url where the error happens?
https://beehaw.org/post/9
What value did you put in the line below? It should be beehaw.org, without www.
https://github.com/LemmyNet/lemmy-ansible/blob/main/templates/docker-compose.yml#L24
It is beehaw.org.
Hmm, then did you configure www.beehaw.org in some other place? Because Lemmy certainly doesnt add that.
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
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.
If you mean federate, then we aren’t comfortable doing that.
No, thats not necessary.
OK. Thanks for taking the time to try and resolve this. I appreciate it.