From: Robert Vollmert <rob@vllmrt.net>
To: 36389@debbugs.gnu.org
Subject: bug#36389: nginx/certbot interaction doesn't work as documented
Date: Wed, 26 Jun 2019 10:39:22 +0200 [thread overview]
Message-ID: <249AC56B-BE05-4162-B65D-618490163CB0@vllmrt.net> (raw)
I’ve tried setting up nginx with certbot on guix. Two immediate issues:
- certbot extends the nginx service to serve challenge files. It appears
that this nginx service extension conflicts (silently) with an independently
configured nginx service. I.e., I had nginx previously configured, and
after adding certbot, my previous nginx kept running with the previous
configuration (even after herd restart nginx), while there was an additional
nginx config in the gnu store with the certbot-specific fragments. certbot
activation called nginx to test that fragment, but apparently never started
nginx (successfully?). There were no errors.
After removing the stand-alone nginx service and restarting nginx, it started
with the certbot configuration.
- After this, /var/lib/certbot/renew worked successfully to register a
certificate, but then failed when calling the nginx deploy hook that I’d
copied from the guix certbot documentation, because /var/run/nginx/pid
doesn’t exist. That might be a bug in the nginx package, not sure. I can’t
find an nginx pid file anywhere, and no other errors related to it either,
even though the config file includes
pid /var/run/nginx/pid;
next reply other threads:[~2019-06-26 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 8:39 Robert Vollmert [this message]
2019-06-26 9:31 ` bug#36389: nginx/certbot interaction doesn't work as documented Alex Sassmannshausen
2019-06-26 18:21 ` bug#36389: odd Robert Vollmert
2021-12-20 16:17 ` bug#36389: Nginx and certbot Andreas Enge
2021-12-20 16:46 ` Andreas Enge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=249AC56B-BE05-4162-B65D-618490163CB0@vllmrt.net \
--to=rob@vllmrt.net \
--cc=36389@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.