Https://0x0.st - Secure Connection Failed

I have no idea where this post fits in the forum. I’ll just post here. Mods, feel free to move if necessary.

This has been creeping up on my for a while. I’ve seen images shared here on the forum form the https://0x0.st domain. They never load for me. I always get Secure Connection Failed. No VPN enabled.

FIREFOX:

VIVALDI:

Now it’s happening with eos-sendlog links. Both on the forum and in terminal. In fact, the terminal (Kitty and Konsole) refuse the command inxi -Fxxc0z | eos-sendlog

❯ inxi -Fxxc0z | eos-sendlog
==> 'curl' failed with code 35.
==> Info: 0x0 failed, trying dpaste ...
==> Info: dpaste failed, trying termbin ...
eos-sendlog-helper: error: configured pastebin services failed!

Funny thing is, when I enable Mullvad VPN, everything is fine. Links work as expected in both browsers and both terminals.

:thinking:

All I can say, is it works for me?

1 Like

I’m wondering if this is an ISP issue. Because I can still reach the domain when I enable Mullvad. And eos-sendlog (which uses that domain) works fine with Mullvad enabled.

And nothing is wrong with the domain itself.

That would make sense, due to different DNS and routing with a VPN.

Maybe try Quad 9 as DNS server and see what happens.

You can try testing a connection using openssl, see what it says about the TLS state. Maybe your browser is using it and openssl finds the site’s TLS negotiations shady.

Can’t supply the exact commands at the moment, you might want to google around for that one.

It’s not a browser issue. Just tested Safari on my iPad and Chrome on my Android phone. Neither will connect. However, when I disconnect each from WIFI and use the cellular connection, all is fine.

As I’ve mentioned before .. this is probably the outcome of either your IP being blocked, or more likely - the use of something like a VPN and that IP is blocked. Other options include something like your local network or ISP blocking 0x0.

I can very easily trigger this exact same ‘error’ on 0x0, or my own website, or countless others, by switching my VPN to a different endpoint.

The actual error message is produced by a malformation in the connection - in reality the connection is refused but returns a string when the browser expected the SSL cert.

Just like last time you reported this error.

I “reported the error” in a thread that was not about the error, but an image you posted. A dedicated thread seems better.

Also, as I stated, I wasn’t using a VPN. But using a VPN fixes the issue. Leading me to believe that you are correct in that it’s more than likely my ISP.

But more strange is that I’ve never had an issue with eos-sendlog links until today. So, this is all just strange.

I’ll just enable Mullvad VPN anytime the 0x0 domain is needed.

Folks really can become fixated on the innocuous use of a word.
I had ‘mentioned’ there originally but swapped for ‘reported’ because I opened the post using the word ‘mention’.
Le sigh.

eos-sendlog appears to have at least 3 different hosts it can use (0x0,dpaste,termbin)..
Maybe your previous executions didnt use 0x0?

I’ve also noticed more ISPs making use of some sort of ‘AI’ (or otherwise automated) blocklists, which are generally terrible in their own right, but also seem to be quite eager to specifically add any of the pastebins that are not pastebin.com such as something like this:

Does the over-use of the word ‘use’ not bother anyone else here? :sweat_smile:

1 Like

Frankly, I’ve given up on the current generation’s ability to ‘grammar’ :slight_smile:

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.