Hi Mark,

Please re-import UTM's CA in the end systems. Please refer this link for help : https://www.sophos.com/en-us/support/knowledgebase/115315.aspx

Thanks

Thank you for your reply.  

The link you sent me to states:  

Note: The steps below are only required when using Decrypt & Scan. When using URL Filtering Only, a feature added in UTM 9.2, deploying the Proxy CA certificate is not required.

We are only performing URL filtering.  We are not using Decrypt and Scan.  Also, other https sites pass without issue.  Only google domains seem to be blocked.

One other note, my name's not Tia.  I wrote that to mean 'Thanks in Advance."  [:)]

Mark

Hi Mark,

I totally missed that abbreviation and I will correct it. Did you clear the web browsing history and try google on several browsers?

No problem.

Yes, I cleared the cache and history.  I also tried it on different browsers.  The only way I've been able to get to google.com is by turning off the web filter module.  I have a support ticket open and it's being worked on.  The really odd thing is that I didn't change anything prior to the problem occurring.  I consistently get a "host not found" error.

This seems to be the solution per support:

For the Host not found blocking error, it seems it occurs when the destination IP is reported as blank.


Can you try the following actions and advise back if this helps:

1) go to Network Services > DNS > Flush resolver cache
2) go to Web protection > Filtering Options > Misc > uncheck "Pharming" protection at the bottom of the page 

Hi Mark,

Did the steps helped ? Please DM me the ticket #.

Thanks

I've been using XG230 (SFOS 16.05.7 MR-7) for a short period.

Same problems here.

Isu, you want the XG forums.  There are some here that are familiar with XG, but you are in a UTM forum here.

Cheers - Bob

Thanks for advice, I didn't notice that.
But I think it is the same bug.
Maybe it is related with firmware etc.
I hope it will be solved, the problem is really annoying for beginning with Sophos.

Thanks for advice, I didn't notice that.
But I think it is the same bug.
Maybe it is related with firmware etc.
I hope it will be solved, the problem is really annoying for beginning with Sophos.