search

coq / coq.github.io

Source files of the coq.inria.fr website
https://coq.inria.fr/
Other
15 stars 37 forks source link

https://coq.inria.fr does not work anymore from a standard IPv6 browser #192

Closed erikmd closed 2 years ago

erikmd commented 2 years ago

Hi,

Using Firefox-esr on Debian GNU/Linux, I get the following view:

2022-03-09_18-42-13_Screenshot_coq_inria_fr

I made a few other tests, and it seems to be the same issue as https://github.com/coq/www/issues/157

``` $ curl -v https://coq.inria.fr * Trying 2001:41d0:305:2100::8b43:443... * Connected to coq.inria.fr (2001:41d0:305:2100::8b43) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/ssl/certs/ca-certificates.crt * CApath: /etc/ssl/certs * TLSv1.3 (OUT), TLS handshake, Client hello (1): * OpenSSL SSL_connect: Connection reset by peer in connection to coq.inria.fr:443 * Closing connection 0 curl: (35) OpenSSL SSL_connect: Connection reset by peer in connection to coq.inria.fr:443 $ curl -v --ipv4 https://coq.inria.fr * Trying 51.91.56.51:443... * Connected to coq.inria.fr (51.91.56.51) port 443 (#0) … Welcome! | The Coq Proof Assistant … ```

Cc @maximedenes @Zimmi48

Zimmi48 commented 2 years ago

Ping @maximedenes (I think you're the only one able to debug / fix this).

maximedenes commented 2 years ago

Thanks for the report. How urgent / blocking is this issue?

erikmd commented 2 years ago

@maximedenes urgency is subjective, but it's really a blocking bug; to give more details FWIW:

I can reproduce the issue every time I use my GNU/Linux laptop with Firefox and the Wi-Fi of my 4G smartphone.

Then I can't browse Coq's website nor use opam update ; opam install… with the coq-released opam repository.

maximedenes commented 2 years ago

@erikmd Thanks for your patience, it should be fixed now. The fix of #157 was done in a persistent configuration that could still be erased automatically in some scenarios, which seemed to have happened around November 2021. It should be now be fully persistent.

Can you confirm it now works fine for you before we close this issue?

erikmd commented 2 years ago

Hi @maximedenes, sorry for replying late.

Yes I can confirm it's very OK now. Thanks!