Hi @Flood and Flood's wife sorry, I may have been a bit too early in marking this as fixed. :( Went to basecamp today and exactly the same problem happened. In settings → network settings → encrypted connection scanning I have ‘scan encrypted connections upon request from protection components’ selected. If I change this to ‘do not scan encrypted connections’, basecamp works. I tried this with the traffic processing script untouched - enabled. I tried adding https://3.basecamp.com/ to the encrypted scanning exclusions and also changing the ‘when encrypted connection scan errors occur’ to ‘add domain to exclusions, but only the ‘do not scan’ option allowed base case to work properly. In settings → network settings → traffic processing - if I disable the inject script [and leave the encrypted connection setting as scan encrypted connections upon request], Basecamp works. Once I have toggle the script off, then back on and forcing bascecamp to clear the browser cache then reload on each setting change, the site works - with the original settings with the script enabled. At a very rough guess, it looks like the traffic processing script is conflicting with basecamp’s scripts on basecamp’s initial load. Once I have allowed basecamp’s scripts to load properly, all is fine. Is there a way to disable the traffic processing script for just a specific domain? Thank you for your help, ice70