So some fag reported us to the proxy hosts, and I was politely told to fuck off within 24 hours about ~8 hours ago. All of the existing proxies are on the chopping block and there's really no appeal I can make.
But I'm not quitting
BECAUSE THE FAGGOTS THAT DID THIS ONLY HELPED MAKE THE SITE STRONGER
I already have a proxy on a host in a certain part of eastern europe that has far worse customers than zzzchan, they will not give a shit no matter what we do here. It's also a much better server, and should hold up fine on it's own for a long time without the need for an array. Smaller satellite proxies may come into play later but for now I won't be dealing with load balancing issues. I had hoped to float by with the array on normal hosts for a bit longer since it would have been cheaper but at this point paying a tiny bit more isn't the issue.
Eta on the new proxy is within the next 2 hours, might be later but i have until tomorrow afternoon. Its not hard to set up. If the site breaks in that time frame I'm in the middle of switching over. The onion will be deactivated while redirecting and will come back after the switch
On the plus side, zzzchan is now even harder to kill thanks to this
The app server remained obfuscated through all this and can still be hosted wherever I like. With the proxy soon to be on a no-fucks-given host there is effectively nobody to report the site to. We cannot be deplatformed, reported, or ddos'd, and all spam has to be done manually while requiring a triple digit IQ. Manual spam is really the only attack vector I have to worry about now and Pasta & Seagull have been fantastic in helping deal with that.
ZZZCHAN LIVES FOREVER
>was politely told to fuck off within 24 hours
For what purpose? What does zzzchan even do that's not okay or do hosts just take down websites any time someone cries hard enough?
Loli, more and more hosts are apparently not permitting it at all. And yes someone bitching about it was enough.
In the case of hypothetical no clearnet viability at any point in the future will the site remain accessible as a hidden service?
Truly these are the dark times.
So, that was the reason for the downtime yesterday somewhere at 8-10AM UTC?
Several proxies got turned off (but not deleted) at the same time. Not all of them went off but anons getting routed thru them had issues. I was able to turn them all back on.
alright the new proxy is in place and origin IPs are being passed. The onion is broken but I will be fixing that shortly.
I had gotten a 522 error when I tried to post earlier, which was likely related to what you're describing. Thanks for the update and for being a good admin.
Was there any potential for lost posts? I was making a post in the fighting game thread on /v/ and I decided to copy it to a text file while my browser tab was freaking out. Just a few minutes ago I looked at the text after reloading the page and the post I was replying to, >>>/v/32071, doesn't seem to exist in that thread.
Oh, wait. I just had a look at the logs and the post was apparently deleted for being spam. That shouldn't have happened - I remember seeing it, and it definitely wasn't spam.
Ah shit, looks like i accidentally took it out alongside a bunch of adbot spam, my bad.
Ah, so that's why the onion is giving me a 502 error.
>The onion is broken but I will be fixing that shortly.
You said this nearly 24 hours ago. Is it supposed to be working now, or am I experience a different issue with my Bad Gateway errors?
Sorry about that, I tightened up some of the iptables config and am working to get it to talk to the proxy. Current status:
Onion can be accessed itself and is running, but is not whitelisted on proxy. Once Whitelisted it will work fine
Onion still giving errors
Onion is still down.
500 Internal Server Error
Fixed now, I had a couple settings mixed up. Let me know if there are any more issues/
It works now.
The onion keeps going down randomly and it's getting annoying.
Never mind it's not related to the site, all hidden services have been going down because of an attack on tor.
>For a few hours today all v3 onion addresses on the Tor network were down. This appears to be a new kind of attack which affects the entire network and involves overloading the consensus authority nodes.
>You will currently not be able to access any v3 onion addresses, what is happening is unknown, but it is potentially a huge attack on the entire network. Earlier today I made a post outlining consequences I would be putting into place to deter markets from funding DDoS attacks against each other, as the potential to scale and completely kill every node on the network is a very real potential outcome. Now everything is down and I have no idea if this has sped up the process of this occurring or if it is even an attack at all, all I know is, this is big.
>Reddit post by u/hugbunt3r This attack began after Dread forum owner, HugBunter made a post stating the consequences for market owners who continue to attack rival markets.
I was under the impression Tor was not centralized in such a way?
>The Tor network is not fully decentralized. When you first connect to the Tor network there is hard coded IPs that your Tor process uses to bootstrap your connection into the Tor network. These IPs allow your Tor process to load up the network’s consensus. This consensus tells the Tor process things like what relays are within the network, which are good relays, bad relays, which are guards, exit nodes, how much traffic a relay can handle, that kind of idea. Your Tor process gets all that information and validates it by signatures of these hard coded IPs. These hard coded IPs are called authority nodes. There is currently 10 of them on the Tor network. And they are why the Tor network cleared out V3 onions for a period of time.