-
-
Notifications
You must be signed in to change notification settings - Fork 611
ACME error - Could not find solver for: tls-alpn-01 #407
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
It seems that the error is returned by the dns provider, have you try to issue the certificate again, or try another dns prodiver? |
I've installed acme.sh and got certificate (using same API keys) after issuing: |
You can try https://github.com/go-acme/lego with CLI mode, in nginxui we use this tool to obtain certificate, if the problem still exists maybe we should turn to the author of that project for help. |
What version of lego package do you use? In debian there's available lego/stable 4.9.1-1 amd64. |
v4.16.1 |
So, after issuing command:
Thus, it seems like issue is within nginxui... |
I'm unable to get wildcard certificates, too. But they worked in the past with nginx-ui. |
Please provide the logs, thanks! |
Did you use nginx to proxy the nginx-ui? |
I will upgrade lego to the latest version(v4.17.3) in next beta verison of nginx-ui, but I can't ensure this will solve your problem. |
Ok, I've re-applied your Nginx config for nginxui and now I receive messages but dashboard graphs (except Disk I/O) remaining empty... |
Did you try to reinstall nginx-ui? I mean remove the database.db and app.ini in /usr/local/etc/nginx-ui, and use the installation script to reinstall it. |
That's what I did:
Content of app.ini:
And reinstallation didn't change anything... |
Did you visit http://ip:port/install in the browser? |
Yes, of course. User and database were created at that step...
|
Hi @Green2Matter, I updated the lego version to v4.17.3 in the nginx UI v2-beta.25, and you can try this version to see if the problem still persists. |
Hi @0xJacky unfortunately it didn't help. Still there's the same error... |
I am sorry about that, can you please provide us the logs of Nginx UI? By executing the following command:
|
logs (sanitised) when trying to issue cert:
For a test with standalone lego, I was using exactly same ovh credentials... |
Hello @Green2Matter, I apologize for keeping you waiting for so long. I have just synchronized the lego configuration file and noticed that there are updates regarding ovh in lego. I have now released a new Nginx UI v2.0.0-beta.25. You can directly reinstall v2.0.0-beta.25 through the Online Update and restart Nginx UI, or reinstall using the script, then re-add the ovh DNS credentials. You should see new options like OVH_CLIENT_ID and OVH_CLIENT_SECRET. Please ensure that the environment variables in the DNS Credentials you add are consistent with the environment variables you use when executing lego in the terminal. |
Hi @0xJacky, thanks for an update but I'm a bit confused.
Lego doesn't send command understandable for OVH servers... |
Please try the following steps:
See if you can successfully request the certificate this time. |
Hi @Green2Matter, can you try this method? I think we're very close to the casue of the issue. |
Hi @0xJacky!
|
Great! I’ll add a switcher at an appropriate location for users to set LEGO_DISABLE_CNAME_SUPPORT. This will allow users who use CNAME domains and cannot issue certificates to try disabling LEGO’s CNAME support and obtain certificates correctly. Reference: Traefik Community - Traefik cannot issue certificate for CNAME’d wildcard domain. For now, you can exit nginx-ui, restart it using systemctl, and wait for the next version of the Nginx UI. |
Describe the bug
Not able to create SSL certificate using builtin ACME client
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Create certificate
Info (please complete the following information):

The text was updated successfully, but these errors were encountered: