# \[ERROR\] Failed to get LetsEncrypt cert

**URL:** <https://forum.pritunl.com/t/error-failed-to-get-letsencrypt-cert/350>\
**Category:** Pritunl VPN\
**Tags:** pritunl\
**Created:** [August 30, 2022, 9:55pm UTC](https://forum.pritunl.com/t/error-failed-to-get-letsencrypt-cert/350 "2022-08-30T21:55:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![OWL\_DV](https://forum.pritunl.com/user_avatar/forum.pritunl.com/owl_dv/32/132_2.png) [@OWL\_DV](https://forum.pritunl.com/u/OWL_DV)\
**Post date:** [August 30, 2022, 9:55pm UTC](https://forum.pritunl.com/t/error-failed-to-get-letsencrypt-cert/350/1 "2022-08-30T21:55:26Z")

</div>

Hi all.  
After command _pritunl reset-ssl-cert_  
[ERROR] Failed to get LetsEncrypt cert

> **LOGS**
>
> [thriving-fields-6695][2022-08-30 21:41:41,386][INFO] Settings changed, restarting server…  
> ssl\_changed = false  
> cert\_changed = true  
> key\_changed = true  
> port\_changed = false  
> redirect\_server\_changed = false  
> reverse\_proxy\_changed = false  
> [thriving-fields-6695][2022-08-30 21:41:41,715][INFO] Server restarting…  
> [thriving-fields-6695][2022-08-30 21:41:41,740][INFO] Starting server  
> selinux\_context = “none”  
> [thriving-fields-6695][2022-08-30 21:41:41,745][INFO] Generating server certificate…  
> [thriving-fields-6695][2022-08-30 21:42:27,245][INFO] Parsing account key…  
> [thriving-fields-6695][2022-08-30 21:42:27,257][INFO] Parsing CSR…  
> [thriving-fields-6695][2022-08-30 21:42:27,265][INFO] Found domains: vultr-eu.XXXX.XXX  
> [thriving-fields-6695][2022-08-30 21:42:27,265][INFO] Getting directory…  
> [thriving-fields-6695][2022-08-30 21:42:27,652][INFO] Directory found!  
> [thriving-fields-6695][2022-08-30 21:42:27,652][INFO] Registering account…  
> [thriving-fields-6695][2022-08-30 21:42:28,568][INFO] Registered!  
> [thriving-fields-6695][2022-08-30 21:42:28,569][INFO] Creating new order…  
> [thriving-fields-6695][2022-08-30 21:42:29,661][INFO] Order created!  
> [thriving-fields-6695][2022-08-30 21:42:30,103][INFO] Verifying vultr-eu.XXXX.XXX…  
> [thriving-fields-6695][2022-08-30 21:42:33,829][ERROR] Failed to get LetsEncrypt cert  
> Traceback (most recent call last):  
> File “/usr/lib/pritunl/lib/python3.8/site-packages/pritunl/handlers/settings.py”, line 1072, in settings\_put  
> acme.update\_acme\_cert()  
> File “/usr/lib/pritunl/lib/python3.8/site-packages/pritunl/acme.py”, line 69, in update\_acme\_cert  
> cert = get\_acme\_cert(settings.app.acme\_key, csr)  
> File “/usr/lib/pritunl/lib/python3.8/site-packages/pritunl/acme.py”, line 41, in get\_acme\_cert  
> certificate = acmetiny.get\_crt(  
> File “/usr/lib/pritunl/lib/python3.8/site-packages/pritunl/acmetiny.py”, line 138, in get\_crt  
> raise ValueError(“Challenge did not pass for {0}: {1}”.format(domain, authorization))  
> ValueError: Challenge did not pass for vultr-eu.XXXX.XX: {‘identifier’: {‘type’: ‘dns’, ‘value’: ‘vultr-eu.XXXX.XX’}, ‘status’: ‘invalid’, ‘expires’: ‘2022-09-06T21:42:29Z’, ‘challenges’: [{‘type’: ‘http-01’, ‘status’: ‘invalid’, ‘error’: {‘type’: ‘urn:ietf:params:acme:error:unauthorized’, ‘detail’: ‘70.XXX.XXX.XXX: Invalid response from XXXXX://vultr-eu.XXXX.XX/.well-known/acme-challenge/XXX-XXXX: 404’, ‘status’: 403}, ‘url’: ‘XXXXX://acme-v02.api.letsencrypt.org/acme/chall-v3/XXXX/XXX’, ‘token’: ‘XXX-XXXX’, ‘validationRecord’: [{‘url’: ‘XXXX://vultr-eu.XXXX.XXX/.well-known/acme-challenge/XXX-XXXX’, ‘hostname’: ‘vultr-eu.XXXX.XXX’, ‘port’: ‘80’, ‘addressesResolved’: [‘70.XXX.XXX.XXX’], ‘addressUsed’: ‘70.XXX.XXX.XXX’}], ‘validated’: ‘2022-08-30T21:42:30Z’}]}  
> acme\_domain = “vultr-eu.XXXX.XX”

- hide domain XXXX.XX
- hide ip XXX.XXX.XXX
- hide link http XXXX
- hide link https XXXXX

thanks for the help

---

<div class="post-metadata">

**Author:** ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)\
**Post date:** [August 31, 2022, 12:51am UTC](https://forum.pritunl.com/t/error-failed-to-get-letsencrypt-cert/350/2 "2022-08-31T00:51:16Z")

</div>

This could be an issue with the firewall or DNS. The Lets Encrypt servers need access to HTTP port 80 on the Pritunl host and the domain name must resolve to the Pritunl host.
