mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #3644] ClouDNS throws unrecognized arguments error #2414
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#2414
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 @dreed47 on GitHub (Mar 20, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3644
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
ClouDNS throws unrecognized arguments error.
Nginx Proxy Manager Version
v2.11.1
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expecting the SSL cert to be added
Screenshots
Operating System
Additional context
@github-actions[bot] commented on GitHub (Oct 26, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@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
@github-actions[bot] commented on GitHub (Jul 4, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍
@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
@github-actions[bot] commented on GitHub (Feb 14, 2026):
Issue is now considered stale. If you want to keep it open, please comment 👍