I've uploaded the files, verified permissions and set up the database. When I run the install, I see the monkey, and I enter in my details. It appears to go well, until a screen showing only: "Oops"

Using Ben Croker's Craft Requirements Checker, I get:


Minimum requirements met. Craft can run on this server!!

The server is running MySQL 5.1.56 with InnoDB, so I believe it's capable of running Craft.

Any advice?

  • @JimKrenz If you want to shoot some FTP/database credentials over to support@buildwithcraft.com, we can look at it and update the thread here with the results. – Brad Bell Aug 1 '14 at 17:37
  • @BradBell — Sent. Thanks for taking a look at it! – Jim Krenz Aug 1 '14 at 18:29
  • Did you sort this, I'm getting the same error over and over again.. – Etheya May 11 '15 at 12:26
  • I'm also getting this on a local Windows install of Craft 3 running WAMP. Don't have time to troubleshoot it right now, but will try post back if I figure it out. – Simon East Jun 15 '17 at 4:01
  • 1
    This question is very closely related to Does Craft have an installer error log I can check? – Simon East Jun 15 '17 at 4:04

The cause of this is most likely an overloaded (very common if this is a shared hosting account) or misconfigured MySQL server.

The installer itself should only take 10-20 seconds on 99% of hosts. However on this one, it sits for about 120 seconds, before Apache redirects the AJAX request to:

'p' => 'internal_error.html',

As seen from your log files. The underlying error is probably being logged in your Apache error logs, but it is most likely something related to a timeout from the long request.

If I try to manually execute the SQL from a database dump that is working, removing Craft from the equation entirely, it does finish in time, but still takes about 45 seconds when it should be done in less than 10.

I'd contact your host and ask them to check on the performance/configuration of your MySQL box.

  • Thanks for reporting back Brad! Is it possible to provide information like this on the "Oops" screen? As it stands now, "Oops" isn't very helpful. :) – Lindsey D Aug 1 '14 at 19:50
  • The problem with PHP and fatal errors like this is there isn't a graceful way to recover, much less get any information about the underlying error from PHP. They aren't normal exceptions that can be caught and dealt with in a try/catch block. – Brad Bell Aug 1 '14 at 20:00
  • Fair enough, that makes sense. Thanks for the explanation! – Lindsey D Aug 1 '14 at 22:34
  • I am troubleshooting this with the host, as they are claiming that there aren't any issues with the server that is hosting my database. So, I am not considering this answered as of the moment. – Jim Krenz Aug 2 '14 at 3:36
  • Of course they are. :) Which host is it? – Brad Bell Aug 2 '14 at 4:07

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