You're right, we force "secured" SSL implementations since SSLv3 and TLS1.0 are deprecated and not considered secure anymore.
Many thanks for the quick fix ! We'll send this page link to our subscribers who are experiencing this issue until the 3.1 official release.
BR.