Comments
-
Just to follow up, applying the rule to a packet filter does appear to work. I'm surprised we need to do this as the same exclusions are on the Proxy itself. Thanks for everyone's responses on this issue, it's been very helpful
-
Thanks Greggmh123 - thats useful to know. I'll give it another go as when i tried last time, I was able to save the wildcard settings ok but they were ignored when looking at the traffic log. I must have missed something. I'll report back once I have tried this again.
-
Thanks Greggmh123, we are currently excluding the Windows Update addresses on the proxy as per this The method you are suggesting I don't think will respect the wildcard filters as far as I know? What we found yesterday which was very odd is that when we tested the feature update using a VM with 1 virtual core and 2GB RAM,…
-
Yes, this is what we are doing and the settings are being respected so it's not that causing the issue unfortunately.
-
Hi Bruce, we have done this already and limited the download speed and the Traffic Manager screen shows it's working but it's made no difference. During the Windows Update, our browsing isn't working (going slow first then total timeout) which I assume could be the proxy and if I turn off the machine that's updating,…
-
I don't know if this will help anyone else but following a discussion with a Watchguard reseller, we have been advised to recreate the https proxy rule which we hadn't done since 2015. So far, this appears to have sorted the issue, but it was intermittent but has been ok for over a week now. HTH Chris
-
Same issues here, only started after the 12.5.1 update. We thought it was just us so thanks for posting!