🥂 New Year Discounts! To celebrate the new year, all new orders will receive 25% off their first month! This means it’s easier than ever to upgrade or try out our cutting-edge game server hosting. Join our Discord and be part of our community!
NeoProtect: Preparing for the Switch
Over the past few months, we’ve been testing NeoProtect in collaboration with a few of our clients. After several weeks of testing and confirming that it matches our expectations, we’ve decided to migrate all nodes from DataPacket to NeoProtect’s DDoS protection.
This document covers everything you need to know about this change, including what you must do to ensure a smooth transition.
What is Changing?
- After extensive testing with a few clients to ensure the new product met our standards, we’re now improving the DDoS protection on all our nodes, enhancing our ability to prevent attacks from disrupting your server(s).
- As a result of the DDoS provider changing, your server’s IP will change, requiring you to modify your setup to ensure players can still connect to your server and that plugins work as they should.
Why are we Changing DDoS Providers?
To provide clients with the best possible service, we have tried several DDoS providers, such as Cloudflare and DataPacket. Ultimately, while each provider excelled in certain aspects, some of our clients were occasionally affected by undetected/mitigated attacks.
Due to these concerns, we looked further. We trialed NeoProtect and found its performance to exceed our expectations, prompting us to initiate a complete provider change so that all our nodes could use this effective protection.
While our providers used to primarily focus on the “general market,” such as Cloudflare, which excels at web-based DDoS protection, NeoProtect is centered around games and thus more specialized for us as a game hosting company.
How does this affect you?
As far as you are concerned, only two things will change:
- The DDoS protection will come at no additional cost.
- The IP address and ports of your server(s) will change.
Since the IP address will change, you must modify certain things to ensure that everything works as it should.
What you need to change
- Configuration files: Any files containing an IP address or port must be modified so long as the IP address is not
0.0.0.0,127.0.0.1, orlocalhost. Example plugins such as Bluemap, Dynmap, and ItemsAdder would require configuration changes. - Note that if you use a proxy like Velocity or Bungeecord, you will have to edit their configuration files so that the IPs of the servers they forward match the new IP or that the proxy is binding to the correct port.
- Premium/Licensed plugins: Some premium / licensed plugins authenticate users through an IP whitelist. If the IP changes, the plugin will be rendered unusable; you must update the whitelist or inform the plugin support about the pending IP change.
- DNS records: If your users connect through your custom domain, such as
mc.mywebsite.com, or reverse proxies, you must modify the records to match your new IP and port. - A record: Change the IP address to the new IP.
- SRV record: Change the port only.
- Database settings: If your plugins use a MySQL database, open its configuration file and modify the IP address.
- Reverse proxies: If you use reverse proxies, you must delete and recreate them after updating the DNS record. See Set up a Reverse Proxy if you need instructions on how.
If you require further assistance, you can open a support ticket here.
Feedback and suggestions can be submitted here, or further discussed on our Discord server.