mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #3701] No module named certbot #2445
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#2445
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @milkywayfarer on GitHub (Apr 15, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3701
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
Any of the attempts to renew or create Let's Encrypt certificates is met with the error
No module named 'certbot'. Everything worked before then suddenly stopped after a restart. Docker image was not modified in any way, I'm running vanilla.Nginx Proxy Manager Version
v2.11.1
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expect it to work again without needing to install
certbotby hand.Operating System
FreeBSD/Docker
@milkywayfarer commented on GitHub (Apr 15, 2024):
UPD: Fixed by running this set of instructions on the running container. I believe I do not need to do this myself :)
@thebigbone commented on GitHub (Apr 15, 2024):
I am running the same version and I haven't had any issues with certbot (ubuntu server). Could it be a BSD problem?
@github-actions[bot] commented on GitHub (Oct 25, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Oct 29, 2025):
Issue was closed due to inactivity.