Hello,
Please help me to set up Cloud Front to work?
I tested a lot and couldn’t get it to work on my Wordpress.
Maybe I’m missing something.
When I activate CDN I get a 502 error.
I tested on other VPSs that are Lamp Stack or Open Lite Server and everything with my CDN on same site setting and files works.
It seems there is something specific that blocks CDN in Hestia.
Please help if you can.
Request Method
GET
Status Code
502 Bad Gateway
Referrer Policy
strict-origin-when-cross-origin
Hi @vipvip
If CloudFront can’t reach your server maybe you have some rule blocking their IPs.
iptables -S
The command is iptables -S, with a capital S
But I would like to know why no rules are applied. When you installed Hestia what were the options you used?
v-list-sys-config json | grep FIREWALL_SYSTEM
v-list-firewall
ufw status
this is my installation:
bash hst-install.sh --port customport --username username --email [email protected] --password mypass --multiphp yes --exim no --dovecot no --clamav no --spamassassin no --api no, but i disable firewall, i have in aws (lighsail) and port 80 and 443 is open for all.
OK, so you’ve disabled iptables and set all the policies to default accept. You have an external firewall allowing all traffic on ports 80 and 443. If that’s the case, since I don’t work with AWS, I can’t say for sure whether it’s configured properly.
Anyway, check whether CloudFront reaches Hestia server (check your website logs) but if you see nothing and iptables is accepting all traffic, seems the problem is in the conf of that Lightsail instance.
I have the same VPS in Azure. Both are with Debian 11. Both are standard installations. After that I install Hestia panel. I have NOT done any manual configurations. If I install Hestia on Debian 12, is it possible to improve it? I use Debian 11 because I know it is a little lighter than 12. What do you recommend I use as a base for Hestia (11 or 12)? I really like it, I have tried really different solutions and Hestia remains the best plug and play solution for a small VPS in my opinion. I would test everything to get CDN to work on it. It is certainly not from the sites or the configuration in Cloud Front because everything works on VPS with LAMP stack or with OLS as it is currently.
Debian 13 will be released in a few months, for a new install I would use Debian 12.
If you have disabled the firewall, the web server is listening on the right ports and you didn’t receive any connection when CloudFront is enabled, then something is happening between the edge and your VPS. If you disable CloudFront for cdn.besttanswim.com, are you able to reach your site?
Yes , if i disabel CloudFrond the is work normal. (and the same site with same CloudFront settings work normal on other OLS or LAMP Vps.)
apache and nginx:
I know nothing about CloudFront so I can’t help here.
Anyway, as I said, if it works with CloudFront disabled… I also see Nginx is listening in a private address so something must redirect the traffic from the public ip to your server’s private ip. I could say there is conf problem in Nginx or Nginx+Apache but if you enable CloudFront and you see nothing in web logs, then CloudFront is not reaching your server and it could be a connectivity issue… I don’t know.
I attach CDN only for confirm, no need help. AWS Lighsail redirect the traffic from the public ip to my server’s private ip.
Do you know what could be causing the 500 error when I save the CDN configuration in my cache module that is related to this path https://mydomain/wp-admin/options.php. This happens sometimes when I clear the cache. Is there some limit in PHP that does not allow this type of operation? May be this is problem. Now i start debian 12 but have the same problem.
I make many test, i dont know hestiacp and dont find solution. Do you have some option for little pay support to fix this for me.
I’m sorry, but I don’t know how to help solve that issue.
Can we conclude that HestiaCP cannot ensure that WordPress works with AWS Cloud Front CDN service?
No, we cannot conclude that HestiaCP can’t ensure that WordPress works with AWS CloudFront CDN service based on a sample from a single user. A single data point is not sufficient to make a general conclusion about the system’s compatibility or reliability.
I did tests with Azure CDN today, everything works without a problem with Hestia.
I guess there is something specific between the communication of CDN Cloud Front and the settings that Hestia makes on the server. There is probably some small setting or limit somewhere that affects it, I don’t know.
I will try different settings in Cloud Front and share my experience later. If you still have any directions where to look for the problem, please share.
