EDIT 2:
Läuft wieder
Heyho,
DiscordSRV ist derzeit nicht funktionstüchtig, daher ist der Channel #Server derzeit nutzlos. Nachrichten vom Server kommen nicht in Discord an und vice versa.
Hintergrund ist, dass Discord gestern in der Früh um 2 Uhr die IP unseres Servers gebannt hat.
Ich stehe bereits mit dem Entwickler von DiscordSRV und Discord in Kontakt.
EDIT:
Discord hat alle Verbindungen von Hetzner (unserem Hoster) gebannt, da dieser Discord mit falschen Fehlermeldungen über offene Ports/DDOS-Attacken zugespammt hat.
Läuft wieder
Heyho,
DiscordSRV ist derzeit nicht funktionstüchtig, daher ist der Channel #Server derzeit nutzlos. Nachrichten vom Server kommen nicht in Discord an und vice versa.
Hintergrund ist, dass Discord gestern in der Früh um 2 Uhr die IP unseres Servers gebannt hat.
Ich stehe bereits mit dem Entwickler von DiscordSRV und Discord in Kontakt.
EDIT:
Discord hat alle Verbindungen von Hetzner (unserem Hoster) gebannt, da dieser Discord mit falschen Fehlermeldungen über offene Ports/DDOS-Attacken zugespammt hat.
Feel free to reach out to Hetzner support and let them know. They are the reason this ban is in place currently as they have been unresponsive to our requests, all the while spamming our abuse contacts. Reference ticket number 2017091403020104. It is our hope that their customers who are impacted by this ban will reach out to them and encourage them to resolve the issue - as our attempts to do so so-far have proven futile.
Essentially their automated systems that detects port scans/ddos have been sending false abuse reports to our hosting providers. As such, we've decided to block all traffic to their network from our servers, and drop all traffic from their network on our site as their system has been flooding our abuse queue with basically fake and non-actionable tickets.
This is not a problem that we face specifically, and many other people have faced such fake reports from Hetzner historically:
However, considering we have hundreds of servers across the globe and someone spoofs a hetzner address when trying to syn flood our servers (which happens more than you'd expect), we get an automated e-mail from their abuse department saying we're port scanning their network. This email goes to our hosting providers and ultimately to us need to deal with. We have attempted to contact Hetzner in an attempt to resolve this matter, but they seem unwilling to do so. As such, we've decided to block all traffic to and from hetzner owned IP ranges - to prevent such issues from occurring in the future - as they so far don't want to stop sending us fake abuse reports.
Essentially their automated systems that detects port scans/ddos have been sending false abuse reports to our hosting providers. As such, we've decided to block all traffic to their network from our servers, and drop all traffic from their network on our site as their system has been flooding our abuse queue with basically fake and non-actionable tickets.
This is not a problem that we face specifically, and many other people have faced such fake reports from Hetzner historically:
However, considering we have hundreds of servers across the globe and someone spoofs a hetzner address when trying to syn flood our servers (which happens more than you'd expect), we get an automated e-mail from their abuse department saying we're port scanning their network. This email goes to our hosting providers and ultimately to us need to deal with. We have attempted to contact Hetzner in an attempt to resolve this matter, but they seem unwilling to do so. As such, we've decided to block all traffic to and from hetzner owned IP ranges - to prevent such issues from occurring in the future - as they so far don't want to stop sending us fake abuse reports.
Zuletzt bearbeitet:
.