Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 29 subscribers
  • Views 2707 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

XG Not Forwarding HTTP/S rather loading User Portal.

Derek Lechner

So, I upgraded to 17.1.4 MR4, and it appeared to break my forwarding of HTTP and HTTPS.  We also moved our Data Center during this time, and think I've finally pinned it down to the XG.

We have the same Pubic IP addresses.

 

I have my WAN port, setup with all 6 Public IPs (This never changed).

The public IP on port 2:1, is supposed to be forwarding HTTP/HTTPS requests to my DMZ.  However, instead of forwarding it is just loading the Sophos User Portal.  I'm using the user portal and SSL VPN, albeit a different IP (port 2:0), so disabling the user portal or changing the port is not happening.

 

I deleted and re-created my forwarding rules, thinking something was missed, however it appears the Sophos is loading the User Portal before processing the Firewall rules.

 

Sophos has also broke the User Portal of my phone system, as that was originally forwarding HTTPS from a different WAN IP (port 2:3) to my internal phone system.

 

THOUGHTS!!! Besides me throwing this out the window?



This thread was automatically locked due to age.
Parents
  • 0

    Since rules seem to be ok, I'd try to change the user portal port only(not the vpn port, so vpn users will continue to work) for as long as you can and test the firewall rules. In the current situation there's not much you can do. If the firewall rules work normally when the user portal port is changed, try it back and retest.

    In addition you could bring it all the way to 17.5 in case something went wrong with the update.

Reply
  • 0

    Since rules seem to be ok, I'd try to change the user portal port only(not the vpn port, so vpn users will continue to work) for as long as you can and test the firewall rules. In the current situation there's not much you can do. If the firewall rules work normally when the user portal port is changed, try it back and retest.

    In addition you could bring it all the way to 17.5 in case something went wrong with the update.

Children
No Data