8ch.net is meant to accept only clearnet connections, while Tor users are supposed to use the oxwugzccvk3dk6tj.onion and will be blocked from 8ch.net by cloudflare if detected.
If user tries to lizard r through Tor (torify lizard r or just Tor set as SOCKS proxy) then sometimes cloudflare will serve a 403 page which will cause the page download function to fail (as designed) and the user sees a confusing stack trace.
What should happen is that if a 403 is encountered, and if the user requested clearnet refresh, then the exception should be caught and user should see the message:
8ch.net returned 403 (forbidden). There can be many reasons for this, but a common one is trying to connect to 8ch.net (instead oxwugzccvk3dk6tj.onion) through Tor. If you are using Tor, please substitute r commands with tr (trl, trc, etc).
`8ch.net` is meant to accept only clearnet connections, while Tor users are supposed to use the `oxwugzccvk3dk6tj.onion` and will be blocked from `8ch.net` by cloudflare if detected.
If user tries to `lizard r` through Tor (`torify lizard r` or just Tor set as SOCKS proxy) then sometimes cloudflare will serve a 403 page which will cause the page download function to fail (as designed) and the user sees a confusing stack trace.
What should happen is that if a 403 is encountered, and if the user requested clearnet refresh, then the exception should be caught and user should see the message:
>8ch.net returned 403 (forbidden). There can be many reasons for this, but a common one is trying to connect to 8ch.net (instead oxwugzccvk3dk6tj.onion) through Tor. If you are using Tor, please substitute r commands with tr (trl, trc, etc).
8ch.netis meant to accept only clearnet connections, while Tor users are supposed to use theoxwugzccvk3dk6tj.onionand will be blocked from8ch.netby cloudflare if detected.If user tries to
lizard rthrough Tor (torify lizard ror just Tor set as SOCKS proxy) then sometimes cloudflare will serve a 403 page which will cause the page download function to fail (as designed) and the user sees a confusing stack trace.What should happen is that if a 403 is encountered, and if the user requested clearnet refresh, then the exception should be caught and user should see the message: