Change your site DNS to cloud flare, hopefully your DSN is not cached for long time…
Login in your cloud flare click on:
-> Cloud Flare settings > Security settings > Basic protection level
Change it I’m under attack.
Next step contact your host provider and change the IP that was your site pointed to… (Do this after your protected fully by cloud flare, then change the IP on cloud flare.
Don’t forget to disable the direct subdomain with cloud flare as you don’t want your attackers to find your new real IP and if you have a mail server on the same server make sure to use reverse proxy for the mail server as well.
It’s guaranteed your website will run back without any issues.
If you have 20USD/month for the site you better make the Pro Plan on Cloud flare.
Usually most of the companies that I worked with used to spend thousands of Euros on buying bigger firewall’s, load balancers and multiple servers to handle DDOS and better performance but at the end if DDoS has a point (IP) to hit the firewall wont handle the huge requests of UPD and TCP attacks…
With Cloud flare you can forget about UPD/TCP attacks, your real IP’s are protected from public as the first layer of your site will be on reverse proxy and no one will know what’s your real IP and with this layer you have to worry only on port 80 attacks, which are also handled by cloud flare awesome team and lots of requests will be blocked… cloud flare has big database that will block any potential bot or infected IP’s.
So UDP and TCP attacks are out of order for now, the port 80 attacks which are nasty but cloud flare is good to handle them as well.
Here is a print screen of the IP’s my site is resolving on:
What other benefits you will receive with cloud flare?
As i work in a team that manages about 12 servers world wide we were always suffering to find out which server isnt functioning or which server is acting weird, we tried many smart monitoring that were given from some leasing and hosting companies but unfortunately all weren’t enough till my colleague Charles found PRTG online and we started playing with it!
Rock and Roll… the inhalation can take up to 5 minutes and you will have a ready software that can check everything on your server or PC…
As for us because we are more interested in web application health, we installed http sensors to websites and we monitor when an server is not responding we receive an email, push notification for your android http://www.notifymyandroid.com/
PRTG Installation video:
Are you a developer and need to monitor your sites?
As developers or freelancers we always get a call from clients my site is DOWN!!! and we are like huh!!
With PRTG we will know faster then a client if the website is not responding anymore, in my case i installed a PRTG on my home network on a windows Virtual machine and used the 10 free licenses to monitor some of my key websites, if the website is not responding to http health i know which site is down and ill contact the hosting company or go on the server to check whats going on!
Wait it gets better!! if you have your own server hosted or dedicated machine… we all know sometimes IIS has memory leaks and if the server is old and IIS is acting up sometimes you can install PRTG on the server create a trigger job with IISReset (as batch)! if the memory/CPU reach some high levels why not try restarting IIS first? and checking the logs after to figure out whats going on…!
You can also create batch files that can do jobs for you for each scenario on your server, its cool FREE! and fun! enjoy the game
How to create a wordpress in command line on centmin with centos6 & nginx & mariadb
Add Domain host
Click on 2
vhost for yourdomain.com created successfully
vhost conf file for yourdomain.com created: /usr/local/nginx/conf/conf.d/yourdomain.com.conf
upload files to /home/nginx/domains/yourdomain.com/public
vhost log files directory is /home/nginx/domains/yourdomain.com/log
Add those lines if you want to use the WordPress Permalink
Add in locations:
mysql -u root -p
CREATE DATABASE yourdatabase;
CREATE USER 'youruser'@'localhost' IDENTIFIED BY 'yourpassword';
GRANT USAGE ON yourdatabase.* to youruser@localhost IDENTIFIED BY 'yourpassword';
GRANT ALL ON yourdatabase.* to youruser@localhost;
go to your domain for example:
follow the WordPress installation after install don’t forget to add this plugin:
After WordPress Installation nginx Compatibility plugin: