Bad certificate warning

@suspended@lemmy.ml

https://beehaw.org/post/9

@nutomic@lemmy.ml

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

@suspended@lemmy.ml

It is beehaw.org.

@nutomic@lemmy.ml

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

@suspended@lemmy.ml

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.ml

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.ml

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.

@nutomic@lemmy.ml

You need to run docker-compose up to reload the settings. With docker-compose restart, it keeps using the old settings.

@suspended@lemmy.ml

I think I may have found something. Instead of using ‘restart’ with nginx shouldn’t I be using ‘reload’? See: https://linuxize.com/post/start-stop-restart-nginx/

reload: Gracefully restarts the Nginx service. On reload, the main Nginx process shuts down the child processes, loads the new configuration, and starts new child processes.

@suspended@lemmy.ml

I’ve never used docker-compose restart. I always use docker-compose up.