Thank you for providing the detailed information. This is very helpful to our investigation. We will investigate it on our side and possibly reach out to them to whitelist that port for us. Sometimes false positives like this can be triggered by bigger patches and things like that. In any case, we will investigate it on our side, for now if it blocks your connection you might need to whitelist on your side. Is anyone else using this same protection and having the same error?