› VitalPBX Community Support › General Discussion › Let's Encrypt issue after upgrade to 2.4.0-5
- This topic has 28 replies, 4 voices, and was last updated 11 months, 1 week ago by
PitzKey.
- Post
-
- February 19, 2020 at 3:23 pm
Hello,
Let’s Encrypt cert stopped renewing after I upgraded to 2.4.0-5.
When I click update on certificate, I get the attached error.
I tried disabling firewall and it didn’t seem to correct the issue.
Thanks!
-G.
0
- Replies
-
- February 19, 2020 at 6:02 pm
- February 19, 2020 at 6:04 pm
- February 19, 2020 at 6:34 pm
- February 19, 2020 at 6:40 pm
- February 19, 2020 at 6:44 pm
- February 19, 2020 at 7:22 pm
Posted by: @ing-joserivera26Try the following, enable the access of your PBX through HTTP (Port 80), then, delete the let’s encrypt certificate, and create it again.
Did not work for me:
valid until 1970-01-010- February 19, 2020 at 7:44 pm
- February 19, 2020 at 9:41 pm
Posted by: @mo10Posted by: @ing-joserivera26Try the following, enable the access of your PBX through HTTP (Port 80), then, delete the let’s encrypt certificate, and create it again.
Did not work for me:
valid until 1970-01-01Did you get some error on the web UI when trying to regenerate the certificate?
0- February 19, 2020 at 9:49 pm
- February 19, 2020 at 9:58 pm
- February 19, 2020 at 10:04 pm
Nothing happens.
[root@vitalpbx ~]# /usr/share/ombutel/scripts/lets_encrypt
[root@vitalpbx ~]# /usr/share/ombutel/scripts/lets_encrypt
[root@vitalpbx ~]# /usr/share/ombutel/scripts/lets_encryptBefore deleting the Cert this showed up:
[root@vitalpbx ~]# /usr/share/ombutel/scripts/lets_encrypt
CertCron: Invalid response
header: HTTP/1.1 404 Not Found
Server: nginx
Date: Wed, 19 Feb 2020 22:00:41 GMT
Content-Type: application/problem+json
Content-Length: 111
Connection: keep-alive
Cache-Control: public, max-age=0, no-cache
Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
body: {
"type": "urn:ietf:params:acme:error:malformed",
"detail": "No order for ID 1807638746",
"status": 4040- February 19, 2020 at 10:38 pm
- February 20, 2020 at 1:19 pm
It could be. Can’t tell. Had a similar issue where I couldn’t update because of firewall and @giovanni-v suggested disabling firewall in console.
0- February 20, 2020 at 1:21 pm
Posted by: @mo10Posted by: @theg-manAre you sure you are not blocking it with firewall?
Try running
systemctl stop firewalld
from console and try adding cert again.
Wow, this helped. Thanks. How is that possible?!
Maybe because of Geo-Firewall?
Please Check! Thank you.
0
Tagged: let's encrypt
- You must be logged in to reply to this topic.