![]() You should also verify that the pfSense web GUI is not using the same port (443), in System/Advanced/Admin Access. What you should do instead is to create a Firewall rule to accept HTTPS: If you do this, it will bypass your reverse proxy. ![]() Hamada sets a NAT rule to forward HTTPS traffic to his Exchange server: Simple one not mentioned in his steps, you have to enable the Squid Proxy Server otherwise Squid will not runĢ. Here’s what I had to do to get it working:ġ. Unfortunately the steps given seem to be incorrect in some places, certainly for my version which is 2.3.2. If you search for help with publishing Exchange on pfSense you will find this document by Mohammed Hamada. I installed the Squid plugin which includes specific reverse proxy support for Exchange. I wanted to publish Exchange through pfSense. PfSense is a FreeBSD-based firewall which you can find here.
0 Comments
Leave a Reply. |