Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] No credential for dnshome DNS challenge #425

Open
GismoNo1 opened this issue Dec 11, 2024 · 1 comment
Open

[BUG] No credential for dnshome DNS challenge #425

GismoNo1 opened this issue Dec 11, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@GismoNo1
Copy link

Thanks for the awesome Zoraxy Proxy Manager!

When I try to set up an dns challenge for dnshome.de (supported by lego) there are no fields in the acme-tool to enter my credentials. When trying to issue a certificate this results in an error, because the credentials are missing.

Bildschirmfoto 2024-12-11 um 13 37 04

For the other by lego supported dns provider there are seperate fields for user, password, api_key etc. in the acme-tool Hope you can fix this. Or is there any workaround?

@GismoNo1 GismoNo1 added the bug Something isn't working label Dec 11, 2024
@tobychui
Copy link
Owner

@GismoNo1

I have checked the automatic generated code for the ACME provider fields and seems the lego implementation is using a string map which the UI code generator cannot parse.

In mod/acme/acmedns/providers.json

 "dnshomede": {
  "Name": "dnshomede",
  "ConfigableFields": [
   {
    "Title": "PropagationTimeout",
    "Datatype": "time.Duration"
   },
   {
    "Title": "PollingInterval",
    "Datatype": "time.Duration"
   }
  ],
  "HiddenFields": [
   {
    "Title": "Credentials",
    "Datatype": "map[string]string" //As this is not a key-value set, the UI generator can't generate a web-form for it
   },
   {
    "Title": "HTTPClient",
    "Datatype": "*http.Client"
   }
  ]
 },

I guess there isn't anything I can help with this situation. If you would love to get dnshome.de supported in Zoraxy, please create a issue / PR on lego repo and ask them to replace this (somewhat poor) implementation to a proper key-value fields like string or int.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants