I'm not sure what happened, this was just working fine for the 0.11.0-beta.4 release.
I tried to do this manually when SSHed into the node VM and that didn't work either, cURL indicates that we're seeing a TLS negotiation issue:
root@control-0:/home/sysadmin# curl -v https://neon-registry.bc27-29ac-1728-4f00.neoncluster.io/service/token?account=sysadmin
* Trying 10.0.1.29:443...
* Connected to neon-registry.bc27-29ac-1728-4f00.neoncluster.io (10.0.1.29) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* CAfile: /etc/ssl/certs/ca-certificates.crt
* CApath: /etc/ssl/certs
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.0 (OUT), TLS header, Unknown (21):
* TLSv1.3 (OUT), TLS alert, decode error (562):
* error:0A000126:SSL routines::unexpected eof while reading
* Closing connection 0
curl: (35) error:0A000126:SSL routines::unexpected eof while reading
I'm going to comment this code out again.
I'm not sure what happened, this was just working fine for the 0.11.0-beta.4 release.
I tried to do this manually when SSHed into the node VM and that didn't work either, cURL indicates that we're seeing a TLS negotiation issue:
I'm going to comment this code out again.