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

"This page can’t be displayed" when connecting to an HTTPS site

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://ib.absa.co.za 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 using transparent proxy, but for some reason I just cannot browse this one particular site.

Any assistance will be much appreciated

This thread was automatically locked due to age.

sachingurung over 8 years ago

Hi Gavin,

Execute, "tracert -d ib.absa.co.za" on the system behind UTM. Check where do you face the RTO, is it UTM or ISP? If RTO is captured while going through UTM check #1 in this brilliant guide here.

Thanks

Sachin Gurung
Team Lead | Sophos Technical Support
Knowledge Base | @SophosSupport | Video tutorials
Remember to like a post. If a post (on a question thread) solves your question use the 'This helped me' link.
Cancel
Vote Up 0 Vote Down

Cancel
GavinHornigold over 8 years ago in reply to sachingurung

Hi Sachin,

Thanks for your reply. I ran the Tracert and it's definitely the UTM blocking access to ib.absa.co.za. Will follow the guide and see what I can find out..

Excuse my ignorance, but what do you mean by RTO ?

Regards

Gavin
Cancel
Vote Up 0 Vote Down

Cancel
sachingurung over 8 years ago in reply to GavinHornigold

Hi Gavin,

Apologies, abbreviations are confusing sometimes. RTO = request time out.

Thanks

Sachin Gurung
Team Lead | Sophos Technical Support
Knowledge Base | @SophosSupport | Video tutorials
Remember to like a post. If a post (on a question thread) solves your question use the 'This helped me' link.
Cancel
Vote Up 0 Vote Down

Cancel

GavinHornigold over 8 years ago in reply to sachingurung

I followed the guide, but cant find anything wrong with my setup. I even tried to add the following filtering option exception

ABSA

Skipping:

Authentication / Caching / Block by download size / Antivirus / Extension blocking / MIME type blocking / URL Filter / Content Removal / SSL scanning / Certificate trust check / Certificate date check

Matching these URLs:

^https?://([A-Za-z0-9.-]*\.)?ib.absa\.co.za\.?/

Still blocking the site though

BAlfson over 8 years ago in reply to GavinHornigold

Hi, Gavin, and welcome to the UTM Community!

Have you tried to access the site from the same browser/machine when you're not behind the UTM? I suspect you have Web Filtering in Transparent mode and are not scanning HTTPS - that the traffic is passing through the UTM with a firewall rule, not Web Filtering.

Cheers - Bob

Sophos UTM Community Moderator
Sophos Certified Architect - UTM
Sophos Certified Engineer - XG
Gold Solution Partner since 2005

MediaSoft, Inc. USA
Cancel
Vote Up 0 Vote Down

Cancel
chris yankajtis over 5 years ago

HI ,I am receiving the same issue when visiting thinkmobiles.com I ran the tracert -d thinkmobiles.com and I can reach their domain with no issues. Any other ideas what might be causing this? Doc2.docx
Cancel
Vote Up 0 Vote Down

Cancel
BAlfson over 5 years ago in reply to chris yankajtis

Hi Chris and welcome to the UTM Community!

What relevant information do you see in the Web Filtering log when you get this message?

Cheers - Bob

Sophos UTM Community Moderator
Sophos Certified Architect - UTM
Sophos Certified Engineer - XG
Gold Solution Partner since 2005

MediaSoft, Inc. USA
Cancel
Vote Up 0 Vote Down

Cancel
DouglasFoster over 5 years ago in reply to chris yankajtis

Testing with OpenSSL indicates that thinkmobiles.com site requires OpenSSL 1.1.1. I have encountered this on some other sites as well. The .za site in the original post worked with all 3 of my OpenSSL test versions.
Cancel
Vote Up 0 Vote Down

Cancel