the error is 503

@blasta Just want to say thank you!

@hadiaghajani Hello, I'm trying to do the same thing ... without success. But i'm not able like you to filter by IP adresses. See my post with scheme : https://forum.netgate.com/topic/166308/squid-reverse-proxy-firewall-rules Regards,

@khalildg That's a lovely screenshot you've got there.

Hello, I did a sheme to see what rules i'm trying to do. [image: Ticket-PFsense.jpg]

@nogbadthebad Hey! Thanks for the reply I've tried this but i've only syslogs and not squid logs The problem with squid, the logs are located to Pfsense disk directly. We can't move to SMB or mount the smb with a classical mount maybe? Best regards

@jdennis011 See attached image for a small draw up. For the breakdown: The enduser is supposed to access system A from outside the network via HTTPS, system A grabs data from the API(both in local lan) but the API only communicates via http. So how do link the two on the HAproxy, such that data between system A and the API is shared via http in the background but shared to the end user via HTTPS? Please note: if system A cannot locate the API server, the site breaks and nothing works. [image: 1635166608168-haproxy.jpeg]

@alekoy did you solve this issue?

@sipriuspt Perhaps their certs really are invalid? A LetsEncrypt root cert expired a while back that caused such problems. Look at the details of the cert error and see what the problem is. That will help you decide if it's anything wrong on your end.

@samdond Browsers will always warn if a certificate is self signed. When you access the pfSense GUI over https, pfSense will use a self generated - thus self signed - certificate. You can instruct your browser to make an exception. Or get a certificate from a trusted certificate authority, like Letsencrypt and the acme.sh pfSense package. @samdond said in Problem with webGUI certificate: Set pfSense's web gui to use http rather than https. That's another solution.