My server settings are Apache2 and Ubuntu 9.x

sudo a2enmod SSL

3. Create the server SSL Key

sudo bash

On Ubuntu this changes you to the root user as you cannot access the directory on the next step.

cd /etc/ssl/private

openssl genrsa -des3 -out myserver.com.key 2048

Make sure its 2048 and not 1024 bit as this would be required later on GoDaddy.
Enter keyphrase

5. Create the CSR (Certificate Service Request) to be entered on GoDaddy

openssl req -new -key myserver.com.key -out myserver.com.csr

Upon enter it will ask you for several things but make sure that under Common Name you put your website url (myserver.com). (GoDaddy will throw an error if it is not a correct website)

6. View the CSR and Copy. Paste it later to your GoDaddy SSL Certificate Management

7. On GoDaddy SSL Certificate Management make a Request and choose Third Party, Web Server no Control Panel. And Paste the CSR code.

a. Upon Submit you would get the approval. It would check that your domain registry and administrative contacts to verify.
b. If it cannot be verified via the domain registry, you will be emailed a code that you need to create as a file and upload to your server instead.

8. Install your certificate gd_bundle.crt and myserver.com.crt to your server. Upload them to the server and install. Back to shell

mv gd_bundle.crt /etc/ssl/gd_bundle.crt
mv myserver.com.crt /etc/ssl/certs/myserver.com.crt

9. Edit the default Apache2 values at /etc/apache2/sites-available/default. Create a new virtualhost

NameVirtualHost *:443

DocumentRoot /var/www/
SSLEngine on
SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
SSLCertificateFile /etc/ssl/certs/myserver.com.crt
SSLCertificateKeyFile /etc/ssl/private/myserver.com.key
SSLCertificateChainFile /etc/ssl/gd_bundle.crt

10. Make sure Apache2 to listen on port 443, edit the /etc/apache2/ports.conf
Under

Listen 443

10. Restart Apache

/etc/init.d/apache2 restart

If all went well you should be able to access https

For EC2 make sure Port 443 is enabled as well on the AWS Console

11. Then to force redirect users to https create an htaccess file and upload to your root www folder

RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://www.myserver.com/$1 [R,L]

First upload the .sql file on your server using an FTP client and remember the path.

eg.
For Linux
/home/lopau/mydump.sql

for Windows
C:/wamp/www/lopau/mydump.sql

Login to your server using an SSH client like Putty.

On the command line access MySQL
$> mysql -u username -p password

replace username and password with yours.

On the MySQL client command line access and use your database.
$> use lopaudb;

Now to import your dump;
$> source /home/lopau/mydump.sql;

If successful you should see
Query OK, 13 rows affected (0.00 sec)

That easy.

Yesterday my host changed servers, then I upgraded to the latest version of WordPress and everything got whack on uploading images in the admin with this error.

Unable to create directory /home/username/public_html/wp-content/uploads/2008/05. Is its parent directory writable by the server?

Here are troubleshooting steps you can do.
1. With the error above, it can be assumed it is a permission problem with the folder. Default is 755, With your FTP software or WebFTP, edit the uploads folder in the wp-content to 777. Then try again.

2. If that doesn’t work, it can be an ownership issue. Wherein the owner of the files is apache and not your user account.

If you have access to SSH, you can edit the file to change ownership to

chown -R username:apache_user /home/username/public_html/wp-content/

username:apache_user for me is the ftp account, others are different.

3. If this doesn’t work. Check the upload path in the admin – Settings – Miscellaneous and make sure it is wp-content/uploads sometimes the upgrade or server move changes it to the absolute path.

The 3rd solution worked for me. Hope you find this useful