6
votes

Running into an odd issue with a getting a successful localhost install of ExpressionEngine 2.5.3.

I am able to run the ExpressionEngine Installation and Update Wizard where server settings, database setting and admin account information is entered. So the Apache side is working as expected, or so I assume.

The issue crops up when I click on the Install ExpressionEngine button — the point where the installer starts working it's magic — get this error:

A Database Error Occurred
Unable to connect to your database server using the provided settings.
Filename: controllers/wizard.php
Line Number: 1532

For the SQL Server Address, Username and Password, I am using the same values I have used in the past: localhost for the server address, root for the username and root for the password.

Those credentials work when used with Sequel Pro 0.9.9.1.

Permissions on config.php and database.php — both empty files — are set to 666, as suggested by the ExpressionEngine installation documentation.

I am trying this on a MacBook Air running 10.8.2 with the built-in Apache and MySQL running via XAMPP. I am using VirtualHost X to so http://baseline.loc/ points to baseline.loc in my Sites folder. There are no other instances of Apache or MySQL running.

I am not well versed debugging server issues but I am comfortable working in the terminal.

Any ideas what I should be looking at to figure out why this usually basic stage of a new project has become a stumbling block?

2
can you try the process over with a fresh DB? - Natetronn
Created a new database (basecamp_alpha) and same error message. - Brooks Seymore
Just for kicks and giggles have you tried the server wizard? - Natetronn
Nah, I know EE runs on this machine. Turned out using 127.0.0.1 instead of localhost was all I needed. - Brooks Seymore
Off topic, but I find this permissions setting script handy anytime I install or migrate Expression Engine. - quickshiftin

2 Answers

11
votes

I've had issues before using localhost as the host. Does 127.0.0.1 work for you?

3
votes

I've had similar in OSX using mamp, simply changed the folder permission of the web folder to everyone read/write via finder and that did the trick