Squid reverse proxy not working
So I'm trying to set up Squid (V0.4.44_7) as a reverse proxy with the use of the following guide but on my system it's not working as it should. I have a webserver that also has Exchange 2013 installed on it.
The plan is that if I succeed in using the reverse proxy properly I can use a second server that only houses the websites separately from my Exchange environment.
I've created a FW rule as was stated in the guide with the exception of allowing HTTP and HTTPS in my custom ports option:
But when I disable my NAT rule, the reverse proxy is not working. I've tried connecting with my mobile phone's 4G connection (IP 220.127.116.11) at the time towards my websites and OWA. I keep getting the error message "TCP_DENIED/403"
Squid realtime log:
Reverse proxy settings:
Someone that might have an idea about what could cause my issue?
Could this perhaps come from the fact that I also enabled Exchange support on the reverse proxy? At the moment my webserver and exchange server are on the same guest...
Just tested disabling this option and that did not solve my issue. When I disable nat no website and exchange front end are working/ reachable from the WAN.
Problem now is that I need to disable NAT for properly using the reverse proxy, or am I mistaken in this regard? If so, to which IP address do I need to point it, as my exchange & webserver will be split up when I have a proxy properly running in my network.
So ideal example setup:
No one? :(
Hello, I've never used the reverse of squid with the exchange, so I do not know how to comment on it.
however in my uses of the reverse it is necessary to use a regex according to the attached image.
another question is about the ports, although it is not recommended, the way I do is the following, I create a rule with port 80 and 443 and point them to pfsense itself - print below - (this is not recommended, however for me it works)
Thanks for the information.
Seems about the same settings as it's on my PFsense.
I'll give it a try with an additional webserver, might be that my OWA is messing up the mappings.