Messages

I've succesfully settled HAProxy on OPNSENS with one frotend and few rules to correctly forward traffic on backend pools (I have two for two different services).

Everything is working properly except cloudfront which is used as CDN for a wordpress website (just for images, css and js).

The main domain points directly to haproxy, the cdn subdomain points to cloudfront.
The mail domain is also settled as "origin" for cloudfront.

When I try to reach cdn.XXXX.TLD I get "502 Bad Gateway".
EDIT: I did realize that also from GTMetrix I get the same error while on the others (pingdom, my browser, google page speed) everything seems  ok.

The frontend uses SSL Offloading, I also used SSL with both wildcard and specific domain.

Any suggestion?

[EDIT:]

I've succesfully settled HAProxy on OPNSENS with one frotend and few rules to correctly forward traffic on backend pools (I have two for two different services).

Everything is working properly except cloudfront which is used as CDN for a wordpress website (just for images, css and js).

The main domain points directly to haproxy, the cdn subdomain points to cloudfront.
The mail domain is also settled as "origin" for cloudfront.

When I try to reach cdn.XXXX.TLD I get "502 Bad Gateway".
EDIT: I did realize that also from GTMetrix I get the same error while on the others (pingdom, my browser, google page speed) everything seems  ok.

The frontend uses SSL Offloading, I also used SSL with both wildcard and specific domain.

Any suggestion?

Most probably this issue was already solved by someone of you but I cannot find any post or docs.

Scenario:
OPNsense succesfully configured with Web Filter that is working properly for LAN clients (transparent mode)
WireGuard succesfully configured for external client. I can connect and the entire traffic is routed throuogh opnsense


ISSUE:

If I want to route traffic for port 80 and 443 through the web filter, when I try to navigate while connected in VPN I get the "ACCESS denied" page and the URL is translated into an IP.

EXAMPLE:
URL: google.com

OUTPUT: ACCESS DENIED to https://123.123.123.123/*

The same request is managed correctly if made from the LAN.

Any idea on how to solve it?