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

Times out trying to access the UTM9 web console when using web protection

We are hoping you can help us. We are investigating using Sophos UTM9 for web protection running firmware 9.501-5 and have come across an annoying situation.

We have the web protection setup and working and use group policy to push out the proxy settings (ip address & port 8080) to our test users which is the same IP address as the UTM web console. However, now when we try to access the UTM9 console the web page tab just says "waiting for 192.168.xxx.xxx" and the log is below:

2017:08:17-13:39:43 sqldcsos01 httpproxy[7170]: id="0003" severity="info" sys="SecureWeb" sub="http" name="http access" action="pass" method="CONNECT" srcip="10.30.30.201" dstip="" user="" group="" ad_domain="" statuscode="407" cached="0" profile="REF_HttProContaInterNetwo (QLDC_General)" filteraction=" ()" size="85226" request="0x14c9f600" url="https://192.168.xxx.xxx:4444/" referer="" error="" authtime="19" dnstime="0" cattime="0" avscantime="0" fullreqtime="3048" device="0" auth="2" ua="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36" exceptions=""
 
2017:08:17-13:39:59 sqldcsos01 httpproxy[7170]: id="0003" severity="info" sys="SecureWeb" sub="http" request="(nil)" function="plain_write_vector" file="epoll.c" line="1117" message="Write error on the epoll handler 88 (Broken pipe)"
 
Eventually the following is displayed in the web page:
 
This page can’t be displayed

Turn on TLS 1.0, TLS 1.1, and TLS 1.2 in Advanced settings and try connecting to https://192.168.xxx.xxx:4444 again. If this error persists, it is possible that this site uses an unsupported protocol or cipher suite such as RC4 (link for the details), which is not considered secure. Please contact your site administrator.

 
I am very new to the Sophos world so any help would be most welcome. I was wondering if it's because the proxy setting is the same ip address as the UTM console just a different port.


This thread was automatically locked due to age.
Parents Reply Children