505 Gateway Error - pool.burst-team.us
-
@solargravity It's a DoS attack on the pool. It affects the pool display, but not the mining.
-
@darindarin Oh that's great news thank you!
-
and when will the display be fixed ?
-
@haitch Okay I feel way better knowing this. I was really worried.
Nevertheless, I'm happy to be a part of the burst community and I'm looking forward to learning and discovering the fun of mining with the rest of the miners.
Thank you again!
SolarGravity
-
@VerdommeMan Display issues will stop when the pool stops getting attacked - but as I said, it's only a display issue. If you reload the pool it'll show you the previous rounds, that it's mining on them, and winning on some of them. The attacks vary over which pools they're going after, so at different times different pools will exhibit the issue.
@solargravity You're welcome.
-
Can you block the originating IP address, either at the firewall level (to kill HTTP requests) or further upstream at the ISP level (to kill network-level floods).?
-
@cryptojam bo, they come from hundreds of addresses. I tried the wack-a-mole aproach, but the moles appeared faster than I could hit thwm, and hit some innocents.
Instead went to divide and conquer - they can hit all the pools, but they can't all at pnce.
-
I was thinking last night that these attacks could actually hurt the pool. If a newbie is joining and having these issues it could deter them from joining or enjoying the discovery process like we all went through in the beginning.
Nevertheless, hopefully this will be resolved soon. I know that a level of the fun is being able to see the metrics.
What do you think?
-
@solargravity That is the whole point - take the pools down to the point they can't mine, and failing that; stop them from displaying. They can no longer stop my pools mining, so they go after the display - I'm working on it.
-
@haitch Thank you for your vigilance. You give me hope that we can solve this!
