[GH-ISSUE #3644] ClouDNS throws unrecognized arguments error #2414

Open
opened 2026-02-26 07:35:28 +03:00 by kerem · 5 comments
Owner

Originally created by @dreed47 on GitHub (Mar 20, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3644

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
ClouDNS throws unrecognized arguments error.

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-cloudns-credentials /etc/letsencrypt/credentials/credentials-12

    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)

Nginx Proxy Manager Version
v2.11.1

To Reproduce
Steps to reproduce the behavior:

  1. Add a new Lets Encrypt SSL certificate
  2. Add your ClouDNS hosted domain name
  3. Select ClouDNS
  4. SAdd dns_cloudns_auth_id and dns_cloudns_auth_password values and click save
  5. See error

Expected behavior
Expecting the SSL cert to be added

Screenshots

Operating System

Additional context

Originally created by @dreed47 on GitHub (Mar 20, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3644 <!-- 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** ClouDNS throws unrecognized arguments error. ``` 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-cloudns-credentials /etc/letsencrypt/credentials/credentials-12 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) ``` **Nginx Proxy Manager Version** v2.11.1 **To Reproduce** Steps to reproduce the behavior: 1. Add a new Lets Encrypt SSL certificate 2. Add your ClouDNS hosted domain name 3. Select ClouDNS 4. SAdd dns_cloudns_auth_id and dns_cloudns_auth_password values and click save 5. See error **Expected behavior** Expecting the SSL cert to be added **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. --> **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. -->
Author
Owner

@github-actions[bot] commented on GitHub (Oct 26, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:2439175013 --> @github-actions[bot] commented on GitHub (Oct 26, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@chrwei commented on GitHub (Oct 27, 2024):

I had this issue with digitialocean too, i believe it's the same problem.

Manually running the command fails, but manually running it though the python venv succeeds. My "fix" is to change internal/certificate.js and edit the command variable to be

const certbotCommand = '/opt/certbot/bin/python /opt/certbot/bin/certbot';

with this change it works via the UI.

seems to be something odd in how the venv is being called

<!-- gh-comment-id:2440212280 --> @chrwei commented on GitHub (Oct 27, 2024): I had this issue with digitialocean too, i believe it's the same problem. Manually running the command fails, but manually running it though the python venv succeeds. My "fix" is to change internal/certificate.js and edit the command variable to be ```const certbotCommand = '/opt/certbot/bin/python /opt/certbot/bin/certbot';``` with this change it works via the UI. seems to be something odd in how the venv is being called
Author
Owner

@github-actions[bot] commented on GitHub (Jul 4, 2025):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:3034205013 --> @github-actions[bot] commented on GitHub (Jul 4, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@chrwei commented on GitHub (Jul 4, 2025):

Unless something else has been done to correct the python venv content, I assume this issue still exists

<!-- gh-comment-id:3037385668 --> @chrwei commented on GitHub (Jul 4, 2025): Unless something else has been done to correct the python venv content, I assume this issue still exists
Author
Owner

@github-actions[bot] commented on GitHub (Feb 14, 2026):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:3900471526 --> @github-actions[bot] commented on GitHub (Feb 14, 2026): Issue is now considered stale. If you want to keep it open, please comment :+1:
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#2414
No description provided.