mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #2427] New DuckDNS certificate yields: AttributeError: module 'certbot.interfaces' has no attribute 'IAuthenticator' #1701
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#1701
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 @LostOnTheLine on GitHub (Nov 25, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2427
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
When I try to get a new certificate I get an
Internal ErrorI thought there was something wrong with my settings so I tried with a lot of different variations, restarting docker, restarting the system, etc, but got the error every time.
I went into the logs & saw this error
An unexpected error occurred: AttributeError: module 'certbot.interfaces' has no attribute 'IAuthenticator'I tried altering a bunch of different things but always had the same error.
I edited an existing Host that was working fine & requested a new certificate & got the same error.
I created a new Docker that was essentially the same as the old one in the docker compose but went to a different directory for the mounts.
When trying to run it I ran into an error because I have mapped
- /g/docker/nginx/nginx.conf:/etc/nginx/nginx.confbecause there's no other way to have thenginx.configpersist without having the whole/etc/nginxdirectory which causes problems.I copied over the
nginx.conffrom the previous installation & started the app anew, creating the user account & then attempting to create a host. When I did I got the sameInternal Erroragain.I removed the mapping for the
nginx.conf, started the container copied it'snginx.conffrom the CLI to a directory that was mapped, & replaced the old one with the new one, then deleted everything except for that & started fresh again. I got to the Adding a Host point & again ran into anInternal Errorwhich was again in the logs with aAn unexpected error occurred: AttributeError: module 'certbot.interfaces' has no attribute 'IAuthenticator'A clean install has the same problem, so I'm now certain the error in not mine but with the app itself.
Also in the logs, at least the last few rounds I tried, is this error
[11/25/2022] [4:28:32 AM] [Express ] › ⚠ warning Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-1" --agree-tos --email "##REDACTED##" --domains "##REDACTED##" --authenticator dns-duckdns --dns-duckdns-credentials "/etc/letsencrypt/credentials/credentials-1"I also have confirmed the domains are correct & have tried different domains that are currently active in my old-version so long as I do not attempt to get an updated certificate for them.
Nginx Proxy Manager Version
v2.9.19 © 2022 jc21.com. Theme by Tabler
To Reproduce
Steps to reproduce the behavior:
Proxy HostsAdd Proxy Hostor edit a current Proxy HostSSLRequest a new SSL certificate with Let's EncryptForce SSLUse a DNS ChallengeDNS Provider:DuckDNSdns_duckdns_token=STRING-OF-NUMBERS-&-DASHES-FROM-DUCKDNSI Agree to the Let's Encrypt Terms of ServiceInternal ErrorExpected behavior
It to work properly & add a Host & get a new SSL certificate
Screenshots
Operating System
Additional context
@imranoftherings commented on GitHub (Nov 26, 2022):
I have the same issue
@godlike73 commented on GitHub (Nov 26, 2022):
same here
@LostOnTheLine commented on GitHub (Nov 26, 2022):
I've been having an issue for a few days before I had time to go in & see what was wrong. Did others as well?
@naoki66 commented on GitHub (Nov 26, 2022):
I have the same issue
@webnizam commented on GitHub (Nov 26, 2022):
I've been facing the same issue since the update to the latest version. I tried updating certbot and python manually inside the container but didn't fix it. I think the problem is just not for duckdns, it's for all letsencrypt certificates. The error arises right when we log in to the terminal as well.
docker exec -it nginx-proxy-manager-app-1 bash
tail /tmp/certbot-log-9xd8glri/log -n 100
@LostOnTheLine commented on GitHub (Nov 27, 2022):
Have you tried reverting to a previous image? do you know what image you were on before it stopped working?
I tried reverting to
jc21/nginx-proxy-manager:2.9.9, which appears to be the newest version that can be pulled via a version tag, not using thegithub-pr-2410type tags but no matter what I do when trying to login I get aBad Gatewayerror. There are tons ofgithub-prtags, sometimes being just days apart, so if you have a version to start with that saves a lot of testing to find one that works since their versions don't@LostOnTheLine commented on GitHub (Nov 27, 2022):
Well, that last post was made & I realized I was looking at it wrong, since that tags are listed alphabetically 2.9.19 comes before 2.9.9. So far I have tried 2.9.19, 2.9.18, 2.9.17, 2.9.16 with the same result. So I now believe that the issue is that something with letsencrypt has changed & NGINX just hasn't changed to meet whatever it now need to to work
Looking into it a bit I found a few things, but they all point to the same event from last year or older.
September 29, 2021 there was a change to their certificates system that seemed to cause a similar type of problem, but that was over a year ago & I don't see anything newer than that.
https://twitter.com/letsencrypt/status/1443248706166398984
@imranoftherings commented on GitHub (Nov 28, 2022):
See these links
https://github.com/certbot/certbot/issues/9478
https://github.com/certbot/certbot/issues/9427#issuecomment-1271019939
@kcastner commented on GitHub (Dec 4, 2022):
Same error to me with hetzner dns plugin... since now with every cert...
which certbot
/usr/local/bin/certbot --version
cat /tmp/certbot-log-pa2fs3m1/log
@writingdeveloper commented on GitHub (Dec 5, 2022):
It seems that I should wait for the new update now?
@DJKatastrof commented on GitHub (Dec 5, 2022):
Wondering the same thing, should we just wait?
@kcastner commented on GitHub (Dec 5, 2022):
For my side there is a temporary fix without use of DNS Plugin:
If you just restart NPM and issue for every single Subdomain, its working until you try to issue via dns plugin..
@rmoesbergen commented on GitHub (Dec 5, 2022):
There's an updated Docker image with a possible fix ( see PR #2411 ):
jc21/nginx-proxy-manager:github-pr-2411
Please test this and report your findings in the PR comments. Also note that renewals are also failing, so make sure to check the expiry of your certificates to prevent unexpected downtime.
@kcastner commented on GitHub (Dec 5, 2022):
Tried the new one... with success
the first ~10 minutes i get following error of multiple instances
After ~10 minutes its working again! - thx @rmoesbergen
@writingdeveloper commented on GitHub (Dec 7, 2022):
Solved with this method! Thanks :)
@LostOnTheLine commented on GitHub (Dec 16, 2022):
The regular non-dev one seems to work again now.