fgreco

Thanks for the response, George. I’ve sent requests to Bitnami for pricing info with no response for a week.

I already have an AWS reserved instance (i.e., I paid once for three years) since it’s cost-effective. I want to update that machine instance and use the Bitnami image to install the WP environment. But it’s unclear whether I pay an additional charge to Bitnami (VMware).

I’ll reach out to AWS to see if I can get an answer from them. Appreciate the help.

I am having the same exact issue. After you associate the elastic IP with your AWS instance that is running WP, Amazon puts the public ip addr back into the pool. That is, that ip addr is no longer valid. However, WP seems to think it is. I can FTP/SSH into the new machine fine. WP works fine *before* I assign the elastic IP.

After I assign my elastic IP, things stop working. And I cannot seem to get back to my WP installation either.

For some reason Apache is doing a redirect based on some WP (or possibly MySQL) config. Here’s what happens when I telnet:

% telnet 123.123.123.123 80 <———– HERE’S THE NEW MACHINE AS PER AWS
Trying 123.123.123.123…
Connected to ec2-123-123-123-123.compute-1.amazonaws.com.
Escape character is ‘^]’.
GET / HTTP/1.1
Host: ec2-123-123-123-123.compute-1.amazonaws.com

HTTP/1.1 301 Moved Permanently <—— REDIRECT???? WHY?
Date: Sun, 16 Apr 2017 03:39:28 GMT
Server: Apache/2.4.25 (Amazon) PHP/7.0.16 <—- APACHE IS WORKING
X-Powered-By: PHP/7.0.16
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
X-Pingback: https://ec2-999-888-777-666.compute-1.amazonaws.com/xmlrpc.php
Location: https://ec2-999-888-777-666.compute-1.amazonaws.com/
Content-Length: 0
Content-Type: text/html; charset=UTF-8

Connection closed by foreign host.