-
-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Problem updating cert #3767
Comments
I have a similar issue renewing certs with one.com. I registered the certs in august, and now i'ts time to renew, but it just fails. Edit: I have the same issue when requesting a new cert from the staging server. |
same here |
I have figured out why it doesn't work (for one.com) and the biggest things that needs fixing in this thread: #2103 Don't expect me to cook up a proper solution for this anytime soon. I have only used this project as a part of pfSense and I would have to do a lot of reading of this projects source code before I could implement a proper solution. It would be appreciated if someone else more experienced in this project wanted to pick up from here. Doing this process manually for the next year or so seems like it's going to take a shorter time than trying to learn how to fix the automated DNS api in the near future personally. I'm used to having to sign in every 30 days to no-ip.com to make sure they don't give up my free domain there anyways and that is already less work now that I registered a proper one.com domain instead. I am a bit disappointed that they don't provide a proper API for doing this though that's not going to break every time they redesign their webpage so I might just change DNS provider as well when my current adress expires... |
Steps to reproduce
Im using acme on a pfSense router but it does the same as using acme.sh on any linux machine.
And im getting some kind of error but i dont understand whats wrong. Has something changed at one.com or does it have something to do with lets encrypts CA expiring?
Debug log
The text was updated successfully, but these errors were encountered: