← Back to Upcase

SSL Certificate


(Marc Schwieterman) #1

It seems that the SSL certificate for upcase.com literally just expired.


(Marc Schwieterman) #2

This seems to have also broken the legacy trails.

curl -v https://exercises.upcase.com

  • Rebuilt URL to: https://exercises.upcase.com/
  • Hostname was NOT found in DNS cache
  • Trying 54.225.70.65…
  • Connected to exercises.upcase.com (54.225.70.65) port 443 (#0)
  • SSL certificate problem: Invalid certificate chain
  • Closing connection 0
    curl: (60) SSL certificate problem: Invalid certificate chain

(Emmanuel Delgado) #3

I can’t access any of the trails:

curl -v https://exercises.upcase.com
* Rebuilt URL to: https://exercises.upcase.com/
*   Trying 54.225.150.1...
* TCP_NODELAY set
* Connected to exercises.upcase.com (54.225.150.1) port 443 (#0)
* SSL certificate problem: Invalid certificate chain
* Closing connection 0
curl: (60) SSL certificate problem: Invalid certificate chain
More details here: https://curl.haxx.se/docs/sslcerts.html

(Chris Toomey) #4

Hi there @chischaschos, sorry for the issue here. Looks like our SSL cert had expired. I’ve updated the SSL configuration so we should be all set now.

As an aside, this is a perfect opportunity to mention Heroku’s automatic certificate management which they added earlier this year. It is amazing and will mean that everything is managed for us moving forward!