0

Relative newbie here...

EC2 instance installed, apache is running and can see the Test Page for the Apache server

I am following the instructions found on http://calebogden.com/wordpress-on-linux-in-the-amazon-cloud-with-mac (the mac portion was no problem as I have FileZila and PuTTY setup successfully to the instance)

The first step in the instructions call for installing phpMyAdmin -- everything went flawlessly until I went to view I can head over and configure my phpMyAdmin

When going to [MY_SERVER_IP] / phpmyadmin / setup / index.php I am getting a 404 for the page. I verified the full path visually within the server, it is legitimate and the index.php file exists on the server.

Tried using both the Public IP (setup through an Elastic IP) as well as the Public DNS without success.

When I go to the Public IP or Public DNS, the Apace test page is available...

Security group has been tested and is setup correctly (otherwise SSH,, FileZila and the Apache test page would not appear, correct?)

What do I look at next to see what is keeping the setup page for phpMyAdmin from appearing?

  • What are the permission settings on your phony admin folders? Public? – Brian Adkins May 12 '14 at 3:34
  • apologies Brain, not following what you mean by phony admin folders... – Learning May 12 '14 at 3:45
  • Damned autocorrect...phpmyadmin folders (sorry). Are they open to the public? – Brian Adkins May 12 '14 at 3:46
  • love those autocorrects... sometimes :-) performed a ls -l for permissions on phpmyadmin and got the following.. >> drwxr-xr-x 10 phpmyadmin apache 4096 May 12 03:01 phpmyadmin << Is a chmod needed for this? – Learning May 12 '14 at 3:47
  • found this gist.github.com/aronwoost/1105007 -- will give it a go, drills a bit deeper than the previously linked post... – Learning May 12 '14 at 3:52
0

As we couldn't find why this was being so funky, and as we haven't this site launched yet, we stopped the instance all together, dropped the volume, installed a new volume and moved forward. All is good, going to take a snapshot, and prepare the site for launching... The only take away we see here is stick with one set of instructions -- we were bouncing between three. Also, develop documentation habits of what you are doing, journal like. Makes it a heck of a lot easier to back track once that 20/20 hindsight kicks in...

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.