starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 13 Packages Projects Releases 10 Wiki Activity

Nginx-proxy-manager transip SSL certbot error #557

New Issue
Closed
opened 2026-02-04 19:48:17 +03:00 by OVERLORD · 6 comments
OVERLORD commented 2026-02-04 19:48:17 +03:00
Owner
Copy Link

Originally created by @jerkelens on GitHub (Feb 26, 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?

certbot --dns-transip-credentials /etc/letsencrypt/credentials/credentials

📝 Provide a clear and concise description of the issue.

When creating a new SSL cert through the webUI it gives this error. Running the command manually through the shell reproduces this error.

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

  1. Fill in domain
  2. Check 'DNS challenge'
  3. Select TransIP
  4. Fill in user name and validate key file
  5. Accept EULA
  6. Click Save

❌ Paste the full error output (if available).

CommandError: usage:
certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ...

Certbot can obtain and install HTTPS/TLS/SSL certificates. By default,
it will attempt to use a webserver both for obtaining and installing the
certificate.
certbot: error: unrecognized arguments: --dns-transip-credentials /etc/letsencrypt/credentials/credentials-4

at /app/lib/utils.js:16:13
at ChildProcess.exithandler (node:child_process:410:5)
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)

🖼️ Additional context (optional).

I used to run a NPM docker, that didn't produce this error, so I'm sure the credentials file is right.

Originally created by @jerkelens on GitHub (Feb 26, 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? certbot --dns-transip-credentials /etc/letsencrypt/credentials/credentials ### 📝 Provide a clear and concise description of the issue. When creating a new SSL cert through the webUI it gives this error. Running the command manually through the shell reproduces this error. ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. 1. Fill in domain 2. Check 'DNS challenge' 3. Select TransIP 4. Fill in user name and validate key file 5. Accept EULA 6. Click Save ### ❌ Paste the full error output (if available). CommandError: usage: certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ... Certbot can obtain and install HTTPS/TLS/SSL certificates. By default, it will attempt to use a webserver both for obtaining and installing the certificate. certbot: error: unrecognized arguments: --dns-transip-credentials /etc/letsencrypt/credentials/credentials-4 at /app/lib/utils.js:16:13 at ChildProcess.exithandler (node:child_process:410:5) 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) ### 🖼️ Additional context (optional). I used to run a NPM docker, that didn't produce this error, so I'm sure the credentials file is right.
OVERLORD added the not a script issue label 2026-02-04 19:48:17 +03:00
OVERLORD commented 2026-02-04 19:48:37 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 26, 2025):

And what is Here the Script issue? We dont serve any certbot

There are 500 variants. Try another

@MickLesk commented on GitHub (Feb 26, 2025): And what is Here the Script issue? We dont serve any certbot There are 500 variants. Try another
OVERLORD commented 2026-02-04 19:48:47 +03:00
Author
Owner
Copy Link

@jerkelens commented on GitHub (Feb 27, 2025):

Out of the box this solution doesn't work for me, shouldn't it?

@jerkelens commented on GitHub (Feb 27, 2025): Out of the box this solution doesn't work for me, shouldn't it?
OVERLORD commented 2026-02-04 19:48:51 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Feb 27, 2025):

certbot: error: unrecognized arguments: --dns-transip-credentials /etc/letsencrypt/credentials/credentials-4 it is a certbot /npm error. I have a instance running in Production where it works fine. Reinstall and test again or ask on the NPM/certbot forums

@michelroegl-brunner commented on GitHub (Feb 27, 2025): `certbot: error: unrecognized arguments: --dns-transip-credentials /etc/letsencrypt/credentials/credentials-4` it is a certbot /npm error. I have a instance running in Production where it works fine. Reinstall and test again or ask on the NPM/certbot forums
OVERLORD commented 2026-02-04 19:48:56 +03:00
Author
Owner
Copy Link

@jerkelens commented on GitHub (Feb 27, 2025):

Nevermind, I will build my own LXC..

@jerkelens commented on GitHub (Feb 27, 2025): Nevermind, I will build my own LXC..
OVERLORD commented 2026-02-04 19:49:07 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Feb 27, 2025):

Thats the spirit

@tremor021 commented on GitHub (Feb 27, 2025): Thats the spirit
OVERLORD commented 2026-02-04 19:49:11 +03:00
Author
Owner
Copy Link

@ampyc commented on GitHub (Feb 28, 2025):

I've had the exact same problem with certbot - manually installing the transip plugin fixed it for me: pip install certbot-dns-transip

I had installed the plugins through the advertised method: /app/scripts/install-certbot-plugins but maybe I missed something here as a next step.

@ampyc commented on GitHub (Feb 28, 2025): I've had the exact same problem with certbot - manually installing the transip plugin fixed it for me: `pip install certbot-dns-transip` I had installed the plugins through the advertised method: `/app/scripts/install-certbot-plugins` but maybe I missed something here as a next step.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label not a script issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#557
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?