Tag: AWS

This is the 3rd and final post in the Running WordPress on AWS Lightsail series. In this post, we’ll set up Cloudflare DNS, Web Application Firewall (WAF) and Content Delivery Network (CDN).

The first step of course, is to get a Cloudflare account. Once you sign in, go to the +Add Site menu selection in the upper right-hand side of the screen.

Next, you’ll add the website the “Add Websites” and let Cloudflare scan it.

It will scan the site and it will display the scanning process.

When completed, it shows “Scan Complete” status and then you click “Continue Setup”.

It shows the DNS configuration settings. Verify everything looks correct. You can make changes on this page.

At the bottom of the DNS settings list, click Continue. Select the Cloudflare Plan.

Hit Continue to the DNS Name Servers screen. These are the servers you updated your DNS settings to in AWS Route 53.

Hit Continue.

It shows the status of Cloudflare. Until the Name Server are updated and replicated out to the other DNS servers, it will show a status of “Not Active”. Once it updated, the status turns green and you can configure the firewall and caching.

This post is the second in the Running WordPress on AWS Lightsail series.

I already had an AWS account for lab testing and demos with my work at Zerto. So if you don’t have one, you’ll need one. I logged in and went to Lightsail.

The rest was really easy. Push the “Create Instance” button, choose the type of instance you want and it spins up in a couple minutes. I picked WordPress.

The AWS Lightsail WordPress instance gets up and running very quickly.

AWS also provides DNS hosting as well. Just click “Create DNS Zone and associate it to IP address shown on the WordPress instance. I didn’t use this because I’m using Cloudflare firewall and CDN.

Instead, I went to AWS’s Route 53 to change to the Cloudflare Name Servers in it. To do that, click on the AWS menu selection on the upper right next to the Billing menu choice.

 

The AWS button takes you to the AWS console.

Scroll down to the Networking & Content Delivery section.

Click on Route 53. It takes you to the AWS DNS Management console.

Click on the Hosted zones.

Here is where you change the Name Servers to the Cloudflare Name Servers.

In the next post in this series, we’ll set up Cloudflare.

A few years ago, I moved over to Godaddy for blog hosting. Yes, I know now that Godaddy WordPress hosting is not good. Keep in mind, I’ve had this blog for 10 years with several different providers and when I moved it to Godaddy, they actually had a better service offering for the money. The operative word here is “had”. Not anymore.

Now that I’ve started blogging again, I quickly discovered that the Godaddy experience for WordPress hosting, well, it’s abysmal. I kept getting hosting timeouts when trying to create a post or just hitting the site. Over the last week, I saw this screen nearly more than any other screen.

The middle part of “Godaddy Firewall”  in the screen shot above originally said “Cloudflare Firewall” because I had Cloudflare set up as a firewall and CDN. I was getting the hosting timeouts and contacted Godaddy support.

Godaddy support immediately pointed the finger to Cloudflare when Cloudflare was clearly showing that it was the WordPress server not responding in a timely manner. So, I decided to eliminate Cloudflare and move everything over to Godaddy firewall/CDN so it would be all Godaddy top to bottom and eliminate the finger pointing.

Of course, this changed nothing. I spent my evenings after work on many support calls or chats last week with Godaddy.  We exhausted all their troubleshooting steps including me allowing them to blow the WordPress installation away and build it completely new.  I had the exact same timeout problems. To my amazement, with a completely new installation of WordPress hosting on Godaddy top to bottom not working any better than before we started, the support guy tried selling me cPanel as a solution. In fact, he was pushy about it. “Can I add this to your account? Can we proceed with adding cPanel?” Unbelievable.

I was clearly demonstrating that WordPress and specifically the wp-admin functionality (the admin screens in WordPress) literally wouldn’t allow me to create blog posts because it was so slow and timing out on a brand new installation. To get the support salesman to move on from sales mode, I questioned him if he thought that creating a blog post was considered basic or optional functionality of the Godaddy WordPress hosting or did they require you to purchase cPanel to do create a simple blog post?

To be fair, not all of the Godaddy support people were like this. I talked to 6 of them over the course of a week and most of them tried to help and were friendly and their response time was good. Note: I talked to 6 different Godaddy support people over the week for a basic WordPress hosting site.

So after a week of constant troubleshooting a simple Godaddy WordPress Hosting installation, I woke up on Sunday morning and decided to fix it. I moved it all over to WordPress on AWS Lightsail. It was done in 5 minutes and was the easiest server deployment I’ve done. Note: I had to talk to 0 support people for AWS install.

If anyone at Godaddy reads this, take this advice please. Tell your support people to never try to sell more services when the service the customer purchased already isn’t working and tell your WordPress team to do installations and eat their own dog food.  They’ll find its unacceptable.

Also, you will be put out of business by AWS or Azure if you don’t provide a better technical experience because AWS is providing a much better technical experience.  Customers will move off your platform very quickly. I did it on a Sunday morning while having my coffee. For example, I also run our church’s WordPress site on Godaddy and I’m moving it too.

In the next post in this series, I show how I deployed WordPress on AWS Lightsail.