It seems that a lot of GPU problems revolve around specific versions of drivers. Though NVidia has their own support structure, you can often learn from information reported by others who fold.
GPUs.txt is public information and there's no need for a secure connection. In my case, FireFox reports that the secure connection cannot be established because: fah-web.stanford.edu uses an invalid security certificate.
The certificate is only valid for fah.stanford.edu
It's an unnecessary hassle to establish a separate security certificates for both fah-web-. and fah.- when nobody cares if the file is intercepted by a hacker.
Again in my case, FireFox allows me to make an exception for the fah-web. certificate, but as Joe has said, removing the "s" is also a reasonable way to access the file.