[Nginx Proxy Manager] - install-certbot-plugins Script #1908

Closed
opened 2026-02-05 02:44:42 +03:00 by OVERLORD · 9 comments
Owner

Originally created by @MortRainey on GitHub (Oct 31, 2025).

Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Nginx Proxy Manager

📂 What was the exact command used to execute the script?

/app/scripts/install-certbot-plugins

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

9.0.11

📝 Provide a clear and concise description of the issue.

The installation of verious certbot plugins fails.

🔄 Steps to reproduce the issue.

Fresh install. Just start the script.

Paste the full error output (if available).

log.txt

🖼️ Additional context (optional).

No response

Originally created by @MortRainey on GitHub (Oct 31, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Nginx Proxy Manager ### 📂 What was the exact command used to execute the script? /app/scripts/install-certbot-plugins ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? 9.0.11 ### 📝 Provide a clear and concise description of the issue. The installation of verious certbot plugins fails. ### 🔄 Steps to reproduce the issue. Fresh install. Just start the script. ### ❌ Paste the full error output (if available). [log.txt](https://github.com/user-attachments/files/23263278/log.txt) ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 02:44:42 +03:00
Author
Owner

@MickLesk commented on GitHub (Oct 31, 2025):

You need more deps, its Not an issue per Default. The most is installed, some Special need more deps

This Script is from npm himself. Not from us

@MickLesk commented on GitHub (Oct 31, 2025): You need more deps, its Not an issue per Default. The most is installed, some Special need more deps This Script is from npm himself. Not from us
Author
Owner

@MortRainey commented on GitHub (Oct 31, 2025):

You need more deps, its Not an issue per Default. The most is installed, some Special need more deps

This Script is from npm himself. Not from us

Maybe. But shouldn't they be installed by the install script? I bet they are in the docker image.

@MortRainey commented on GitHub (Oct 31, 2025): > You need more deps, its Not an issue per Default. The most is installed, some Special need more deps > > This Script is from npm himself. Not from us Maybe. But shouldn't they be installed by the install script? I bet they are in the docker image.
Author
Owner

@burgerga commented on GitHub (Oct 31, 2025):

I would swear certbot-dns-multi was included in the script which supports 100+ DNS providers, but I see it was removed 2 weeks ago. Maybe we can add that again and put a note in the json pointing to it (instead of suggesting to use /app/scripts/install-certbot-plugins)? Would prevent a lot of github issues with npm + certbot...

@burgerga commented on GitHub (Oct 31, 2025): I would swear [certbot-dns-multi](https://github.com/alexzorin/certbot-dns-multi) was included in the script which supports 100+ DNS providers, but I see it was removed 2 weeks ago. Maybe we can add that again and put a note in the json pointing to it (instead of suggesting to use `/app/scripts/install-certbot-plugins`)? Would prevent a lot of github issues with npm + certbot...
Author
Owner

@tremor021 commented on GitHub (Oct 31, 2025):

You need more deps, its Not an issue per Default. The most is installed, some Special need more deps
This Script is from npm himself. Not from us

Maybe. But shouldn't they be installed by the install script? I bet they are in the docker image.

Install it and check :)

@tremor021 commented on GitHub (Oct 31, 2025): > > You need more deps, its Not an issue per Default. The most is installed, some Special need more deps > > This Script is from npm himself. Not from us > > Maybe. But shouldn't they be installed by the install script? I bet they are in the docker image. Install it and check :)
Author
Owner

@requiemmg commented on GitHub (Nov 3, 2025):

HI, just installed nginx Proxy Manager by this script in my PVE as a new LXC. Did not change any configs and wanted to configure via webinterface, so I went for a certificate. As I wanted to use a "*.mydomain.net" wildcard, i went for DNS challenge.
My domain is being hosted at INWX, so i filled out the corresponding forms. I knew that DNS was set up correctly as I get certificates without any problem on other instances.

Long story short, it gave me a headache and this error:
Encountered exception during recovery: certbot.errors.PluginError: Unable to determine base domain for _acme-challenge.mydomain.net using names: ['_acme-challenge.mydomain.net', 'mydomain.net', 'net']. Unable to determine base domain for _acme-challenge.mydomain.net using names: ['_acme-challenge.mydomain.net, 'mydomain.net', 'net']. Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/letsencrypt-log/letsencrypt.log or re-run Certbot with -v for more details.

I will not bother you with what I tried, but when I checked in the lxc i found out that the corresponding certbot-dns-inwx was not installed after all.

A pip install certbot-dns-inws ran into

Attempting uninstall: cffi Found existing installation: cffi 1.17.1 error: uninstall-no-record-file × 
Cannot uninstall cffi 1.17.1 ╰─> The package's contents are unknown: no RECORD file was found for cffi.
hint: The package was installed by debian. You should check if it can uninstall the package.

Solution:

pip install --ignore-installed certbot-dns-inwx

After this, retrieval of the certificate from the web UI was not a problem anymore. But wow, it really gave me a headache.
Hope this helps someone!

@requiemmg commented on GitHub (Nov 3, 2025): HI, just installed nginx Proxy Manager by this script in my PVE as a new LXC. Did not change any configs and wanted to configure via webinterface, so I went for a certificate. As I wanted to use a "*.mydomain.net" wildcard, i went for DNS challenge. My domain is being hosted at INWX, so i filled out the corresponding forms. I knew that DNS was set up correctly as I get certificates without any problem on other instances. Long story short, it gave me a headache and this error: ```Encountered exception during recovery: certbot.errors.PluginError: Unable to determine base domain for _acme-challenge.mydomain.net using names: ['_acme-challenge.mydomain.net', 'mydomain.net', 'net']. Unable to determine base domain for _acme-challenge.mydomain.net using names: ['_acme-challenge.mydomain.net, 'mydomain.net', 'net']. Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/letsencrypt-log/letsencrypt.log or re-run Certbot with -v for more details.``` I will not bother you with what I tried, but when I checked in the lxc i found out that the corresponding certbot-dns-inwx was not installed after all. A `pip install certbot-dns-inws` ran into ``` Attempting uninstall: cffi Found existing installation: cffi 1.17.1 error: uninstall-no-record-file × Cannot uninstall cffi 1.17.1 ╰─> The package's contents are unknown: no RECORD file was found for cffi. hint: The package was installed by debian. You should check if it can uninstall the package. ``` Solution: `pip install --ignore-installed certbot-dns-inwx` After this, retrieval of the certificate from the web UI was not a problem anymore. But wow, it really gave me a headache. Hope this helps someone!
Author
Owner

@MortRainey commented on GitHub (Nov 3, 2025):

Main problem seems to be "Cannot import 'setuptools.build_meta'" but setuptools are installed.

@MortRainey commented on GitHub (Nov 3, 2025): Main problem seems to be "Cannot import 'setuptools.build_meta'" but setuptools are installed.
Author
Owner

@MickLesk commented on GitHub (Nov 3, 2025):

Then Report it to NPM Repo please. This Installer is not from us.

@MickLesk commented on GitHub (Nov 3, 2025): Then Report it to NPM Repo please. This Installer is not from us.
Author
Owner

@mathiaslehmann commented on GitHub (Nov 10, 2025):

https://v64.tech/t/nginx-proxy-manager-dnschallenge-ipv64-debian-13-fail/4177/7

@mathiaslehmann commented on GitHub (Nov 10, 2025): https://v64.tech/t/nginx-proxy-manager-dnschallenge-ipv64-debian-13-fail/4177/7
Author
Owner

@MortRainey commented on GitHub (Nov 10, 2025):

https://v64.tech/t/nginx-proxy-manager-dnschallenge-ipv64-debian-13-fail/4177/7

Danke dir. Das ist die Lösung. 🙏

@MortRainey commented on GitHub (Nov 10, 2025): > https://v64.tech/t/nginx-proxy-manager-dnschallenge-ipv64-debian-13-fail/4177/7 Danke dir. Das ist die Lösung. 🙏
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1908