Comment 3 for bug 1970742

The problem seems to be an issue with the upstream website that this pulls data from (https://tgftp.nws.noaa.gov/data/) which seems to have some odd SSL errors; although it will load fine in a browser and says that it's using TLS 1.2, both this utility and cURL seem to fail due 'unsafe legacy renegotiations' being disabled.

It is possible to override this behavior locally and 'fix' it with a custom openssl.conf (see: https://stackoverflow.com/questions/71603314/ssl-error-unsafe-legacy-renegotiation-disabled) which does allow this utility to work as intended, although with the risk of man-in-the-middle attacks.