Jump to content


Photo

HTTPS getting blocked

https blocked 810

  • Please log in to reply
5 replies to this topic

#1 Jayson Webb

Jayson Webb
  • Members
  • 1 posts

Posted 07 August 2018 - 10:09 AM

We have a Barracuda Web Security Gateway 810 and since we upgraded to Firmware v14.0.0.012 last Monday 7/30 we have multiple computers getting blocked from random HTTPS sites even though the sites are white listed. wnct.com and google sites (like google drive and google maps) seem to be the biggest offenders. It seems to be completely random and tied to certain computers and not accounts as in I can access a site under my account on my pc but if I log into user A computer then it blocks me on their PC.

 

The sites work fine when the users go off site but don't work when going through the barracuda. Has anyone come across this and have a solution for it?

 



#2 Marcel Dima

Marcel Dima
  • Barracuda Team Members
  • 26 posts

Posted 07 August 2018 - 11:33 AM

Hi Jayson,
This issue with your WSG needs to be investigated.
Please contact Barracuda Support and open a case.



#3 Michael Greig

Michael Greig
  • Members
  • 166 posts

Posted 13 August 2018 - 01:10 PM

Seems like my hamachi issue...a random https url blocked for a short time.

 

https://community.ba...achi-detection/



#4 Kevin Tavallali

Kevin Tavallali
  • Members
  • 2 posts

Posted 21 August 2018 - 11:59 AM

This is happening to us as well. WSG 310 on firmware 14.0.0.12. Upgraded from v12 last week and randomly, Google drive, maps and music are blocked for certain users. Called support and they had me upgrade the DC agent on our domain controllers but the problem remains. 



#5 Harold Perier

Harold Perier
  • Members
  • 3 posts

Posted 29 August 2018 - 08:40 AM

I have a 610 Web Security gateway with the same issue after update to Version 14.0.0.012 on 8/21. Contacting support now. Don't feel confident after reading these posts.



#6 Kevin Tavallali

Kevin Tavallali
  • Members
  • 2 posts

Posted 06 September 2018 - 08:29 AM

Anyone has success with this issue yet? Please update if a solution or workaround is found.