Sorry for the technical issues, we are currently working hard on fixing things up. We cannot share more details at this moment unfortunately
its all good! take ur time, what matters is the site is being taken care of! im sure you guys are working very hard to fix it. thanks!!
5k bots and frequent 503/502 errors... something is definitly off, but im glad to see the devs stepping up and taking a look at it
I know some other websites were having problems too around the same time. I haven't had an issue since Monday, I imagine why regular mod approval hasn't happened, is there a lil busy with this.
Guest number just jumped up to around 4000 again and yet another DDOS has hit the forums, took me a few mins to get this page to open in refreshing
It's been insane the last few days. If it is a DDoS attack, all I can really think of is why? The devs don't ever really have backlash or anything, the forums aren't necessarily toxic unless you're toxic yourself. The game itself is the greatest it's ever been. The fact the devs are remaining silent about this and stating that they can't share information about it at this time, is already raising some red flags. That's typically not a good sign. Did someone get banned and is being very anal about it maybe? Even right now as we speak, I connected just fine two seconds ago to load up this page. In the midst of typing this post, I got a "502 Bad Gateway nginx" error. There are like 4,000 guests. I don't actually know how much traffic a DDoS needs to become effective. I figured it'd be somewhere in the 5- or 6-digit range rather than 4-digit range. I swear BeamNG had Cloudflare, though, but I think it's just me being crazy. Whatever the case may be, I hope this isn't going to do lasting damage. Servers don't usually get DDoS'd for days on end like this. Usually only a day or two at most.
--- Post updated --- google also have their super anti ddos protection named cloud armor, Idk, but it seems that devs cannot set it, it was easy for me when i started my site.
For those who are having problems connecting to the website (like the 502 Bad Gateway), please wait for about 30 seconds and try refreshing the page. Sometimes the page will simply display in HTML (with only the text and missing elements), and sometimes the site will appear correctly.