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

[FEATURE] Improve error message Lets Encrypt #1804

Closed
jaapmarcus opened this issue May 14, 2021 · 2 comments
Closed

[FEATURE] Improve error message Lets Encrypt #1804

jaapmarcus opened this issue May 14, 2021 · 2 comments
Labels
feature New feature or request web Issues related to web components

Comments

@jaapmarcus
Copy link
Member

Is your feature request related to a problem? Please describe.
Current error message in Hestia is worth less. Users are required to check log files an if it is not an sys admin. They don't have the correct access rights to see them

Describe the solution you'd like
Current message is something like:
"type": "urn:ietf:params:acme:error:malformed",
"detail": "Unable to update challenge :: authorization must be pending",
"status": 400

How ever if you follow in "step" for
{
"type": "http-01",
"status": "pending",
"url": "https://acme-v02.api.letsencrypt.org/acme/chall-v3/12520447717/scDRXA",
"token": "9yriok5bpLtV__m-rZ8f2tQmrfeQli0tCxSj4iNkv2Y"
}

You would normally see an error message where an Ip is unable to resolve and so on. This error has more meaning then the first one.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
There are no alternatives except give every user the knowlegde to how to debug.

@jaapmarcus jaapmarcus added feature New feature or request web Issues related to web components labels May 14, 2021
@jlguerrerosanz
Copy link
Contributor

What we could do:

  1. parse the output of: https://acme-v02.api.letsencrypt.org/acme/chall-v3/12520447717/scDRXA" and show it to the user
  2. Tell the user to visit: https://acme-v02.api.letsencrypt.org/acme/chall-v3/12520447717/scDRXA", for more info
  3. show the content of the LE-XXXX-XXXX.log logfile
  4. show the path to the LE-XXXX-XXXX.log logfile

@jaapmarcus
Copy link
Member Author

4 is no option as non admin users don’t have access
3. Have seen to many users unable to read the logs so it will still have the issues
2. If we go trough the issue finding this link 1 should be more use full alternative we can show the link if the detection fails

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request web Issues related to web components
Projects
None yet
Development

No branches or pull requests

2 participants