NginxProxyManager / NginxProxyManager/nginx-proxy-manager
INWX Plugin not working
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Describe the bug
I'm getting this error message with the INWX plugin:
CommandError: Saving debug log to /tmp/letsencrypt-log/letsencrypt.log
Unsafe permissions on credentials configuration file: /etc/letsencrypt/credentials/credentials-8
Encountered exception during recovery: certbot.errors.PluginError: INWX login failed: ('There was a problem: Authentication error (Error code 2200)', {'code': 2200, 'msg': 'Authentication error', 'svTRID': '20250204-', 'runtime': 3.0283})
INWX login failed: ('There was a problem: Authentication error (Error code 2200)', {'code': 2200, 'msg': 'Authentication error', 'svTRID': '20250204-', 'runtime': 3.0275})
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.
at /app/lib/utils.js:16:13
at ChildProcess.exithandler (node:child_process:430:5)
at ChildProcess.emit (node:events:518:28)
at maybeClose (node:internal/child_process:1104:16)
at Socket. (node:internal/child_process:456:11)
at Socket.emit (node:events:518:28)
at Pipe. (node:net:343:12)
More Info:
The directory /etc/letsencrypt/credentials is empty
The plugin's config file is stored in /opt/certbot/lib/python3.11/site-packages/etc/letsencrypt/inwx.cfg
The settings entered in the UI:
dns_inwx_url = https://api.domrobot.com/xmlrpc/
dns_inwx_username = MY_USERNAME
dns_inwx_password = MY_PASSWORD
dns_inwx_shared_secret = your_shared_secret optional
Nginx Proxy Manager Version
v2.12.2
To Reproduce
Steps to reproduce the behavior:
- Go to 'SSL Certificates'
- Click on 'Add SSL Certificate'
- Enter 'Domain Names', 'Email Address for Let's Encrypt'
- Check 'Use a DNS Challenge'
- Select 'INWX' from the dropdown menu
- Check 'I Agree to the LE ToS'
- Click on 'Save'
- The error message from above is displayed
Expected behavior
Authentication to not fail
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the INWX settings in the SSL certificate flow and the generated /opt/certbot/lib/python3.11/site-packages/etc/letsencrypt/inwx.cfg file, then inspect the error path at /app/lib/utils.js. Reproduce the INWX DNS challenge with the reported settings and determine whether the generated credentials are accepted; done means authentication succeeds without the PluginError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, typescript
- Domain
- api, devops, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100