certbot-standalone-nfq
HTTP authenticator plugin for Certbot which is compatible with any web server! (Linux only and root is required.)
How?
It works by asking the Linux kernel to temporarily divert incoming port 80 HTTP traffic into a queue. The Certbot plugin then picks out the Let's Encrypt validation requests from the queue and responds to them. All other traffic reaches its original destination, totally unchanged. This all happens very quickly and no traffic disruptions occur.
Why?
- Avoids messing about with any webserver configuration, meaning that it can work well with tricky webservers like Apache Tomcat.
- Avoids having a proxy in front of your normal webserver, which means all source addresses (and indeed every network packet) are totally preserved!
It is inspired by this community thread.
Installation
via snap
Using the certbot snap is the easiest way to use this plugin. See here for instructions on installing Certbot via snap.
sudo snap install certbot-standalone-nfq
sudo snap set certbot trust-plugin-with-root=ok
sudo snap connect certbot:plugin certbot-standalone-nfq
via pip
A source tarball is available.
| How did you install Certbot? | How to install the plugin |
|---|---|
From snap |
Don't use pip! Use the snap instructions above. |
Using the official Certbot pip instructions |
sudo /opt/certbot/bin/pip install certbot-standalone-nfq |
From apt, yum, dnf or any other distro package manager. (Requires Certbot 1.25.0 or newer.) |
pip install certbot-standalone-nfq |
Usage
certbot-standalone-nfq should just work without having to configure anything:
certbot certonly -a standalone-nfq \
-d "example.com" -d "www.example.com" \
--dry-run
If (for some reason, like port forwarding shenanigans) your web server is listening on
a port other than 80, you can use the --http-01-port argument of Certbot to change
the port that the plugin will divert the traffic from.
Metadata
Release files for certbot-standalone-nfq 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| certbot-standalone-nfq-0.1.3.tar.gz | 14.8 kB | Without provenance | Details for certbot-standalone-nfq-0.1.3.tar.gz |
Release files / certbot-standalone-nfq-0.1.3.tar.gz
| Download URL | certbot-standalone-nfq-0.1.3.tar.gz |
|---|---|
| Size | 14.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
73c88c0756c8f857af9f8ac9cc9f00c04f991c79d2a118f78d262d639c0823bb
|
|
BLAKE2b-256 checksum How to use checksums |
19f901057bfca6a64d1a1be93a88ce873d759f14adeab26b01781d28d417ebad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.2
|
Security for certbot-standalone-nfq 0.1.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.