- 3 Posts
- 12 Comments
How do I do that?
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.
I’ve never used docker-compose restart. I always use docker-compose up.
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.
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
OK. Thanks for taking the time to try and resolve this. I appreciate it.
Can you link your instance…
If you mean federate, then we aren’t comfortable doing that.
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"
I can’t believe that I missed that! Thank you.