Re: TLS connect error: "an EOF was observed that violates the protocol"

Rodrigo Arias <[email protected]> Wed, 28 Aug 2024 23:02:38 +0200
Newsgroups gmane.comp.web.dillo.devel
Message-ID <[email protected]>
Hi,

>I have confirmed that this patch prevents Dillo from crashing.
>Thanks!

Nice!

>> However, it doesn't explain the EOF you are getting in narkive. Are
>> you using tor or some proxy?
>
>No vpn/tor/proxy. I wouldn't be surprised if my network provider was
>doing some weird stuff though... Maybe thats an area for further study.

Look at what I just found:

hop% torsocks curl -v https://narkive.com
* Host narkive.com:443 was resolved.
* IPv6: (none)
* IPv4: 149.248.211.108
*   Trying 149.248.211.108:443...
* Connected to narkive.com (149.248.211.108) port 443
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: none
* OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to narkive.com:443
* Closing connection
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to narkive.com:443

Same if I pass Dillo traffic via tor.

I think your IP may be banned from narkive. Try in some days or reset 
your router if you have a dynamic IP. Or mail them if persists.

Best,
Rodrigo.
_______________________________________________
Dillo-dev mailing list -- dillo-dev-lx9mn2B4QYRWk0Htik3J/[email protected]
To unsubscribe send an email to dillo-dev-leave-lx9mn2B4QYRWk0Htik3J/[email protected]