search

projectatomic / container-best-practices

Container Best Practices
Other
166 stars 70 forks source link

production instance is down: 503 #127

Closed TomasTomecek closed 6 years ago

TomasTomecek commented 6 years ago

:<

$ curl -v http://docs.projectatomic.io/container-best-practices/
*   Trying 54.87.143.15...
* TCP_NODELAY set
* Connected to docs.projectatomic.io (54.87.143.15) port 80 (#0)
> GET /container-best-practices/ HTTP/1.1
> Host: docs.projectatomic.io
> User-Agent: curl/7.58.0
> Accept: */*
>
< HTTP/1.1 503 Service Temporarily Unavailable
< Date: Mon, 12 Feb 2018 14:44:55 GMT
< Content-Length: 411
< Connection: close
< Content-Type: text/html; charset=iso-8859-1
<
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>503 Service Temporarily Unavailable</title>
</head><body>
<h1>Service Temporarily Unavailable</h1>
<p>The server is temporarily unable to service your
request due to maintenance downtime or capacity
problems. Please try again later.</p>
<hr>
<address>Apache/2.2.15 (Red Hat) Server at docs.projectatomic.io Port 80</address>
</body></html>
* Closing connection 0

Also, no TLS?

$ curl -v https://docs.projectatomic.io/container-best-practices/
*   Trying 54.87.143.15...
* TCP_NODELAY set
* Connected to docs.projectatomic.io (54.87.143.15) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  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, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server did not agree to a protocol
* Server certificate:
*  subject: C=US; ST=North Carolina; L=Raleigh; O=Red Hat Inc.; CN=*.rhcloud.com
*  start date: Apr  7 00:00:00 2015 GMT
*  expire date: Apr 11 12:00:00 2018 GMT
*  subjectAltName does not match docs.projectatomic.io
* SSL: no alternative certificate subject name matches target host name 'docs.projectatomic.io'
* stopped the pause stream!
* Closing connection 0
* TLSv1.2 (OUT), TLS alert, Client hello (1):
curl: (51) SSL: no alternative certificate subject name matches target host name 'docs.projectatomic.io'
mscherer commented 6 years ago

Yep, that's hosted on openshift 2.0 that got decommisionned. I tought that it was supposed to no longer be used, cf https://osci.plan.io/issues/16?pn=1#note-20

@sanjacloud @jberkus , should we try to move it to Openshift v3 ?

jberkus commented 6 years ago

This is entirely @sanjacloud, she can explain it.

TomasTomecek commented 6 years ago

hi @sanjacloud, I'm sad that I didn't meet you at devconf

ghost commented 6 years ago

@TomasTomecek, we are doing a rehaul of the website. Let's have a call next week - more via email.