Does not renew certificate and does not appear proxy when clicking #1270
Comments
|
Please try what is in section NPM admin page is staying blank or behaving weirdly in issue #1271 and see if anything changes. It would also be useful to see if any error show up in the logs of npm. How to get them is also described in the previously mentioned issue. If you would just like to go back to an older verison of NPM this is possible by utilizing the docker image tags. Just change Edit: I have transferred your logs from the other issue to here. Could you tell me if you use the DNS challenge for any of your certificates? Or are they all just http challenge? |
|
I noticed something. If I use IP:81 NPM works fine, but I can't renew the certificate, but if I was using it as I was using it, an npm.mydomin domain doesn't work correctly. I didn't quite understand what you meant by that... I ordered it renewed and it won't.
|
|
When creating an SSL certificate there is a toggle enabling the dns challenge. |
|
I never used this option. |
|
Hm, the letsencrypt logs would be useful. Please execute |
|
|
Renewing wildcard certificate also fail here, issued via the Cloudflare API DNS Challenge fails with a mixture of errors: Internal Error or timeout. The docker logs are: The letsencrypt logs are: I have also tried using a normal LE certificate, but when issuring it errors out with the same types of errors, but now includes DNS Challenge errors (error logs below) Saving debug log to /var/log/letsencrypt/letsencrypt.log I also have to log into the container and kill the certbot process after each attempt to renew, as it never terminates itself. I am running NPM version 2.9.6 Never had these problems previously, only with 2.9.x |
|
Hm, both of your logs seem to not really show anything unusual, so I'm really not sure what the problem could be. Are there more logs which actually show some error? Maybe the file |
|
I went to add a new proxy to my NPM earlier today and found that both of my NPM instances haven't renewed certs in over a month. |
|
Certbot only renews the certificate if it expires within 30 days. LetsEncrypt certificates are valid for 90 days, so a certificate should only be renewed every two months. So a certificate having been renewed over a month ago is totally normal. There is also a bug where the displayed renewal date is not updated in the admin panel when one of the certificate renewals failed, while all other certificates are actually renewed correctly. But as v3 is currently the priority and it switches to acme.sh, this will most likely not be fixed in v2. |
|
For me when I click on "renew" on a certificate, it says "Please wait..." and after a few minutes the GUI says "timeout" . The app log says Also, the GUI was broken except for being able to log in but I fixed that by clearing the browser cache. |
|
any updates? from the docker image would expect the main functionality to work |
|
No, no updates since there is not enough information on what the problem could be. |
|
The problem magically vanished from my installation. It seems the error provided is too vague to effectively troubleshoot. |
|
As it turned out, my problems were related to the closed 80 port, but I noticed that the certificate update process does not exit after the update failed, I think this is due to the fact that the users above received an error cert bot instance already running. |
|
Issue is now considered stale. If you want to keep it open, please comment 👍 |
Version 2.9.6
1- After logging in, if I click on the 13 Proxy Hosts link, nothing happens.
2 - When I try to renew any certificate, I get an error.
3 - Ports 80 and 443 are open on my firewall
4 - When I run some function, delete an SSL, disable a proxy, it doesn't update, I have to press F5 to see the change.
5 - It's very buggy, after I delete an SSL, it doesn't update, if I update (F5), add everything and when I click on the SSL Certificates link, nothing opens, I have to log off and log in again to appear.
This version is well buggy.
Which versions are available? how do i use a previous version?
Logs
The text was updated successfully, but these errors were encountered: