# Unable to setup Lets Encrypt SSL

**URL:** <https://forum.hestiacp.com/t/unable-to-setup-lets-encrypt-ssl/22475>\
**Category:** Uncategorized\
**Created:** [November 17, 2026, 12:15pm UTC](https://forum.hestiacp.com/t/unable-to-setup-lets-encrypt-ssl/22475 "2026-11-17T12:15:32Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![oladipomd](https://forum.hestiacp.com/user_avatar/forum.hestiacp.com/oladipomd/32/5873_2.png) [@oladipomd](https://forum.hestiacp.com/u/oladipomd)\
**Post date:** [November 17, 2026, 12:15pm UTC](https://forum.hestiacp.com/t/unable-to-setup-lets-encrypt-ssl/22475/1 "2026-11-17T12:15:32Z")

</div>

When I try to set up SSL for a domain, I get the following error

Error: Let’s Encrypt validation status 400 (members.ng). Details: 403:“195.35.56.229: Invalid response from [http://members.ng/.well-known/acme-challenge/mmRVuoYQP4sADje2S9ATDrRnK734\_ThrJzDoHQgKMpk:](http://members.ng/.well-known/acme-challenge/mmRVuoYQP4sADje2S9ATDrRnK734_ThrJzDoHQgKMpk:) 404”

I understand that Hestia likely uses an alias to point to the acme file, but I do not know where to change it since the file is not created in the new hosting account. Please help.

---

<div class="post-metadata">

**Author:** ![sahsanu](https://forum.hestiacp.com/user_avatar/forum.hestiacp.com/sahsanu/32/9318_2.png) [@sahsanu](https://forum.hestiacp.com/u/sahsanu)\
**Post date:** [November 17, 2026, 1:39pm UTC](https://forum.hestiacp.com/t/unable-to-setup-lets-encrypt-ssl/22475/2 "2026-11-17T13:39:32Z")

</div>

> [@oladipomd](#):
>
> I understand that Hestia likely uses an alias to point to the acme file, but I do not know where to change it

Hestia doesn’t use a file to server tha acme challenge, it creates a nginx conf file for your domain.

Show the output of these commands:

```t
nginx -t && systemctl restart nginx
systemctl status nginx --no-pager -l
ls -la /home/*/conf/web/members.ng/
cat /home/*/conf/web/members.ng/nginx.conf
cat /home/*/conf/web/members.ng/nginx.conf_letsencrypt

```

---

<div class="post-metadata">

**Author:** ![oladipomd](https://forum.hestiacp.com/user_avatar/forum.hestiacp.com/oladipomd/32/5873_2.png) [@oladipomd](https://forum.hestiacp.com/u/oladipomd)\
**Post date:** [November 17, 2026, 1:52pm UTC](https://forum.hestiacp.com/t/unable-to-setup-lets-encrypt-ssl/22475/3 "2026-11-17T13:52:52Z")

</div>

> [@sahsanu](#):
>
> ```auto
> nginx -t && systemctl restart nginx
> systemctl status nginx --no-pager -l
> ls -la /home/*/conf/web/members.ng/
> cat /home/*/conf/web/members.ng/nginx.conf
> cat /home/*/conf/web/members.ng/nginx.conf_letsencrypt
> 
> ```

Please see below

> root@websguy:/# nginx -t && systemctl restart nginx  
> nginx: the configuration file /etc/nginx/nginx.conf syntax is ok  
> nginx: configuration file /etc/nginx/nginx.conf test is successful
> 
> root@websguy:/# systemctl status nginx --no-pager -l  
> ● nginx.service - nginx - high performance web server  
> Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)  
> Active: active (running) since Tue 2026-11-17 13:47:27 UTC; 21s ago  
> Docs: [nginx documentation](https://nginx.org/en/docs/)  
> Process: 3912648 ExecStart=/usr/sbin/nginx -c /etc/nginx/nginx.conf (code=exited, status=0/SUCCESS)  
> Main PID: 3912649 (nginx)  
> Tasks: 11 (limit: 38369)  
> Memory: 39.4M  
> CPU: 816ms  
> CGroup: /system.slice/nginx.service  
> ├─3912649 “nginx: master process /usr/sbin/nginx -c /etc/nginx/nginx.conf”  
> ├─3912650 “nginx: worker process” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “”  
> ├─3912651 “nginx: worker process” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “”  
> ├─3912652 “nginx: worker process” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “”  
> ├─3912653 “nginx: worker process” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “”  
> ├─3912654 “nginx: worker process” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “”  
> ├─3912655 “nginx: worker process” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “”  
> ├─3912656 “nginx: worker process” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “”  
> ├─3912657 “nginx: worker process” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “” “”  
> ├─3912658 “nginx: cache manager process” “” “” “” “” “” “” “” “” “” “” “” “”  
> └─3912659 “nginx: cache loader process” “” “” “” “” “” “” “” “” “” “” “” “” “”
> 
> Nov 17 13:47:27 websguy.com.ng systemd[1]: Starting nginx - high performance web server…  
> Nov 17 13:47:27 websguy.com.ng systemd[1]: Started nginx - high performance web server.
> 
> root@websguy:/# ls -la /home/smartwork/conf/web/members.ng/  
> total 20  
> drwxr-xr-x 2 root root 4096 Nov 17 12:05 .  
> drwxr-x–x 15 root root 4096 Nov 17 10:49 ..  
> -rw-r----- 1 root smartwork 1614 Nov 17 10:49 apache2.conf  
> -rw-r----- 1 root smartwork 1526 Nov 17 10:49 nginx.conf  
> -rw-r–r-- 1 root root 147 Nov 17 12:05 nginx.conf\_letsencrypt  
> lrwxrwxrwx 1 root root 58 Nov 17 12:05 nginx.ssl.conf\_letsencrypt → /home/smartwork/conf/web/members.ng/nginx.conf\_letsencrypt
> 
> root@websguy:/# cat /home/smartwork/conf/web/members.ng/nginx.conf  
> #=========================================================================#
> 
> # Default Web Domain Template
> 
> # DO NOT MODIFY THIS FILE! CHANGES WILL BE LOST WHEN REBUILDING DOMAINS
> 
> # [Web Templates and FastCGI/Proxy Cache | Hestia Control Panel](https://hestiacp.com/docs/server-administration/web-templates.html)
> 
> #=========================================================================#
> 
> server {  
> listen 195.35.56.229:80;  
> server\_name members.ng www.members.ng;  
> error\_log /var/log/apache2/domains/members.ng.error.log error;
> 
> ```auto
> include /home/smartwork/conf/web/members.ng/nginx.forcessl.conf*;
> 
> location ~ /\.(?!well-known|file) {
> deny all;
> return 404;
> }
> 
> location / {
> proxy_pass http://195.35.56.229:8080;
> 
> location ~* ^.+\.(css|htm|html|js|mjs|json|xml|apng|avif|bmp|cur|gif|ico|jfif|jpg|jpeg|pjp|pjpeg|png|svg|tif|tiff|webp|aac|caf|flac|m4a|midi|mp3|ogg|opus|wav|3gp|av1|avi|m4v|mkv|mov|mpg|mpeg|mp4|mp4v|webm|otf|ttf|woff|woff2|doc|docx|odf|odp|ods|odt|pdf|ppt|pptx|rtf|xls|xlsx|7z|bz2|gz|rar|tar|tgz|zip|apk|appx|bin|dmg|exe|img|iso|jar|msi|webmanifest)$ {
> try_files $uri @fallback;
> 
> root /home/smartwork/web/members.ng/public_html;
> access_log /var/log/apache2/domains/members.ng.log combined;
> access_log /var/log/apache2/domains/members.ng.bytes bytes;
> 
> expires max;
> }
> }
> 
> location @fallback {
> proxy_pass http://195.35.56.229:8080;
> }
> 
> location /error/ {
> alias /home/smartwork/web/members.ng/document_errors/;
> }
> 
> include /home/smartwork/conf/web/members.ng/nginx.conf_*;
> 
> ```
> 
> }
> 
> root@websguy:/# cat /home/smartwork/conf/web/members.ng/nginx.conf\_letsencrypt  
> location ~ “^/.well-known/acme-challenge/(.\*)$” {  
> default\_type text/plain;  
> return 200 “$1.YXfyBH0qUEhdIMZDnyjISFldHvs-30iKASLuqiSbXyk”;  
> }

---

<div class="post-metadata">

**Author:** ![sahsanu](https://forum.hestiacp.com/user_avatar/forum.hestiacp.com/sahsanu/32/9318_2.png) [@sahsanu](https://forum.hestiacp.com/u/sahsanu)\
**Post date:** [November 17, 2026, 1:54pm UTC](https://forum.hestiacp.com/t/unable-to-setup-lets-encrypt-ssl/22475/4 "2026-11-17T13:54:25Z")

</div>

Try to issue the certificate again.

---

<div class="post-metadata">

**Author:** ![oladipomd](https://forum.hestiacp.com/user_avatar/forum.hestiacp.com/oladipomd/32/5873_2.png) [@oladipomd](https://forum.hestiacp.com/u/oladipomd)\
**Post date:** [November 17, 2026, 2:10pm UTC](https://forum.hestiacp.com/t/unable-to-setup-lets-encrypt-ssl/22475/5 "2026-11-17T14:10:25Z")

</div>

It works. Thank you very much.

So it needed a forced restart of nginx?

---

<div class="post-metadata">

**Author:** ![sahsanu](https://forum.hestiacp.com/user_avatar/forum.hestiacp.com/sahsanu/32/9318_2.png) [@sahsanu](https://forum.hestiacp.com/u/sahsanu)\
**Post date:** [November 17, 2026, 2:14pm UTC](https://forum.hestiacp.com/t/unable-to-setup-lets-encrypt-ssl/22475/6 "2026-11-17T14:14:23Z")

</div>

> [@oladipomd](#):
>
> So it needed a forced restart of nginx?

Yes, it shouldn’t but yes, looks like there is an issue reloading your nginx. Indeed, right now you should restart nginx again to apply the new cert.
