I recently upgraded to the latest version of Untangle (Build: 9.3.2~svn20121030r33425release9.3-1lenny) and am having a peculiar problem.
We have a "public" wireless network that is on its own VLAN and ACLs are configured so that this network can only access the Internet. This has worked out very well as these users are still able to access any of our services we've opened to the outside world (email, our website, etc.) as the traffic simply loops back in through Untangle via our pubilc IP addresses as advertised by outside DNS servers.
However, with the upgrade, this no longer works for HTTPS connections. When I'm connected to our public wireless network and browse to "https://mail.ourdomain.com", I am directed to the Untangle login screen. Non-HTTPS connections work fine (like our webserver http://www.ourdomain.com).
Connections from the "real" outside work fine.
I haven't a clue on how to troubleshoot this! Any suggestions? This was not a problem when we were running the previous version of Untangle.
We have a "public" wireless network that is on its own VLAN and ACLs are configured so that this network can only access the Internet. This has worked out very well as these users are still able to access any of our services we've opened to the outside world (email, our website, etc.) as the traffic simply loops back in through Untangle via our pubilc IP addresses as advertised by outside DNS servers.
However, with the upgrade, this no longer works for HTTPS connections. When I'm connected to our public wireless network and browse to "https://mail.ourdomain.com", I am directed to the Untangle login screen. Non-HTTPS connections work fine (like our webserver http://www.ourdomain.com).
Connections from the "real" outside work fine.
I haven't a clue on how to troubleshoot this! Any suggestions? This was not a problem when we were running the previous version of Untangle.