While I still don't know what was causing the issue, upgrading the Network Security Manager to 220.127.116.11 resolved the problem.
I have the same problem but with the version 18.104.22.168
do you know any solution?
Unfortunately, I don't have any advice for you.
After updating my NSM, I've never encountered this problem again. And, what you see in this thread was the extent of my research.