fgreco
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: WordPress, AWS, and Elastic IPThe tip on changing the home and siteurl in both the wp-config and in Mariadb seems to do the trick.
Unfortunately I was fixated on getting it to work on Chrome. Safari/Firefox worked fine, which I should have tried in the beginning to lead me to the answer faster. Chrome wasn’t working. For some reason, Chrome was oddly redirecting my static ip address to some other IP addr.
Since Safari/Firefox/curl work, I tried a Chrome incognito window, which worked, so I narrowed down the issue to a local Chrome DNS cacheing issue. After flushing the Chrome DNS cache -> chrome://net-internals/#dns and restarting Chrome, I was able to see the WP login.
@jluizsouzadev, @threadi… I greatly appreciate you taking the time to help! Thank you!
Forum: Fixing WordPress
In reply to: WordPress, AWS, and Elastic IPMy bad. I meant “wp-admin”.
Forum: Fixing WordPress
In reply to: WordPress, AWS, and Elastic IPI hard-coded the elastic IP in the wp-config.php file, and I updated the WP database site_options. They are all pointing to my http://nnn.nnn.nnn.nnn elastic ip.
Safari/Firefox/Opera/curl/Chrome-incognito now show the sample blog page (regular chrome seems to be redirecting for some reason… prob a separate issue). If I append “admin” to the URL, I get “Not Found… The requested URL was not found on this server.” I would have expected the login page for admin would come up.
I still think its a WP config issue and not AWS… Before I associated the static IP, everything worked fine.
Forum: Fixing WordPress
In reply to: WordPress, AWS, and Elastic IPFrom what I understand WP uses the home/siteurl settings in the config file *and* in the mariadb. I’m guessing the config file overrides the DB.
Forum: Fixing WordPress
In reply to: WordPress, AWS, and Elastic IPWhat’s odd is that I can ssh and ftp into the instance fine using the static ip. So it’s not a matter of network ACL. I can even curl the http endpoint from bash. So ports 20, 21, 22 and 80 seem to be open.
Forum: Fixing WordPress
In reply to: WordPress, AWS, and Elastic IPI can still ssh/ftp into the static IP… but WP does not respond in chrome. And in Safari (and curl), I get that odd black-and-white WP blog sample page.
Forum: Fixing WordPress
In reply to: WordPress, AWS, and Elastic IP- Created AWS instance without a static IP. ssh/ftp works
- Installed LAMP – ssh/ftp/http works
- Installed WordPress – works
- Enabled WP debugging; restarted httpd
- Installed Divi theme – shows up in Appearance/themes
- Associated static ip (AWS elastic ip) to this instance – ssh/ftp still work… but WP does NOT.
- I cleared the DNS cache in Chrome.
- I looked for debug logs in wp-content/debug.log … no debug file there.
The only error I see is the Chrome timeout msg:
This site can’t be reached
ec2-xx-xxx-xxx-XXX.compute-1.amazonaws.com took too long to respond.
Not sure where Chrome got that URL. That is not the static IP address. And it is not the initial public (non-static) IP addr from that instance. Odd that when I use curl from the bash command line, I do get that weird blog home page (curl URL | grep -i blog). And when I try another browser (Safari), I get that weird black-and-white WP blog page. When I append “/admin” to the URL in Safari, I get “The requested URL was not found on this server.”
Forum: Fixing WordPress
In reply to: WordPress, AWS, and Elastic IPYes, of course. I don’t expect help with hosting. I greatly appreciate the help here on WP.
However, I get the feeling that WP is somehow hardcoding the IP addr when I install it. And then setting/resetting the static IP (AWS elastic ip) is causing problems. So the two problems seem to be slight related (AWS IP addresses and WP installation).
Here’s my debug plan:
- Using AWS instance *without* using a static ip, install LAMP/WP.
- Confirm ssh/ftp/web access.
- Enable WP debugging
- Try web access (it won’t work) and then inspect debugging logs… and post results.
Sound reasonable?
Forum: Fixing WordPress
In reply to: WordPress, AWS, and Elastic IPTo debug this cleanly, would you suggest I start from scratch and create a new AWS instance and *not* associate it with a static (elastic) IP? Perhaps not getting WP working and the elastic IP are two different issues?
Forum: Installing WordPress
In reply to: Bitnami image on AWS – pricing confusionThanks 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.comHTTP/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: http://ec2-999-888-777-666.compute-1.amazonaws.com/xmlrpc.php
Location: http://ec2-999-888-777-666.compute-1.amazonaws.com/
Content-Length: 0
Content-Type: text/html; charset=UTF-8Connection closed by foreign host.