![\"\"](\"https:\/\/lamp.ciscoar.com\/wp-content\/uploads\/2019\/06\/digital-ocean-removal-confirmation.jpg\")
<\/a><\/a><\/a>Step two – Deleting Virtual Host file<\/h2>\n\n\n\n
As you probably know, deleting the DNS entries doesn’t stop people (the most tech savvy) to reach your Apache’s Virtual Host if they know the IP Address of your server (VPS).<\/p>\n\n\n\n
That is because Apache still has an entry for your Virtual Host and will send any request coming via the IP Address to the matching Virtual Host, that’s why the next step is then, to delete the Virtual Host file and reload Apache to allow it to recognize this change.<\/p>\n\n\n\n
Finding the right Virtual Host file<\/h3>\n\n\n\n
Use the following image of the Linux directory tree<\/strong> (folders) to see where the Virtual Host files are located, and if you need the path for CentOS 7<\/strong>, here you are:<\/p>\n\n\n\n Just in case you want to double check that what you are doing is the right thing here you can see an screenshot of a typical Virtual Host file, as you can see it is just an small text file.<\/p>\n\n\n\n Depending on your preferences, once you’ve identified the Virtual Host file you want to delete, just remove it either via the CLI using the “rm” command or using the GUI provided by WinSCP.<\/p>\n\n\n\n Note:<\/strong> Remember that when you are removing a file you don’t have to add any argument to the “rm<\/strong>” command.<\/p>\n\n\n\n The follow screenshot shows how to delete a file using WinSCP<\/p>\n\n\n\n Restarting Apache is a task that you’ll get used to more sooner than later, because most of the tasks involving Apache’s files and directories require to restart it, here the CLI command you are going to need for CentOS 7.<\/p>\n\n\n\n Checking or verifying that Apache is back on its feet could be considered an optional task, but in my opinion it’s always at your best interest to make sure the changes you made didn’t affected the normal execution of your web server.<\/p>\n\n\n\n This step can be considered optional if you don’t mind having some files and folders that are not really being used, it’s going to be kind of backup of your website. If you were using SSL certificates for your Virtual Host then, also optional, do find them on your server and delete them too.<\/p>\n\n\n\n If your website was running on WordPress, then there is an additional step for you, I’m talking about deleting the WordPress Data Base, that task can be done either via the CLI or if you prefer the GUI fashion then you can count with PHP MyAdmin<\/strong> for this task.<\/p>\n\n\n\n As you can imagine, Data Bases are the main processor and memory consumers so this step shouldn’t be optional because every time you are removing an Apache’s Virtual Host you’ll want to get back as much resources as possible to improve the performance of your server.<\/p>\n\n\n\n We’re going to use phpMyAdmin to delete the Data Base because its GUI makes this task a lot easy.<\/p>\n\n\n\n\/etc\/httpd\/conf.d\/<\/code><\/pre>\n\n\n\n<\/a>Example of a typical Virtual Host file<\/h3>\n\n\n\n
<\/a>Deleting the Virtual Host file<\/h3>\n\n\n\n
rm virtual-host-01.conf<\/code><\/pre>\n\n\n\n<\/a>Step three – Restart Apache<\/h2>\n\n\n\n
sudo systemctl restart httpd<\/code><\/pre>\n\n\n\nStep four – verify Apache status <\/h2>\n\n\n\n
sudo systemctl status httpd.service<\/code><\/pre>\n\n\n\n<\/a>Step five – Remove Virtual Host files<\/h2>\n\n\n\n
The truth is that most of the times people just prefer to remove all these files and folders to have a clean OS and save some disk space at the same time, it is totally up to you.<\/p>\n\n\n\nStep six – Delete WordPress Data Base<\/h2>\n\n\n\n
<\/figure><\/figure><\/a>