Numerous Issues with new 2021.10 installation

The curl call works for https and gets redirect for http right now.

➜ eaasi-installer git:(a2d2e9e) ✗ curl -v -X POST 'http://eaasi.csuci.edu/emil/environment-repository/actions/prepare'

* TCP_NODELAY set
* Connected to eaasi.csuci.edu (172.30.240.23) port 80 (#0)
> POST /emil/environment-repository/actions/prepare HTTP/1.1
> Host: eaasi.csuci.edu
> User-Agent: curl/7.64.1
> Accept: */*
>
< HTTP/1.1 301 Moved Permanently
< Server: nginx/1.22.0
< Date: Sat, 04 Jun 2022 17:25:30 GMT
< Content-Type: text/html
< Content-Length: 169
< Connection: keep-alive
< Location: https://eaasi.csuci.edu/emil/environment-repository/actions/prepare
<
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx/1.22.0</center>
</body>
</html>
* Connection #0 to host eaasi.csuci.edu left intact
* Closing connection 0

➜ eaasi-installer git:(a2d2e9e) ✗ curl -v -X POST 'https://eaasi.csuci.edu/emil/environment-repository/actions/prepare'

* TCP_NODELAY set
* Connected to eaasi.csuci.edu (172.30.240.23) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: C=US; ST=California; O=California State University, Channel Islands; OU=Academic and Information Technology; CN=eaasi.csuci.edu
*  start date: Oct 22 00:00:00 2021 GMT
*  expire date: Oct 22 23:59:59 2022 GMT
*  subjectAltName: host "eaasi.csuci.edu" matched cert's "eaasi.csuci.edu"
*  issuer: C=US; ST=MI; L=Ann Arbor; O=Internet2; OU=InCommon; CN=InCommon RSA Server CA
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7fa2f3810a00)
> POST /emil/environment-repository/actions/prepare HTTP/2
> Host: eaasi.csuci.edu
> User-Agent: curl/7.64.1
> Accept: */*
>
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 200
< server: nginx/1.22.0
< date: Sat, 04 Jun 2022 17:25:45 GMT
< content-type: application/json
< content-length: 69
< access-control-allow-origin: *
< access-control-allow-headers: content-type, authorization
< access-control-allow-methods: POST, GET, DELETE, OPTIONS
<
* Connection #0 to host eaasi.csuci.edu left intact
{"status":"0","message":"Preparing environment-repository finished!"}* Closing connection 0

That looks good now, it is the expected behavior.

We’ll fix the wait-condition for this check in the upcoming release. It can currently fail too early as-is in the installer, when the backend takes longer to start. For now, you can ignore that error as reported by the installer.

Okay, thanks! I’ll assume things are good to go with the my node then.

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.