Hi,
Can you check the offered cipher using openssl s_client ?
It could be that there is no suggested cipher or changing suggested cipher
between ipv4 vs ipv6, (something that can happen with some farms and other load
balancing systems) .
On Thursday, 11 January 2024 12:18:24 IST Rabin Yash
Nice catch,
IPv4 works, as the moment I remove the address from my interface, I can
connect to the site.
>From what I can see, it does able to complete the TLS handshake, and I can
see the certificate.
And I see the same behavior from inside a container.
Ping to the address seems to be working, a
Looking at the curl output, it manages to connect using IPv6 and is timing out
on the SSL negotiation.
Few things to check:
- Does this work for you with IPv4?
- Can you use "openssl s_client" to see if your environment manages to finish
the SSL handshake?
- Can you try to connect from
I tried both:
curl --connect-timeout 3 -ipv6 https://web.telegram.org/
curl --connect-timeout 3 -Iv6 https://web.telegram.org/
In both cases, the response was prompt.
I am connected to the Internet via Bezeq (as infrastructure provider)
and Partner (as ISP).
I got IPv6 from Partner several
Hi list,
Can you please help me identify if the issue, is in my end / ISP (Bezeq)
and not the service it self.
When I try to load telegram web, with IPv6 address, the connection will
hang for me.
❯ curl --connect-timeout 3 -Iv6 https://web.telegram.org/
* processing: https://web.telegram.org/
*