git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: public-inbox.org down?

From
Stefan Beller <sbeller@google.com>
Date
Apr 30, 2018, 16:39 UTC
Message-ID
<CAGZ79kaKqVyq=y6Ocbhg8Unb2eKLSzNUkE0ZNHBgC1Tvkiu3vg@mail.gmail.com>
In-Reply-To
<CAJZjrdWEgdXmcXuxmF2CH3S6SZT8Lt-3Cw8ZJKiN6fnig-wivg@mail.gmail.com>
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:
Show 14 quoted lines
> 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):
Previous: Samuel LijinNext: Eric Wong
Message 2 of 3 in “public-inbox.org down?”
  1. Samuel LijinApr 30, 2018
  2. Stefan BellerApr 30, 2018
  3. Eric WongApr 30, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.