* public-inbox.org down?
@ 2018-04-30 15:59 Samuel Lijin
2018-04-30 16:39 ` Stefan Beller
0 siblings, 1 reply; 3+ messages in thread
From: Samuel Lijin @ 2018-04-30 15:59 UTC (permalink / raw)
To: git@vger.kernel.org
DNS lookup is working but the website (possibly the server) seems to be
down. The TLS handshake is never acked:
$ curl -v https://public-inbox.org
* Rebuilt URL to: https://public-inbox.org/
* Trying 64.71.152.64...
* TCP_NODELAY set
* Connected to public-inbox.org (64.71.152.64) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: public-inbox.org down?
2018-04-30 15:59 public-inbox.org down? Samuel Lijin
@ 2018-04-30 16:39 ` Stefan Beller
2018-04-30 16:46 ` Eric Wong
0 siblings, 1 reply; 3+ messages in thread
From: Stefan Beller @ 2018-04-30 16:39 UTC (permalink / raw)
To: Samuel Lijin, Eric Wong; +Cc: git@vger.kernel.org
Hi Samuel,
public-inbox.org is reachable from here, which may not add a lot of
information to your debugging.
I cc'd Eric Wong, who runs the infrastructure of public-inbox.org, so
he knows of your problem.
Stefan
On Mon, Apr 30, 2018 at 8:59 AM, Samuel Lijin <sxlijin@gmail.com> wrote:
> DNS lookup is working but the website (possibly the server) seems to be
> down. The TLS handshake is never acked:
>
> $ curl -v https://public-inbox.org
> * Rebuilt URL to: https://public-inbox.org/
> * Trying 64.71.152.64...
> * TCP_NODELAY set
> * Connected to public-inbox.org (64.71.152.64) port 443 (#0)
> * ALPN, offering h2
> * ALPN, offering http/1.1
> * successfully set certificate verify locations:
> CAfile: /etc/ssl/certs/ca-certificates.crt
> CApath: none
> * TLSv1.2 (OUT), TLS handshake, Client hello (1):
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: public-inbox.org down?
2018-04-30 16:39 ` Stefan Beller
@ 2018-04-30 16:46 ` Eric Wong
0 siblings, 0 replies; 3+ messages in thread
From: Eric Wong @ 2018-04-30 16:46 UTC (permalink / raw)
To: Stefan Beller, Samuel Lijin; +Cc: git
Oops, some upgrades went awry for the non-Tor HTTPS endpoint termination.
The Tor .onions should remain available if that happens
http://ou63pmih66umazou.onion/git
http://czquwvybam4bgbro.onion/git
http://hjrcffqmbrq6wope.onion/git
nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git
nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git
nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git
And my monitoring scripts didn't test HTTPS :x Just fixed that, at least.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-04-30 16:46 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-04-30 15:59 public-inbox.org down? Samuel Lijin
2018-04-30 16:39 ` Stefan Beller
2018-04-30 16:46 ` Eric Wong
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).