# I'm having trouble generating the let's encrypt certificate **URL:** \ **Category:** Help\ **Created:** [May 11, 2026, 2:03pm UTC](https://community.letsencrypt.org/t/im-having-trouble-generating-the-lets-encrypt-certificate/247159 "2026-05-11T14:03:23Z")\ **Posts on this page:** 18\ **Page:** 2
**Author:** ![pipa\_85](https://avatars.discourse-cdn.com/v4/letter/p/90db22/32.png) [@pipa\_85](https://community.letsencrypt.org/u/pipa_85)\ **Post date:** [May 14, 2026, 10:21am UTC](https://community.letsencrypt.org/t/im-having-trouble-generating-the-lets-encrypt-certificate/247159/21 "2026-05-14T10:21:10Z")
we don't have a record for studio.openedx.univ-bejaia.dz in the DNS. We configured the DNS as follows: Internal DNS openedx IN A our internal IP address \*.openedx CNAME openedx.univ-bejaia.dz. External DNS openedx A 41.111.207.114 \*.openedx CNAME openedx.univ-bejaia.dz. should we also add in the DNS the following sub domains ? studio.openedx.univ-bejaia.dz apps.openedx.univ-bejaia.dz meilisearch.openedx.univ-bejaia.dz ---
**Author:** ![pipa\_85](https://avatars.discourse-cdn.com/v4/letter/p/90db22/32.png) [@pipa\_85](https://community.letsencrypt.org/u/pipa_85)\ **Post date:** [May 14, 2026, 1:16pm UTC](https://community.letsencrypt.org/t/im-having-trouble-generating-the-lets-encrypt-certificate/247159/22 "2026-05-14T13:16:40Z")
When I ran the command below, I found no service listening on port 443. **(env) openedx@openedx:~$ nc -zv localhost 443** **localhost [127.0.0.1] 443 (https) : Connection refused** The command below also returns nothing. **(env) openedx@openedx:~$ ss -tulpn | grep ':80|:443'** **(env) openedx@openedx:~$** The caddy doesn't seem to have a port ![docker ps](https://global.discourse-cdn.com/letsencrypt/original/3X/6/3/635f58ef4a765caf929c2684df14b14d5bb39c53.png) ---
**Author:** ![danb35](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/danb35/32/70869_2.png) [@danb35](https://community.letsencrypt.org/u/danb35)\ **Post date:** [May 14, 2026, 1:25pm UTC](https://community.letsencrypt.org/t/im-having-trouble-generating-the-lets-encrypt-certificate/247159/23 "2026-05-14T13:25:57Z")
> [@pipa\_85](#): > > The caddy doesn't seem to have a port You should probably expose one, then. Two, really: 80 and 443 (and 443/udp). Consult the Caddy docs or support channels for more on how to do that. ---
**Author:** ![pipa\_85](https://avatars.discourse-cdn.com/v4/letter/p/90db22/32.png) [@pipa\_85](https://community.letsencrypt.org/u/pipa_85)\ **Post date:** [May 14, 2026, 3:00pm UTC](https://community.letsencrypt.org/t/im-having-trouble-generating-the-lets-encrypt-certificate/247159/24 "2026-05-14T15:00:50Z")
I solved the problem but I still can't generate a certificate: Can you help me fix the problem ? ![dockerps](https://global.discourse-cdn.com/letsencrypt/original/3X/7/8/78064e256def694b14153675b6e0d7681be89a6f.png) bellow some of the los generated by caddy (I ​​apologize for the length of the message): caddy-1 | {"level":"error","ts":1778768831.1829667,"logger":"tls.obtain","msg":"could not get certificate from issuer","identifier":"openedx.univ-bejaia.dz","issuer":"acme-v02.api.letsencrypt.org-directory","error":"HTTP 400 urn:ietf:params:acme:error:connection - 41.111.207.114: Fetching [https://openedx.univ-bejaia.dz:443/.well-known/acme-challenge/MDDB9NumYyRPMF23cvmNHlZ8oLWl5w\_00fZa9PuSOgQ:](https://openedx.univ-bejaia.dz:443/.well-known/acme-challenge/MDDB9NumYyRPMF23cvmNHlZ8oLWl5w_00fZa9PuSOgQ:) Error getting validation data"} caddy-1 | {"level":"warn","ts":1778768831.1830883,"logger":"http","msg":"missing email address for ZeroSSL; it is strongly recommended to set one for next time"} caddy-1 | {"level":"error","ts":1778768831.8087902,"logger":"tls.obtain","msg":"could not get certificate from issuer","identifier":"openedx.univ-bejaia.dz","issuer":"acme.zerossl.com-v2-DV90","error":"account pre-registration callback: failed getting EAB credentials: HTTP 422: caddy\_legacy\_user\_removed (code 2977)"} caddy-1 | {"level":"error","ts":1778768831.80901,"logger":"tls.obtain","msg":"will retry","error":"[openedx.univ-bejaia.dz] Obtain: account pre-registration callback: failed getting EAB credentials: HTTP 422: caddy\_legacy\_user\_removed (code 2977)","attempt":1,"retrying\_in":60,"elapsed":10.195853689,"max\_duration":2592000} caddy-1 | {"level":"error","ts":1778768832.1108418,"logger":"http.acme\_client","msg":"challenge failed","identifier":"meilisearch.openedx.univ-bejaia.dz","challenge\_type":"http-01","problem":{"type":"urn:ietf:params:acme:error:connection","title":"","detail":"41.111.207.114: Fetching [https://meilisearch.openedx.univ-bejaia.dz:443/.well-known/acme-challenge/TeRMrgTMidDLvBUErpt5jjNERFCAjSxAHHMgG1QXn7Q:](https://meilisearch.openedx.univ-bejaia.dz:443/.well-known/acme-challenge/TeRMrgTMidDLvBUErpt5jjNERFCAjSxAHHMgG1QXn7Q:) Error getting validation data","instance":"","subproblems":}} caddy-1 | {"level":"error","ts":1778768832.11089,"logger":"http.acme\_client","msg":"validating authorization","identifier":"meilisearch.openedx.univ-bejaia.dz","problem":{"type":"urn:ietf:params:acme:error:connection","title":"","detail":"41.111.207.114: Fetching [https://meilisearch.openedx.univ-bejaia.dz:443/.well-known/acme-challenge/TeRMrgTMidDLvBUErpt5jjNERFCAjSxAHHMgG1QXn7Q:](https://meilisearch.openedx.univ-bejaia.dz:443/.well-known/acme-challenge/TeRMrgTMidDLvBUErpt5jjNERFCAjSxAHHMgG1QXn7Q:) Error getting validation data","instance":"","subproblems":},"order":"[https://acme-v02.api.letsencrypt.org/acme/order/3334780226/510776789156","attempt":2,"max\_attempts](https://acme-v02.api.letsencrypt.org/acme/order/3334780226/510776789156%22,%22attempt%22:2,%22max_attempts)":3} caddy-1 | {"level":"error","ts":1778768832.1109133,"logger":"tls.obtain","msg":"could not get certificate from issuer","identifier":"meilisearch.openedx.univ-bejaia.dz","issuer":"acme-v02.api.letsencrypt.org-directory","error":"HTTP 400 urn:ietf:params:acme:error:connection - 41.111.207.114: Fetching [https://meilisearch.openedx.univ-bejaia.dz:443/.well-known/acme-challenge/TeRMrgTMidDLvBUErpt5jjNERFCAjSxAHHMgG1QXn7Q:](https://meilisearch.openedx.univ-bejaia.dz:443/.well-known/acme-challenge/TeRMrgTMidDLvBUErpt5jjNERFCAjSxAHHMgG1QXn7Q:) Error getting validation data"} caddy-1 | {"level":"warn","ts":1778768832.1110094,"logger":"http","msg":"missing email address for ZeroSSL; it is strongly recommended to set one for next time"} caddy-1 | {"level":"error","ts":1778768832.297565,"logger":"tls.obtain","msg":"could not get certificate from issuer","identifier":"meilisearch.openedx.univ-bejaia.dz","issuer":"acme.zerossl.com-v2-DV90","error":"account pre-registration callback: failed getting EAB credentials: HTTP 422: caddy\_legacy\_user\_removed (code 2977)"} caddy-1 | {"level":"error","ts":1778768832.2976158,"logger":"tls.obtain","msg":"will retry","error":"[meilisearch.openedx.univ-bejaia.dz] Obtain: account pre-registration callback: failed getting EAB credentials: HTTP 422: caddy\_legacy\_user\_removed (code 2977)","attempt":1,"retrying\_in":60,"elapsed":10.684478901,"max\_duration":2592000} caddy-1 | {"level":"error","ts":1778768832.939397,"logger":"http.acme\_client","msg":"challenge failed","identifier":"apps.openedx.univ-bejaia.dz","challenge\_type":"http-01","problem":{"type":"urn:ietf:params:acme:error:connection","title":"","detail":"41.111.207.114: Fetching [https://apps.openedx.univ-bejaia.dz:443/.well-known/acme-challenge/l4BLroO6Qm7Vu\_lR-qLptw5bgCdzhc8FzzUBT00HxIU:](https://apps.openedx.univ-bejaia.dz:443/.well-known/acme-challenge/l4BLroO6Qm7Vu_lR-qLptw5bgCdzhc8FzzUBT00HxIU:) Error getting validation data","instance":"","subproblems":}} caddy-1 | {"level":"error","ts":1778768832.939444,"logger":"http.acme\_client","msg":"validating authorization","identifier":"apps.openedx.univ-bejaia.dz","problem":{"type":"urn:ietf:params:acme:error:connection","title":"","detail":"41.111.207.114: Fetching [https://apps.openedx.univ-bejaia.dz:443/.well-known/acme-challenge/l4BLroO6Qm7Vu\_lR-qLptw5bgCdzhc8FzzUBT00HxIU:](https://apps.openedx.univ-bejaia.dz:443/.well-known/acme-challenge/l4BLroO6Qm7Vu_lR-qLptw5bgCdzhc8FzzUBT00HxIU:) Error getting validation data","instance":"","subproblems":},"order":"[https://acme-v02.api.letsencrypt.org/acme/order/3334780206/510776791046","attempt":2,"max\_attempts](https://acme-v02.api.letsencrypt.org/acme/order/3334780206/510776791046%22,%22attempt%22:2,%22max_attempts)":3} caddy-1 | {"level":"error","ts":1778768832.9394724,"logger":"tls.obtain","msg":"could not get certificate from issuer","identifier":"apps.openedx.univ-bejaia.dz","issuer":"acme-v02.api.letsencrypt.org-directory","error":"HTTP 400 urn:ietf:params:acme:error:connection - 41.111.207.114: Fetching [https://apps.openedx.univ-bejaia.dz:443/.well-known/acme-challenge/l4BLroO6Qm7Vu\_lR-qLptw5bgCdzhc8FzzUBT00HxIU:](https://apps.openedx.univ-bejaia.dz:443/.well-known/acme-challenge/l4BLroO6Qm7Vu_lR-qLptw5bgCdzhc8FzzUBT00HxIU:) Error getting validation data"} caddy-1 | {"level":"warn","ts":1778768832.9395719,"logger":"http","msg":"missing email address for ZeroSSL; it is strongly recommended to set one for next time"} caddy-1 | {"level":"error","ts":1778768833.1246226,"logger":"tls.obtain","msg":"could not get certificate from issuer","identifier":"apps.openedx.univ-bejaia.dz","issuer":"acme.zerossl.com-v2-DV90","error":"account pre-registration callback: failed getting EAB credentials: HTTP 422: caddy\_legacy\_user\_removed (code 2977)"} caddy-1 | {"level":"error","ts":1778768833.1246614,"logger":"tls.obtain","msg":"will retry","error":"[apps.openedx.univ-bejaia.dz] Obtain: account pre-registration callback: failed getting EAB credentials: HTTP 422: caddy\_legacy\_user\_removed (code 2977)","attempt":1,"retrying\_in":60,"elapsed":11.511526126,"max\_duration":2592000} caddy-1 | {"level":"error","ts":1778768833.2936373,"logger":"http.acme\_client","msg":"challenge failed","identifier":"studio.openedx.univ-bejaia.dz","challenge\_type":"http-01","problem":{"type":"urn:ietf:params:acme:error:connection","title":"","detail":"41.111.207.114: Fetching [https://studio.openedx.univ-bejaia.dz:443/.well-known/acme-challenge/QuDzLvjz98N9eTFKOZ5Up3wOwvPYaOhyO88ROnLCb8Q:](https://studio.openedx.univ-bejaia.dz:443/.well-known/acme-challenge/QuDzLvjz98N9eTFKOZ5Up3wOwvPYaOhyO88ROnLCb8Q:) Error getting validation data","instance":"","subproblems":}} caddy-1 | {"level":"error","ts":1778768833.293678,"logger":"http.acme\_client","msg":"validating authorization","identifier":"studio.openedx.univ-bejaia.dz","problem":{"type":"urn:ietf:params:acme:error:connection","title":"","detail":"41.111.207.114: Fetching [https://studio.openedx.univ-bejaia.dz:443/.well-known/acme-challenge/QuDzLvjz98N9eTFKOZ5Up3wOwvPYaOhyO88ROnLCb8Q:](https://studio.openedx.univ-bejaia.dz:443/.well-known/acme-challenge/QuDzLvjz98N9eTFKOZ5Up3wOwvPYaOhyO88ROnLCb8Q:) Error getting validation data","instance":"","subproblems":},"order":"[https://acme-v02.api.letsencrypt.org/acme/order/3334780196/510776788576","attempt":2,"max\_attempts](https://acme-v02.api.letsencrypt.org/acme/order/3334780196/510776788576%22,%22attempt%22:2,%22max_attempts)":3} caddy-1 | {"level":"error","ts":1778768833.2936983,"logger":"tls.obtain","msg":"could not get certificate from issuer","identifier":"studio.openedx.univ-bejaia.dz","issuer":"acme-v02.api.letsencrypt.org-directory","error":"HTTP 400 urn:ietf:params:acme:error:connection - 41.111.207.114: Fetching [https://studio.openedx.univ-bejaia.dz:443/.well-known/acme-challenge/QuDzLvjz98N9eTFKOZ5Up3wOwvPYaOhyO88ROnLCb8Q:](https://studio.openedx.univ-bejaia.dz:443/.well-known/acme-challenge/QuDzLvjz98N9eTFKOZ5Up3wOwvPYaOhyO88ROnLCb8Q:) Error getting validation data"} ---
**Author:** ![sebastiannielsen](https://avatars.discourse-cdn.com/v4/letter/s/e9bcb4/32.png) [@sebastiannielsen](https://community.letsencrypt.org/u/sebastiannielsen)\ **Post date:** [May 15, 2026, 12:23am UTC](https://community.letsencrypt.org/t/im-having-trouble-generating-the-lets-encrypt-certificate/247159/25 "2026-05-15T00:23:21Z")
You have your client set for ZeroSSL. Thats why its erroring out. Try changing to Lets Encrypt. ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [May 15, 2026, 1:59am UTC](https://community.letsencrypt.org/t/im-having-trouble-generating-the-lets-encrypt-certificate/247159/26 "2026-05-15T01:59:45Z")
> [@sebastiannielsen](#): > > You have your client set for ZeroSSL I am pretty sure Caddy tries with multiple CA. Which explains why the below Let's Encrypt error appears in their error log. It looks like ZeroSSL fails as it wasn't setup right (EAB) but that would not affect Let's Encrypt. > [@pipa\_85](#): > > Fetching [https://meilisearch.openedx.univ-bejaia.dz:443/.well-known/acme-challenge/TeRMrgTMidDLvBUErpt5jjNERFCAjSxAHHMgG1QXn7Q:](https://meilisearch.openedx.univ-bejaia.dz:443/.well-known/acme-challenge/TeRMrgTMidDLvBUErpt5jjNERFCAjSxAHHMgG1QXn7Q:) Error getting validation data","instance":"","subproblems":},"order":"[https://acme-v02.api.letsencrypt.org/acme/order/3334780226/510776789156"](https://acme-v02.api.letsencrypt.org/acme/order/3334780226/510776789156%22,%22attempt%22:2,%22max_attempts) ---
**Author:** ![danb35](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/danb35/32/70869_2.png) [@danb35](https://community.letsencrypt.org/u/danb35)\ **Post date:** [May 15, 2026, 2:26am UTC](https://community.letsencrypt.org/t/im-having-trouble-generating-the-lets-encrypt-certificate/247159/27 "2026-05-15T02:26:38Z")
> [@pipa\_85](#): > > `Fetching https://meilisearch.openedx.univ-bejaia.dz:443/.well-known/acme-challenge/TeRMrgTMidDLvBUErpt5jjNERFCAjSxAHHMgG1QXn7Q: Error getting validation data"}` When I try to visit this URL, I'm getting an expired certificate for a Fortinet firewall, which makes it sound like the firewall continues to be an issue. ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [May 15, 2026, 2:54am UTC](https://community.letsencrypt.org/t/im-having-trouble-generating-the-lets-encrypt-certificate/247159/28 "2026-05-15T02:54:27Z")
> [@danb35](#): > > When I try to visit this URL, I'm getting an expired certificate for a Fortinet firewall, I do too. Interesting that HTTP requests are redirected to HTTPS just fine. It is the HTTPS request that gets blocked by Fortinet. I should note that some systems (like my AWS servers) get a 403 Forbidden with any HTTP request but other systems (like Let's Debug or [check-host.net](http://check-host.net)) get redirected. The Let's Encrypt primary validation center must also get redirected otherwise we would have seen the HTTP URL in the error message. In short, the firewall is still heavily involved. @pipa_85 While it is legal to redirect a cert HTTP Challenge to HTTPS it is not required. I don't know Caddy well enough to know if that is how it handles that but I suspect not. It is not as efficient and adds complexity and I don't think Caddy would design for that. ---
**Author:** ![pipa\_85](https://avatars.discourse-cdn.com/v4/letter/p/90db22/32.png) [@pipa\_85](https://community.letsencrypt.org/u/pipa_85)\ **Post date:** [May 17, 2026, 10:55am UTC](https://community.letsencrypt.org/t/im-having-trouble-generating-the-lets-encrypt-certificate/247159/29 "2026-05-17T10:55:28Z")
I was able to generate a certificate for the domain openedx.univ-bejaia.dz by disabling Caddy and enabling Apache (without docker). As you can see, Let's Debug ([Let's Debug](https://letsdebug.net/openedx.univ-bejaia.dz/2932293)) now shows everything is OK. In my opinion, this proves that the problem isn't with the firewall. I disabled the HTTPS redirection, but Caddy still can't generate a certificate. Could you please check if the HTTPS connections are blo blocked? ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [May 17, 2026, 1:02pm UTC](https://community.letsencrypt.org/t/im-having-trouble-generating-the-lets-encrypt-certificate/247159/30 "2026-05-17T13:02:32Z")
> [@pipa\_85](#): > > I was able to generate a certificate for the domain openedx.univ-bejaia.dz ... this proves that the problem isn't with the firewall. The most recent cert issued for that domain was 5 days ago. So, yes, you had it working then but that does not mean it would work now. > [@pipa\_85](#): > > I disabled the HTTPS redirection, but Caddy still can't generate a certificate. Could you please check if the HTTPS connections are blo blocked Do you mean HTTP connections? Because HTTP connections are needed when using an HTTP Challenge and those are failing. See this Let's Debug test result: [Let's Debug](https://letsdebug.net/openedx.univ-bejaia.dz/2932510) As for HTTPS connections to that domain, they are failing because they are using a Fortinet self-signed cert. Are you able to make HTTPS connections to that domain? Because many other tools show it failing. Such as this one: [SSL Checker](https://decoder.link/sslchecker/openedx.univ-bejaia.dz/443) We are not a general help site for server admin. We can help get and manage certs but your problems are more related to just knowing how your server and firewall is configured. It looks to me like you are trying to install and run a packaged product. You should probably work with their tech support on these problems. They know more how they should be correctly configured. ---
**Author:** ![pipa\_85](https://avatars.discourse-cdn.com/v4/letter/p/90db22/32.png) [@pipa\_85](https://community.letsencrypt.org/u/pipa_85)\ **Post date:** [May 17, 2026, 1:23pm UTC](https://community.letsencrypt.org/t/im-having-trouble-generating-the-lets-encrypt-certificate/247159/31 "2026-05-17T13:23:52Z")
this is because I enabled caddy again. I just desabled it, you can see that the connection to openedx.univ-bejaia.dz is now secure with a let's encrypt certificate ![openedx](https://global.discourse-cdn.com/letsencrypt/original/3X/e/0/e0e72df603ca810c06a5dbf73c70df9461513963.png) We have a WAF (FortiWeb). With Apache, I can easily generate certificates with this WAF, but perhaps Caddy doesn't support it. I'll try disabling the WAF and see what happens. Thank you for your help. Please let me know you've read this message so I can reactivate Caddy. ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [May 17, 2026, 1:46pm UTC](https://community.letsencrypt.org/t/im-having-trouble-generating-the-lets-encrypt-certificate/247159/32 "2026-05-17T13:46:36Z")
> [@pipa\_85](#): > > you can see that the connection to openedx.univ-bejaia.dz is now secure Not with HTTPS it is not. See: [SSL Checker](https://decoder.link/sslchecker/openedx.univ-bejaia.dz/443) But, that would not necessarily prevent you from getting a cert using HTTP Challenge That Let's Debug test is testing the HTTP connection for that kind of challenge. Very different things. And Let's Debug is a good test to check for basic problems. But, you may still fail to get a certificate. You might try running this test to see if your current setup could get a cert ```nohighlight certbot certonly --dry-run --webroot -w /var/www/test -d openedx.univ-bejaia.dz ``` That is what you showed in your first post. The --dry-run will not affect your previous certs. It just uses the Let's Encrypt Staging (test) system to verify you could get a cert. It is a more thorough check than what Let's Debug does. ---
**Author:** ![pipa\_85](https://avatars.discourse-cdn.com/v4/letter/p/90db22/32.png) [@pipa\_85](https://community.letsencrypt.org/u/pipa_85)\ **Post date:** [May 17, 2026, 2:18pm UTC](https://community.letsencrypt.org/t/im-having-trouble-generating-the-lets-encrypt-certificate/247159/33 "2026-05-17T14:18:07Z")
> [@MikeMcQ](#): > > `certbot certonly --dry-run --webroot -w /var/www/test -d openedx.univ-bejaia.dz` ![dry run](https://global.discourse-cdn.com/letsencrypt/original/3X/4/c/4ce0ba7f81a7651bc58f74504e98cc7af065dffd.png) Sorry, I forgot to add the certificate in fortiweb that's why you got theses errors, you can try again wou will not see errors: > **[SSL Checker](https://decoder.link/sslchecker/openedx.univ-bejaia.dz/443)** > > Verify that your SSL certificate is installed correctly, identify installation issues if any. ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [May 17, 2026, 3:54pm UTC](https://community.letsencrypt.org/t/im-having-trouble-generating-the-lets-encrypt-certificate/247159/34 "2026-05-17T15:54:33Z")
Good. Your Apache and firewall are still working to get a certificate. I don't know Caddy well enough to assist you in that. Maybe someone else here will help with that. Or, try the Caddy community forum. If posting at Caddy forum refer them to this thread and the --dry-run success you just had with Certbot and Apache. ---
**Author:** ![pipa\_85](https://avatars.discourse-cdn.com/v4/letter/p/90db22/32.png) [@pipa\_85](https://community.letsencrypt.org/u/pipa_85)\ **Post date:** [May 20, 2026, 10:52am UTC](https://community.letsencrypt.org/t/im-having-trouble-generating-the-lets-encrypt-certificate/247159/35 "2026-05-20T10:52:00Z")
First, thank you all for your help, the problem is solved. It was FortiWeb that caused the issue, not Caddy or Docker. I disabled FortiWeb, and the certificate was generated. What I find strange is that FortiWeb didn't block HTTP access to the server with **Apache,** but it did block HTTP access to the server with **Caddy in Docker**. Can I now re-enable FortiWeb, or will that prevent the certificate from renewing ? ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [May 20, 2026, 12:55pm UTC](https://community.letsencrypt.org/t/im-having-trouble-generating-the-lets-encrypt-certificate/247159/36 "2026-05-20T12:55:32Z")
> [@pipa\_85](#): > > Can I now re-enable FortiWeb, or will that prevent the certificate from renewing ? A certificate renewal goes through the same validation steps as the original cert. You will need to find out why FortiWeb was interfering. ---
**Author:** ![pipa\_85](https://avatars.discourse-cdn.com/v4/letter/p/90db22/32.png) [@pipa\_85](https://community.letsencrypt.org/u/pipa_85)\ **Post date:** [May 20, 2026, 1:11pm UTC](https://community.letsencrypt.org/t/im-having-trouble-generating-the-lets-encrypt-certificate/247159/37 "2026-05-20T13:11:08Z")
> [@MikeMcQ](#): > > A certificate renewal goes through the same validation steps as the original cert. You will need to find out why FortiWeb was interfering. Okay, thank you for your help. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [June 19, 2026, 1:11pm UTC](https://community.letsencrypt.org/t/im-having-trouble-generating-the-lets-encrypt-certificate/247159/38 "2026-06-19T13:11:46Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed. [Previous page](https://community.letsencrypt.org/t/im-having-trouble-generating-the-lets-encrypt-certificate/247159.md?page=1)