Reply to thread

Message

<blockquote data-quote="Rebel" data-source="post: 457797" data-attributes="member: 65125">That’s him? Lmao oh no today he’s messaged me but I’ve yet to have been downed[ATTACH=full]10250[/ATTACH]On topic, for the most part I’d suggest hosting your website aka cms and swfs on a protected cpanel host, and using a Protected TCP Proxy, HAPROXY, Or Nginx Proxy, for your client. Which could easily be done by yourself for under £8 using Centos 6-7 Server. Also I’d say use bitninja to block and filter attacks and host your emulator on a vps with only tcp ports open. Also would recommend not hosting your emulator and database, MySQL on the same server Incase of attacks on your query which could prevent cpu spam and emulator crashes.P.SI’ve also noticed adding Google reCAPTCHA, and having it display. Only if login attempts are failed or empty and of course any other submit forms submit. Also making sure pages that require a db query or pages you’d have to be logged into your account view should be done as well. So if someone views a page and their not logged in it sends them back to /index.All these things will help lower your risk of being downed so easily.</blockquote>

[QUOTE="Rebel, post: 457797, member: 65125"] That’s him? Lmao oh no today he’s messaged me but I’ve yet to have been downed [ATTACH=full]10250[/ATTACH] On topic, for the most part I’d suggest hosting your website aka cms and swfs on a protected cpanel host, and using a Protected TCP Proxy, HAPROXY, Or Nginx Proxy, for your client. Which could easily be done by yourself for under £8 using Centos 6-7 Server. Also I’d say use bitninja to block and filter attacks and host your emulator on a vps with only tcp ports open. Also would recommend not hosting your emulator and database, MySQL on the same server Incase of attacks on your query which could prevent cpu spam and emulator crashes. P.S I’ve also noticed adding Google reCAPTCHA, and having it display. Only if login attempts are failed or empty and of course any other submit forms submit. Also making sure pages that require a db query or pages you’d have to be logged into your account view should be done as well. So if someone views a page and their not logged in it sends them back to /index. All these things will help lower your risk of being downed so easily. [/QUOTE]

Verification

Reply to thread

Connect with us

Newest members