A number of Dataverse instances are now unreachable by Python3 on metrics.dataverse.org:
<urlopen error [SSL: DH_KEY_TOO_SMALL] dh key too small (_ssl.c:1129)>
<urlopen error [SSL: DH_KEY_TOO_SMALL] dh key too small (_ssl.c:1129)>
<urlopen error [SSL: DH_KEY_TOO_SMALL] dh key too small (_ssl.c:1129)>
<urlopen error [SSL: DH_KEY_TOO_SMALL] dh key too small (_ssl.c:1129)>
Ideally we would address this on the server-side; another work-around would be to relax the client-side cipher settings.
Update: the pattern I believe I'm seeing by examining SSL certificates is that affected Dataverse instance are using LetsEncrypt for their certs.
A number of Dataverse instances are now unreachable by Python3 on metrics.dataverse.org:
Ideally we would address this on the server-side; another work-around would be to relax the client-side cipher settings.
Update: the pattern I believe I'm seeing by examining SSL certificates is that affected Dataverse instance are using LetsEncrypt for their certs.