[GH-ISSUE #2427] New DuckDNS certificate yields: AttributeError: module 'certbot.interfaces' has no attribute 'IAuthenticator' #1701

Closed
opened 2026-02-26 07:32:06 +03:00 by kerem · 16 comments
Owner

Originally created by @LostOnTheLine on GitHub (Nov 25, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2427

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    • Yes
  • Are you sure you're not using someone else's docker image?
    • Yes
  • Have you searched for similar issues (both open and closed)?
    • Yes

Describe the bug

When I try to get a new certificate I get an Internal Error
I 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.conf because there's no other way to have the nginx.config persist without having the whole /etc/nginx directory which causes problems.
I copied over the nginx.conf from the previous installation & started the app anew, creating the user account & then attempting to create a host. When I did I got the same Internal Error again.
I removed the mapping for the nginx.conf, started the container copied it's nginx.conf from 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 an Internal Error which was again in the logs with a An 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:

  1. Go to Proxy Hosts
  2. Click on Add Proxy Host or edit a current Proxy Host
  3. Go to SSL
  4. Request a new SSL certificate with Let's Encrypt
  5. Enable Force SSL
  6. Use a DNS Challenge
  7. DNS Provider: DuckDNS
  8. Copy-Paste Duck DNS Token from duckdns.org: dns_duckdns_token=STRING-OF-NUMBERS-&-DASHES-FROM-DUCKDNS
  9. I Agree to the Let's Encrypt Terms of Service
  10. See Internal Error
  11. Goto Logs
  12. See error

Expected behavior

It to work properly & add a Host & get a new SSL certificate

Screenshots

Operating System

  • Windows 10 Pro 21H2 - 19044.2130
  • Docker Desktop 4.14.1 (91661)
  • Portainer Business Edition 2.16.2 (Not in Swarm mode)
  • Portainer Stack
version: "3"
services:
  nginx_proxy:
    image: 'jc21/nginx-proxy-manager:latest'
    container_name: nginx_proxy
    restart: unless-stopped
    ports:
      - 80:80
      - 443:443
      - 81:81
    environment:
      DISABLE_IPV6: 'true'
    volumes:
      - /g/docker/nginx/nginx.conf:/etc/nginx/nginx.conf
      - /g/docker/nginx/log:/var/log
      - /g/docker/nginx/data:/data
      - /g/docker/nginx/letsencrypt:/etc/letsencrypt
      - /g/docker/nginx/www:/var/www
      - /g/docker/nginx/images:/var/images

Additional context

Originally created by @LostOnTheLine on GitHub (Nov 25, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2427 <!-- Are you in the right place? - If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit. - If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask. - If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the *right place.* --> **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - Are you sure you're not using someone else's docker image? - Yes - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug** <!-- A clear and concise description of what the bug is. --> When I try to get a new certificate I get an `Internal Error` I 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.conf` because there's no other way to have the `nginx.config` persist without having the whole `/etc/nginx` directory which causes problems. I copied over the `nginx.conf` from the previous installation & started the app anew, creating the user account & then attempting to create a host. When I did I got the same `Internal Error` again. I removed the mapping for the `nginx.conf`, started the container copied it's `nginx.conf` from 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 an `Internal Error` which was again in the logs with a `An 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** <!-- What version of Nginx Proxy Manager is reported on the login page? --> v2.9.19 © 2022 [jc21.com](https://jc21.com/?utm_source=nginx-proxy-manager). Theme by [Tabler](https://tabler.github.io/?utm_source=nginx-proxy-manager) **To Reproduce** Steps to reproduce the behavior: 1. Go to `Proxy Hosts` 2. Click on `Add Proxy Host` or edit a current Proxy Host 3. Go to `SSL` 4. `Request a new SSL certificate with Let's Encrypt` 5. Enable `Force SSL` 6. `Use a DNS Challenge` 7. `DNS Provider:` `DuckDNS` 8. Copy-Paste Duck DNS Token from duckdns.org: `dns_duckdns_token=STRING-OF-NUMBERS-&-DASHES-FROM-DUCKDNS` 9. ✅ `I Agree to the Let's Encrypt Terms of Service` 10. See `Internal Error` 11. Goto Logs 12. See error **Expected behavior** <!-- A clear and concise description of what you expected to happen. --> It to work properly & add a Host & get a new SSL certificate **Screenshots** <!-- If applicable, add screenshots to help explain your problem. --> **Operating System** <!-- Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error. --> - Windows 10 Pro 21H2 - 19044.2130 - Docker Desktop 4.14.1 (91661) - Portainer Business Edition 2.16.2 (Not in Swarm mode) - Portainer Stack > ``` > version: "3" > services: > nginx_proxy: > image: 'jc21/nginx-proxy-manager:latest' > container_name: nginx_proxy > restart: unless-stopped > ports: > - 80:80 > - 443:443 > - 81:81 > environment: > DISABLE_IPV6: 'true' > volumes: > - /g/docker/nginx/nginx.conf:/etc/nginx/nginx.conf > - /g/docker/nginx/log:/var/log > - /g/docker/nginx/data:/data > - /g/docker/nginx/letsencrypt:/etc/letsencrypt > - /g/docker/nginx/www:/var/www > - /g/docker/nginx/images:/var/images > ``` **Additional context** <!-- Add any other context about the problem here, docker version, browser version, logs if applicable to the problem. Too much info is better than too little. -->
kerem 2026-02-26 07:32:06 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@imranoftherings commented on GitHub (Nov 26, 2022):

I have the same issue

<!-- gh-comment-id:1327970501 --> @imranoftherings commented on GitHub (Nov 26, 2022): I have the same issue
Author
Owner

@godlike73 commented on GitHub (Nov 26, 2022):

same here

<!-- gh-comment-id:1327991180 --> @godlike73 commented on GitHub (Nov 26, 2022): same here
Author
Owner

@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?

<!-- gh-comment-id:1327997168 --> @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?
Author
Owner

@naoki66 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?

I have the same issue

<!-- gh-comment-id:1328022478 --> @naoki66 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? I have the same issue
Author
Owner

@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

An unexpected error occurred:
AttributeError: module 'certbot.interfaces' has no attribute 'IAuthenticator'
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/certbot-log-9xd8glri/log or re-run Certbot with -v for more details.
Version 2.9.18 (cce73be) 2022-03-31 05:46:34 UTC, OpenResty 1.19.9.1, debian 10 (buster), Certbot
Base: debian:buster-slim, linux/arm64
Certbot: nginxproxymanager/nginx-full:latest, linux/arm64
Node: nginxproxymanager/nginx-full:certbot, linux/arm64

tail /tmp/certbot-log-9xd8glri/log -n 100

2022-11-26 13:33:30,067:DEBUG:certbot._internal.log:Exiting abnormally:
Traceback (most recent call last):
File "/usr/local/bin/certbot", line 8, in
sys.exit(main())
File "/usr/local/lib/python3.7/dist-packages/certbot/main.py", line 19, in main
return internal_main.main(cli_args)
File "/usr/local/lib/python3.7/dist-packages/certbot/_internal/main.py", line 1707, in main
plugins = plugins_disco.PluginsRegistry.find_all()
File "/usr/local/lib/python3.7/dist-packages/certbot/_internal/plugins/disco.py", line 208, in find_all
cls._load_entry_point(entry_point, plugins)
File "/usr/local/lib/python3.7/dist-packages/certbot/_internal/plugins/disco.py", line 215, in _load_entry_point
plugin_ep = PluginEntryPoint(entry_point)
File "/usr/local/lib/python3.7/dist-packages/certbot/_internal/plugins/disco.py", line 56, in init
self.plugin_cls: Type[interfaces.Plugin] = entry_point.load()
File "/usr/local/lib/python3.7/dist-packages/pkg_resources/init.py", line 2450, in load
return self.resolve()
File "/usr/local/lib/python3.7/dist-packages/pkg_resources/init.py", line 2456, in resolve
module = import(self.module_name, fromlist=['name'], level=0)
File "/usr/local/lib/python3.7/dist-packages/certbot_dns_duckdns/cert/client.py", line 14, in
@zope.interface.implementer(interfaces.IAuthenticator)
AttributeError: module 'certbot.interfaces' has no attribute 'IAuthenticator'
2022-11-26 13:33:30,067:ERROR:certbot._internal.log:An unexpected error occurred:
2022-11-26 13:33:30,068:ERROR:certbot._internal.log:AttributeError: module 'certbot.interfaces' has no attribute 'IAuthenticator'

<!-- gh-comment-id:1328047291 --> @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** > An unexpected error occurred: AttributeError: module 'certbot.interfaces' has no attribute 'IAuthenticator' Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/certbot-log-9xd8glri/log or re-run Certbot with -v for more details. Version 2.9.18 (cce73be) 2022-03-31 05:46:34 UTC, OpenResty 1.19.9.1, debian 10 (buster), Certbot Base: debian:buster-slim, linux/arm64 Certbot: nginxproxymanager/nginx-full:latest, linux/arm64 Node: nginxproxymanager/nginx-full:certbot, linux/arm64 **tail /tmp/certbot-log-9xd8glri/log -n 100** > 2022-11-26 13:33:30,067:DEBUG:certbot._internal.log:Exiting abnormally: Traceback (most recent call last): File "/usr/local/bin/certbot", line 8, in <module> sys.exit(main()) File "/usr/local/lib/python3.7/dist-packages/certbot/main.py", line 19, in main return internal_main.main(cli_args) File "/usr/local/lib/python3.7/dist-packages/certbot/_internal/main.py", line 1707, in main plugins = plugins_disco.PluginsRegistry.find_all() File "/usr/local/lib/python3.7/dist-packages/certbot/_internal/plugins/disco.py", line 208, in find_all cls._load_entry_point(entry_point, plugins) File "/usr/local/lib/python3.7/dist-packages/certbot/_internal/plugins/disco.py", line 215, in _load_entry_point plugin_ep = PluginEntryPoint(entry_point) File "/usr/local/lib/python3.7/dist-packages/certbot/_internal/plugins/disco.py", line 56, in __init__ self.plugin_cls: Type[interfaces.Plugin] = entry_point.load() File "/usr/local/lib/python3.7/dist-packages/pkg_resources/__init__.py", line 2450, in load return self.resolve() File "/usr/local/lib/python3.7/dist-packages/pkg_resources/__init__.py", line 2456, in resolve module = __import__(self.module_name, fromlist=['__name__'], level=0) File "/usr/local/lib/python3.7/dist-packages/certbot_dns_duckdns/cert/client.py", line 14, in <module> @zope.interface.implementer(interfaces.IAuthenticator) AttributeError: module 'certbot.interfaces' has no attribute 'IAuthenticator' 2022-11-26 13:33:30,067:ERROR:certbot._internal.log:An unexpected error occurred: 2022-11-26 13:33:30,068:ERROR:certbot._internal.log:AttributeError: module 'certbot.interfaces' has no attribute 'IAuthenticator'
Author
Owner

@LostOnTheLine commented on GitHub (Nov 27, 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.

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 the github-pr-2410 type tags but no matter what I do when trying to login I get a Bad Gateway error. There are tons of github-pr tags, 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

<!-- gh-comment-id:1328312335 --> @LostOnTheLine commented on GitHub (Nov 27, 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. 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 the `github-pr-2410` type tags but no matter what I do when trying to login I get a `Bad Gateway` error. There are tons of `github-pr` tags, 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
Author
Owner

@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

<!-- gh-comment-id:1328362830 --> @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
Author
Owner
<!-- gh-comment-id:1328378628 --> @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
Author
Owner

@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
/usr/local/bin/certbot --version
An unexpected error occurred:
AttributeError: module 'certbot.interfaces' has no attribute 'IAuthenticator'
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/certbot-log-pa2fs3m1/log or re-run Certbot with -v for more details.
cat /tmp/certbot-log-pa2fs3m1/log
2022-12-04 21:41:31,627:DEBUG:certbot._internal.log:Exiting abnormally:
Traceback (most recent call last):
  File "/usr/local/bin/certbot", line 8, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.7/dist-packages/certbot/main.py", line 19, in main
    return internal_main.main(cli_args)
  File "/usr/local/lib/python3.7/dist-packages/certbot/_internal/main.py", line 1707, in main
    plugins = plugins_disco.PluginsRegistry.find_all()
  File "/usr/local/lib/python3.7/dist-packages/certbot/_internal/plugins/disco.py", line 208, in find_all
    cls._load_entry_point(entry_point, plugins)
  File "/usr/local/lib/python3.7/dist-packages/certbot/_internal/plugins/disco.py", line 215, in _load_entry_point
    plugin_ep = PluginEntryPoint(entry_point)
  File "/usr/local/lib/python3.7/dist-packages/certbot/_internal/plugins/disco.py", line 56, in __init__
    self.plugin_cls: Type[interfaces.Plugin] = entry_point.load()
  File "/usr/local/lib/python3.7/dist-packages/pkg_resources/__init__.py", line 2450, in load
    return self.resolve()
  File "/usr/local/lib/python3.7/dist-packages/pkg_resources/__init__.py", line 2456, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/local/lib/python3.7/dist-packages/certbot_dns_hetzner/dns_hetzner.py", line 18, in <module>
    @zope.interface.implementer(interfaces.IAuthenticator)
AttributeError: module 'certbot.interfaces' has no attribute 'IAuthenticator'
2022-12-04 21:41:31,627:ERROR:certbot._internal.log:An unexpected error occurred:
2022-12-04 21:41:31,627:ERROR:certbot._internal.log:AttributeError: module 'certbot.interfaces' has no attribute 'IAuthenticator'
<!-- gh-comment-id:1336530719 --> @kcastner commented on GitHub (Dec 4, 2022): Same error to me with hetzner dns plugin... since now with every cert... <details><summary>which certbot</summary> ``` /usr/local/bin/certbot ``` </details> <details> <summary>/usr/local/bin/certbot --version</summary> ``` An unexpected error occurred: AttributeError: module 'certbot.interfaces' has no attribute 'IAuthenticator' Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/certbot-log-pa2fs3m1/log or re-run Certbot with -v for more details. ``` </details> <details> <summary>cat /tmp/certbot-log-pa2fs3m1/log</summary> ``` 2022-12-04 21:41:31,627:DEBUG:certbot._internal.log:Exiting abnormally: Traceback (most recent call last): File "/usr/local/bin/certbot", line 8, in <module> sys.exit(main()) File "/usr/local/lib/python3.7/dist-packages/certbot/main.py", line 19, in main return internal_main.main(cli_args) File "/usr/local/lib/python3.7/dist-packages/certbot/_internal/main.py", line 1707, in main plugins = plugins_disco.PluginsRegistry.find_all() File "/usr/local/lib/python3.7/dist-packages/certbot/_internal/plugins/disco.py", line 208, in find_all cls._load_entry_point(entry_point, plugins) File "/usr/local/lib/python3.7/dist-packages/certbot/_internal/plugins/disco.py", line 215, in _load_entry_point plugin_ep = PluginEntryPoint(entry_point) File "/usr/local/lib/python3.7/dist-packages/certbot/_internal/plugins/disco.py", line 56, in __init__ self.plugin_cls: Type[interfaces.Plugin] = entry_point.load() File "/usr/local/lib/python3.7/dist-packages/pkg_resources/__init__.py", line 2450, in load return self.resolve() File "/usr/local/lib/python3.7/dist-packages/pkg_resources/__init__.py", line 2456, in resolve module = __import__(self.module_name, fromlist=['__name__'], level=0) File "/usr/local/lib/python3.7/dist-packages/certbot_dns_hetzner/dns_hetzner.py", line 18, in <module> @zope.interface.implementer(interfaces.IAuthenticator) AttributeError: module 'certbot.interfaces' has no attribute 'IAuthenticator' 2022-12-04 21:41:31,627:ERROR:certbot._internal.log:An unexpected error occurred: 2022-12-04 21:41:31,627:ERROR:certbot._internal.log:AttributeError: module 'certbot.interfaces' has no attribute 'IAuthenticator' ``` </details>
Author
Owner

@writingdeveloper commented on GitHub (Dec 5, 2022):

It seems that I should wait for the new update now?

<!-- gh-comment-id:1336781686 --> @writingdeveloper commented on GitHub (Dec 5, 2022): It seems that I should wait for the new update now?
Author
Owner

@DJKatastrof commented on GitHub (Dec 5, 2022):

It seems that I should wait for the new update now?

Wondering the same thing, should we just wait?

<!-- gh-comment-id:1336841274 --> @DJKatastrof commented on GitHub (Dec 5, 2022): > It seems that I should wait for the new update now? Wondering the same thing, should we just wait?
Author
Owner

@kcastner commented on GitHub (Dec 5, 2022):

It seems that I should wait for the new update now?

Wondering the same thing, should we just wait?

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..

<!-- gh-comment-id:1336861628 --> @kcastner commented on GitHub (Dec 5, 2022): > > It seems that I should wait for the new update now? > > Wondering the same thing, should we just wait? 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..
Author
Owner

@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.

<!-- gh-comment-id:1336953707 --> @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.
Author
Owner

@kcastner 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.

Tried the new one... with success

the first ~10 minutes i get following error of multiple instances
Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-80" --agree-tos --email "EMAIL_REMOVED" --domains "*.EXAMPLE.dev,EXAMPLE.dev" --authenticator dns-hetzner --dns-hetzner-credentials "/etc/letsencrypt/credentials/credentials-80"
Another instance of Certbot is already running.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/certbot-log-0d844pcc/log or re-run Certbot with -v for more details.

    at ChildProcess.exithandler (node:child_process:402:12)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1100:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)

After ~10 minutes its working again! - thx @rmoesbergen

image

<!-- gh-comment-id:1336969831 --> @kcastner 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. Tried the new one... with success <details><summary>the first ~10 minutes i get following error of multiple instances</summary> ``` Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-80" --agree-tos --email "EMAIL_REMOVED" --domains "*.EXAMPLE.dev,EXAMPLE.dev" --authenticator dns-hetzner --dns-hetzner-credentials "/etc/letsencrypt/credentials/credentials-80" Another instance of Certbot is already running. Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/certbot-log-0d844pcc/log or re-run Certbot with -v for more details. at ChildProcess.exithandler (node:child_process:402:12) at ChildProcess.emit (node:events:513:28) at maybeClose (node:internal/child_process:1100:16) at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5) ``` </details> After ~10 minutes its working again! - thx @rmoesbergen ![image](https://user-images.githubusercontent.com/34087750/205593500-4e0ef95c-912b-4d31-9340-5b0dcaac8619.png)
Author
Owner

@writingdeveloper commented on GitHub (Dec 7, 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.

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

image

Solved with this method! Thanks :)

<!-- gh-comment-id:1340524452 --> @writingdeveloper commented on GitHub (Dec 7, 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. > > 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 > > ![image](https://user-images.githubusercontent.com/34087750/205593500-4e0ef95c-912b-4d31-9340-5b0dcaac8619.png) Solved with this method! Thanks :)
Author
Owner

@LostOnTheLine commented on GitHub (Dec 16, 2022):

The regular non-dev one seems to work again now.

<!-- gh-comment-id:1354329148 --> @LostOnTheLine commented on GitHub (Dec 16, 2022): The regular non-dev one seems to work again now.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#1701
No description provided.