Hello, I am also experiencing problems with setting up nginx and certbot, but I think it is more nginx that is to blame. After reconfiguring and restarting nginx, it is still running with the old configuration. Only rebooting solves the problem for me.
Here is what it looks like (everything as root): $ ps -ef | grep nginx root 2821 1 0 17:03 ? 00:00:00 nginx: master process /gnu/store/bdhfqs7sx3mal6pzz8z00hw4cpn5dj7x-nginx-1.21.4/sbin/nginx -c /gnu/store/q7bwm828r8y88sfs395n04bi8s6b7zwl-nginx.conf -p /var/run/nginx $ guix system reconfigure ... nginx: configuration file /gnu/store/clq2yshkq3gxpcqa6d54m8qif8i37kl9-nginx.conf test is successful $ herd restart nginx; ps -ef | grep nginx root 2835 1 0 17:12 ? 00:00:00 nginx: master process /gnu/store/bdhfqs7sx3mal6pzz8z00hw4cpn5dj7x-nginx-1.21.4/sbin/nginx -c /gnu/store/q7bwm828r8y88sfs395n04bi8s6b7zwl-nginx.conf -p /var/run/nginx Notice that it is still running the old, q7b... config file! $ reboot $ ps -ef | grep nginx root 188 1 0 17:13 ? 00:00:00 nginx: master process /gnu/store/bdhfqs7sx3mal6pzz8z00hw4cpn5dj7x-nginx-1.21.4/sbin/nginx -c /gnu/store/clq2yshkq3gxpcqa6d54m8qif8i37kl9-nginx.conf -p /var/run/nginx Now the new, clq... config file is used! So somehow nginx appears to memorise its previous configuration file even when the service is stopped. The problem can be solved by rebooting after each web server reconfiguration, but this is of course not very comfortable. Andreas
