![]() I made numerous changes to the server infrastructure that broke this feature, and since we don't make updates to the software often this feature is largely unnecessary. The most important change is that it no longer includes an automatic update feature. To solve these issues with the launcher, I have updated it to a newer version. Issues with A1V1, A1V2, H1V1, H1V2, O1V1 and O1V2 having most of the events happening outside the playable area This time I decided to tackle three simple problems that have been an issue for awhile:Įrror messages appearing when the news feed is loaded Transparency is the best policy when it comes to these issues and I hope you continue to enjoy what GruntMods has to offer.It's been a long time since I've published an update for the GruntMods Edition. We are always working at providing the best possible service and apologize for any interruptions. We are also working with our providers to establish load balancing, which will both improve speeds and availability between different regions, even during peak usage or through similar size DDOS attacks. This provides additional protection against issues with specific regional data centers. Server Redundancy: The Web Server is now located in a Toronto data center, and the file server is located in Montreal.Going forward, additional monitoring will be put into place on both servers to notify us of any issues that occur before they impact performance. Server Monitoring: We have implemented file level server monitoring to notify us of suspicious activity on the file server.New Server Instances: We have deployed additional server instances and reconfigured these with tighter security settings, to cover us against further attacks through other avenues.Increased Security: We have raised the protection level with our partners at Cloudflare, bots and other automated systems will have a significantly harder time visiting the site and utilizing any services we offer.We have taken the following measures to ensure the server is as secure and functional as possible: Several hours after service was restored at 8am, we again saw an increase in traffic matching the profile of the original DDOS attack. Although we have measures in place to prevent automated attacks against our service there is no such thing as a perfect defense and as such the site was taken offline by our hosting provider until the attack subsided. On February 2nd at 3:13am EST and its respective file server was the victim of a DDOS attack. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |