2014-08-20 Tags: devops
Self hosting WordPress rocks. Unsecured websites do not rock. It does not matter how long or complicated your password is if it is being transmitted in plain text over HTTP. Luckily, it is easy to create a Self Signed certificate and use it on your website. Keep in mind that browsers become very unhappy with Self Signed Certificates and tend to yell at the user. So, if you have a lot of traffic and want your users to feel safe purchase an SSL certificate from a real Certificate Authority. In any case, at the very least you should be using a self signed SSL for all of the admin portions of your site. Here’s how to do it on Debian 7.5 running a standard LAMP stack.
mkdir /etc/apache2/ssl openssl req -new -x509 -days 365 -nodes -out /etc/apache2/ssl/wp.pem -keyout /etc/apache2/ssl/wp.key2. Create a Virtual Host for your website in /etc/apache2/conf.d/yoursite.conf
<VirtualHost 126.96.36.199:443> SSLEngine on SSLCertificateFile /etc/apache2/ssl/wp.pem SSLCertificateKeyFile /etc/apache2/ssl/wp.key DocumentRoot /srv/www/yoursite.com/public_html <Directory *> AllowOverride All order allow,deny Allow from all </Directory> </VirtualHost>
sudo a2enmod ssl4. Restart apache
sudo service apache2 restartAll set! Now, you can navigate to https://yourwebsite.com, confirm the security exception, and administer and view your WordPress site securely.