[GH-ISSUE #5143] All-Inkl DNS Challenge fails, Property "dns_kas_kas_user" and Property "dns_kas_kas_password" not found #3127

Closed
opened 2026-02-26 07:37:55 +03:00 by kerem · 12 comments
Owner

Originally created by @FlyingT on GitHub (Jan 14, 2026).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5143

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
All-Inkl DNS Challenge fails, it appears like the Credentials File Content doesnt get passed through the command

Nginx Proxy Manager Version
v2.13.6

To Reproduce
Steps to reproduce the behavior:

  1. Go to Certificates
  2. Click on Add Certificate > Let's Encryot via DNS
  3. Add Domain Name *.mydomain.de
  4. Select Key Type RSA 2048
  5. Select DNS Provider All-Inkl
  6. Enter Credentials File Content
    dns_kas_user = w0123456
    dns_kas_password = secure-password-123
  7. Set Propagation Seconds to 600

I can login with the same credentials to https://kas.all-inkl.com/ just fine, so they are correct.

Expected behavior
I receive an certificate

Log
[1/14/2026] [8:18:49 AM] [Nginx ] › ℹ info Reloading Nginx
[1/14/2026] [8:18:49 AM] [Certbot ] › ▶ start Installing kas...
[1/14/2026] [8:18:49 AM] [Certbot ] › ☒ complete Installed kas
[1/14/2026] [8:18:49 AM] [SSL ] › ℹ info Requesting LetsEncrypt certificates via All-Inkl for Cert #7: *.mydomain.de
[1/14/2026] [8:18:49 AM] [SSL ] › ℹ info Command: certbot certonly --config /etc/letsencrypt.ini --work-dir /tmp/letsencrypt-lib --logs-dir /data/logs --cert-name npm-7 --agree-tos -m MY@MAIL.de --preferred-challenges dns --domains *.mydomain.de --authenticator dns-kas --dns-kas-credentials /etc/letsencrypt/credentials/credentials-7 --dns-kas-propagation-seconds 600 --key-type ecdsa
[1/14/2026] [8:18:51 AM] [Nginx ] › ℹ info Reloading Nginx
[1/14/2026] [8:18:51 AM] [Express ] › ⚠ warning Saving debug log to /data/logs/letsencrypt.log
Missing properties in credentials configuration file /etc/letsencrypt/credentials/credentials-7:

  • Property "dns_kas_kas_user" not found (should be KAS username/login).
  • Property "dns_kas_kas_password" not found (should be KAS password)

Operating System
Ubuntu Server 24.04.3 LTS

Additional context
Firefox 146.0.1, Portainer Community 2.33.5 LTS

Originally created by @FlyingT on GitHub (Jan 14, 2026). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5143 **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** All-Inkl DNS Challenge fails, it appears like the Credentials File Content doesnt get passed through the command **Nginx Proxy Manager Version** v2.13.6 **To Reproduce** Steps to reproduce the behavior: 1. Go to Certificates 2. Click on Add Certificate > Let's Encryot via DNS 3. Add Domain Name *.mydomain.de 4. Select Key Type RSA 2048 5. Select DNS Provider All-Inkl 6. Enter Credentials File Content dns_kas_user = w0123456 dns_kas_password = secure-password-123 7. Set Propagation Seconds to 600 I can login with the same credentials to https://kas.all-inkl.com/ just fine, so they are correct. **Expected behavior** I receive an certificate **Log** [1/14/2026] [8:18:49 AM] [Nginx ] › ℹ info Reloading Nginx [1/14/2026] [8:18:49 AM] [Certbot ] › ▶ start Installing kas... [1/14/2026] [8:18:49 AM] [Certbot ] › ☒ complete Installed kas [1/14/2026] [8:18:49 AM] [SSL ] › ℹ info Requesting LetsEncrypt certificates via All-Inkl for Cert #7: *.mydomain.de [1/14/2026] [8:18:49 AM] [SSL ] › ℹ info Command: certbot certonly --config /etc/letsencrypt.ini --work-dir /tmp/letsencrypt-lib --logs-dir /data/logs --cert-name npm-7 --agree-tos -m MY@MAIL.de --preferred-challenges dns --domains *.mydomain.de --authenticator dns-kas --dns-kas-credentials /etc/letsencrypt/credentials/credentials-7 --dns-kas-propagation-seconds 600 --key-type ecdsa [1/14/2026] [8:18:51 AM] [Nginx ] › ℹ info Reloading Nginx [1/14/2026] [8:18:51 AM] [Express ] › ⚠ warning Saving debug log to /data/logs/letsencrypt.log Missing properties in credentials configuration file /etc/letsencrypt/credentials/credentials-7: * Property "dns_kas_kas_user" not found (should be KAS username/login). * Property "dns_kas_kas_password" not found (should be KAS password) **Operating System** Ubuntu Server 24.04.3 LTS **Additional context** Firefox 146.0.1, Portainer Community 2.33.5 LTS
kerem 2026-02-26 07:37:55 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@Kaputtnique commented on GitHub (Jan 14, 2026):

why no ECDSA 256? thats working for me. but i have no wildcard configured.

also, why "dns_kas_kas_user"

dns_kas_user = your_kas_user
dns_kas_password = your_kas_password
<!-- gh-comment-id:3748563563 --> @Kaputtnique commented on GitHub (Jan 14, 2026): why no ECDSA 256? thats working for me. but i have no wildcard configured. also, why "dns_kas_kas_user" ``` dns_kas_user = your_kas_user dns_kas_password = your_kas_password ```
Author
Owner

@Kaputtnique commented on GitHub (Jan 14, 2026):

hmm, tested another ddns name and that throws same error.. :-D weird

my awnser is "dns_kas_kas_user" too -- but the first one worked like charme

<!-- gh-comment-id:3748589529 --> @Kaputtnique commented on GitHub (Jan 14, 2026): hmm, tested another ddns name and that throws same error.. :-D weird my awnser is "dns_kas_kas_user" too -- but the first one worked like charme
Author
Owner

@FlyingT commented on GitHub (Jan 14, 2026):

also, why "dns_kas_kas_user"

That actually seems to be the issue!

The Enter Credentials File Content preset gives you this:

dns_kas_user = your_kas_user
dns_kas_password = your_kas_password

But certbot is expecting dns_kas_kas_user and dns_kas_kas_password !
So the certbot command needs to be fixed to use the correct variables.

I just confirmed it by manually changing the Enter Credentials File Content to this, notice the double kas:

dns_kas_kas_user = your_kas_user
dns_kas_kas_password = your_kas_password

And it worked!
@jc21 should be an easy fix, just a typo :)

<!-- gh-comment-id:3748741754 --> @FlyingT commented on GitHub (Jan 14, 2026): > also, why "dns_kas_kas_user" That actually seems to be the issue! The Enter Credentials File Content preset gives you this: ``` dns_kas_user = your_kas_user dns_kas_password = your_kas_password ``` But certbot is expecting `dns_kas_kas_user` and `dns_kas_kas_password` ! So the certbot command needs to be fixed to use the correct variables. I just confirmed it by manually changing the Enter Credentials File Content to this, notice the double **kas**: ``` dns_kas_kas_user = your_kas_user dns_kas_kas_password = your_kas_password ``` And it worked! @jc21 should be an easy fix, just a typo :)
Author
Owner

@Kaputtnique commented on GitHub (Jan 14, 2026):

yeah, but it worked once for me lul. and then not. X__x

<!-- gh-comment-id:3748786158 --> @Kaputtnique commented on GitHub (Jan 14, 2026): yeah, but it worked once for me lul. and then not. X__x
Author
Owner

@mobilandi commented on GitHub (Jan 14, 2026):

@FlyingT Thanks for reporting the bug and finding the issue. I built the all-inkl certbot plugin and made an error with the naming convention that certbot expects. I will fix it today. It's no task for jc21, since the certbot plugin is independent from npm.

Just for the technical explanation:
I had to rename the plugin before releasing it on PyPI, because there was already the name reserverd for "certbot_dns_allinkl". Even though there was no release for it. That's why I had to rename some variables and made a careless mistake there.

When it's fixed I will let you know how to get the updated version of the plugin.

<!-- gh-comment-id:3750659603 --> @mobilandi commented on GitHub (Jan 14, 2026): @FlyingT Thanks for reporting the bug and finding the issue. I built the all-inkl certbot plugin and made an error with the naming convention that certbot expects. I will fix it today. It's no task for jc21, since the certbot plugin is independent from npm. Just for the technical explanation: I had to rename the plugin before releasing it on PyPI, because there was already the name reserverd for "certbot_dns_allinkl". Even though there was no release for it. That's why I had to rename some variables and made a careless mistake there. When it's fixed I will let you know how to get the updated version of the plugin.
Author
Owner

@mobilandi commented on GitHub (Jan 14, 2026):

@FlyingT Please restart your container and give it another try. I updated the certbot plugin and npm should pull the newest minor release on every start. Would be nice if you can give me any feedback if it worked for you.

<!-- gh-comment-id:3751126704 --> @mobilandi commented on GitHub (Jan 14, 2026): @FlyingT Please restart your container and give it another try. I updated the certbot plugin and npm should pull the newest minor release on every start. Would be nice if you can give me any feedback if it worked for you.
Author
Owner

@FlyingT commented on GitHub (Jan 14, 2026):

@FlyingT Please restart your container and give it another try. I updated the certbot plugin and npm should pull the newest minor release on every start. Would be nice if you can give me any feedback if it worked for you.

I will try it tomorrow and ping you :)

<!-- gh-comment-id:3751228357 --> @FlyingT commented on GitHub (Jan 14, 2026): > [@FlyingT](https://github.com/FlyingT) Please restart your container and give it another try. I updated the certbot plugin and npm should pull the newest minor release on every start. Would be nice if you can give me any feedback if it worked for you. I will try it tomorrow and ping you :)
Author
Owner

@FlyingT commented on GitHub (Jan 16, 2026):

@mobilandi It now works!

<!-- gh-comment-id:3758674314 --> @FlyingT commented on GitHub (Jan 16, 2026): @mobilandi It now works!
Author
Owner

@mobilandi commented on GitHub (Jan 16, 2026):

Great, thanks for your feedback:)

<!-- gh-comment-id:3758902217 --> @mobilandi commented on GitHub (Jan 16, 2026): Great, thanks for your feedback:)
Author
Owner

@listiges-kaenguru commented on GitHub (Feb 18, 2026):

Hi @mobilandi !


EDIT: I just found the problem. I hat 2 problems. My password had illegal characters and 2FA does not seem to be supported.

app-1 | zeep.exceptions.Fault: kas_auth_type_disabled


No luck on my site. Do you have any idea what´s wrong? It says "str expected, not list"

app-1  | [2/18/2026] [10:24:40 PM] [Certbot  ] › ▶  start     Installing kas...
app-1  | [2/18/2026] [10:24:43 PM] [Remote Version] › ℹ  info      Fetching https://api.github.com/repos/NginxProxyManager/nginx-proxy-manager/releases/latest
app-1  | [2/18/2026] [10:24:45 PM] [Certbot  ] › ☒  complete  Installed kas
app-1  | [2/18/2026] [10:24:45 PM] [SSL      ] › ℹ  info      Requesting LetsEncrypt certificates via All-Inkl for Cert #33: *.mypage.de
app-1  | [2/18/2026] [10:24:45 PM] [SSL      ] › ℹ  info      Command: certbot certonly --config /etc/letsencrypt.ini --work-dir /tmp/letsencrypt-lib --logs-dir /data/logs --cert-name npm-33 --agree-tos -m info@mypage.de --preferred-challenges dns --domains *.mypage.de --authenticator dns-kas --dns-kas-credentials /etc/letsencrypt/credentials/credentials-33 --dns-kas-propagation-seconds 600 --key-type ecdsa
app-1  | [2/18/2026] [10:24:47 PM] [Nginx    ] › ℹ  info      Reloading Nginx
app-1  | [2/18/2026] [10:24:47 PM] [Express  ] › ⚠  warning   Saving debug log to /data/logs/letsencrypt.log
app-1  | Encountered exception during recovery: TypeError: str expected, not list
app-1  | An unexpected error occurred:
app-1  | TypeError: str expected, not list
<!-- gh-comment-id:3923320052 --> @listiges-kaenguru commented on GitHub (Feb 18, 2026): Hi @mobilandi ! --- > EDIT: I just found the problem. I hat 2 problems. My password had illegal characters and 2FA does not seem to be supported. `app-1 | zeep.exceptions.Fault: kas_auth_type_disabled` --- No luck on my site. Do you have any idea what´s wrong? It says "str expected, not list" ``` app-1 | [2/18/2026] [10:24:40 PM] [Certbot ] › ▶ start Installing kas... app-1 | [2/18/2026] [10:24:43 PM] [Remote Version] › ℹ info Fetching https://api.github.com/repos/NginxProxyManager/nginx-proxy-manager/releases/latest app-1 | [2/18/2026] [10:24:45 PM] [Certbot ] › ☒ complete Installed kas app-1 | [2/18/2026] [10:24:45 PM] [SSL ] › ℹ info Requesting LetsEncrypt certificates via All-Inkl for Cert #33: *.mypage.de app-1 | [2/18/2026] [10:24:45 PM] [SSL ] › ℹ info Command: certbot certonly --config /etc/letsencrypt.ini --work-dir /tmp/letsencrypt-lib --logs-dir /data/logs --cert-name npm-33 --agree-tos -m info@mypage.de --preferred-challenges dns --domains *.mypage.de --authenticator dns-kas --dns-kas-credentials /etc/letsencrypt/credentials/credentials-33 --dns-kas-propagation-seconds 600 --key-type ecdsa app-1 | [2/18/2026] [10:24:47 PM] [Nginx ] › ℹ info Reloading Nginx app-1 | [2/18/2026] [10:24:47 PM] [Express ] › ⚠ warning Saving debug log to /data/logs/letsencrypt.log app-1 | Encountered exception during recovery: TypeError: str expected, not list app-1 | An unexpected error occurred: app-1 | TypeError: str expected, not list ```
Author
Owner

@mobilandi commented on GitHub (Feb 19, 2026):

@listiges-kaenguru
The KAS API of all-inkl sadly doesn't support 2FA if I didn't miss anything. I also had to create another account without 2FA just for those DNS changes.
Do I understand correctly, that your ppassword has characters that are legal for login on the all-inkl website but not for DNS challenge?

<!-- gh-comment-id:3926274834 --> @mobilandi commented on GitHub (Feb 19, 2026): @listiges-kaenguru The KAS API of all-inkl sadly doesn't support 2FA if I didn't miss anything. I also had to create another account without 2FA just for those DNS changes. Do I understand correctly, that your ppassword has characters that are legal for login on the all-inkl website but not for DNS challenge?
Author
Owner

@listiges-kaenguru commented on GitHub (Feb 19, 2026):

@mobilandi
Yes that´s correct. Could not figure out which character caused the problem.

I can prove that ! and * are no problem. These worked for me.

<!-- gh-comment-id:3926315705 --> @listiges-kaenguru commented on GitHub (Feb 19, 2026): @mobilandi Yes that´s correct. Could not figure out which character caused the problem. I can prove that ! and * are no problem. These worked for me.
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#3127
No description provided.