DNS challenge DYNU configuration

[suhrke]

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

Hello, I wanted to use the DNS challenge plugin Dynu, and this wants to get certbot_dns_dynu:dns_dynu_auth_token = YOUR_DYNU_AUTH_TOKEN

I replaced YOUR_DYNU_AUTH_TOKEN with my own api token at dynu.com

and got only

"Internal error" and "This section requires some knowledge about Certbot and its DNS plugins. Please consult the respective plugins documentation."

In the corresponding python script inside the container /opt/certbot/lib/python3.7/site-packages/certbot_dns_dynu/dns_dynu.py I found also only the reference to the dynu auth token. I use this DNS challenge on another platform (proxmox-ve) which uses auth-token and oauth2 Client-ID/secret what works properly. So I look for a way to configure this in nginx proxy manager properly, but found not any hint.

Nginx Proxy Manager Version

To Reproduce Steps to reproduce the behavior:

1. Go to '...' dynu.com, create the subdomain/address record for the affected certificate
2. create a new proxy with this dns name
3. go to SSL
4. request a new SSL certificate with LE
5. take "Use a DNS challenge"
6. choose "dynu"
7. put yout authentication token into the configuration field like certbot_dns_dynu:dns_dynu_auth_token = MY_OWN_DYNU_AUTH_TOKEN
8. put in yout LE account email
9. choose "I agree to .."
10. optional choose "Force SSL" and "HTTP/2 support"
11. choose "Save"

Expected behavior

correct pull a certificate from letsencrypt with dns challenge provided by dynu.com

Screenshots

Operating System

ubuntu 20.04 LTS / Docker version 20.10.7, build f0df350

Additional context