Wordpress on AWS EC2 - broken after assigning elastic IP Wordpress on AWS EC2 - broken after assigning elastic IP wordpress wordpress

Wordpress on AWS EC2 - broken after assigning elastic IP


Your wordpress admin is already associated with your publicDNS. This is because, when you have logged-in the wp-admin console, you have created a new admin user. This information with respect to your publicDNS was saved in the mysql db. So you won't be able to access wp-admin from the elastic IP.

What you can do ?

You can log-in to your wordpress mysql and update all the references of the publicDNS to Elastic IP. Once it is done, you will be able to access the wp-admin from the static IP.


I run into the same problem. A quick fix is to hardcode your site URL into the wp-config.php which you can edit via FTP.

define('WP_HOME','http://yoursite.com'); define('WP_SITEURL','http://yoursite.com');

Worked fine for me.

See also https://codex.wordpress.org/Changing_The_Site_URL for guideline.


I too faced the same issue, followed the steps in this page to get my issue fixed.

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/hosting-wordpress.html

Follow steps under this section: "Help! My Public DNS Name Changed and now my Blog is Broken"

Pasting it here for quick reference: Login via ssh to your ec2 instance then run the below commands:

  1. Download the wp-cli with the following command

    curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar

  2. Search and replace the old site URL in your WordPress installation with the following command. Substitute the old and new site URLs for your EC2 instance and the path to your WordPress installation (usually /var/www/html or /var/www/html/blog)

    php wp-cli.phar search-replace 'old_site_url' 'new_site_url' --path=/path/to/wordpress/installation --skip-columns=guid