2015-01-05, 07:29 AM
2015-01-05, 06:02 PM
Use multiple front-ends, don't have a single point of failure in your network. Mask your network as much as possible with CloudFlare and reverse-proxies. Patch exploits in MyBB such as the avatar method so they can't get your IP that way. Host your MX server on a different server so they can't get IP via mail headers etc. Ensure server services are properly configured not to use up all your resources to help protect against application layer attacks.
There's a lot you can do.
There's a lot you can do.
2015-01-06, 06:33 PM
(2015-01-05, 06:02 PM)Marisa Wrote: [ -> ]Use multiple front-ends, don't have a single point of failure in your network. Mask your network as much as possible with CloudFlare and reverse-proxies. Patch exploits in MyBB such as the avatar method so they can't get your IP that way. Host your MX server on a different server so they can't get IP via mail headers etc. Ensure server services are properly configured not to use up all your resources to help protect against application layer attacks.
There's a lot you can do.
There is a lot you can do but it can all be for nothing. CloudFlare will give out the servers IP address on request.
The best form of protection is by going with a specialist DDoS service which can filter out large attacks. Better spend the money there than by paying ransoms, with protection at least you get some protection but paying out isn't a form of protection as the next guy could come or the same guy returning when he needs a quick buck.
Though of course, try whatever you can and see the outcome. Maybe, just maybe you won't need to opt for an expensive filtering service.
2015-01-07, 05:22 PM
Yeah... The problem has been solved already. I've just forgot to report back.
Moving to OVH, using VPS and coding an anti-DDoS protection did the trick but it also required to disable the logs of the http.
About the guy that said OVH has network issues, I can confirm it since I've experienced it first hand.
When it happens, you won't be able to connect to your server, it will only happen to you at that time and others will be able to browse your website. After 5 minutes it's solved by itself.
Overall, OVH has a stable network.
Currently I'm satisfied. They are a bit pricy though.
Moving to OVH, using VPS and coding an anti-DDoS protection did the trick but it also required to disable the logs of the http.
About the guy that said OVH has network issues, I can confirm it since I've experienced it first hand.
When it happens, you won't be able to connect to your server, it will only happen to you at that time and others will be able to browse your website. After 5 minutes it's solved by itself.
Overall, OVH has a stable network.
Currently I'm satisfied. They are a bit pricy though.