Thread

Hi there,

I’ve done a fair bit of EE upgrades but I seem to be running into an odd issue with this current upgrade.
The site I’m trying to upgrade is EE 2.1.3 and following the outlined update instructions I backup all the important bits, then copy over the new files and then place config.php and database.php back into their proper directory.

However after doing all this and then visiting domain.com/admin.php all my browser (Chrome/Mac) tells me is “The page you requested was not found.” even though the admin.php file is clearly in the root folder of the site’s filesystem (trying to visit /system also triggers this message).

Chrome occasionally also throws this error upon refreshing the page while showing the previously mentioned error:

Access to the webpage was denied
It is likely that the server hosting the webpage has been overloaded or encountered an error. In order to avoid causing too much traffic and making the situation worse, Google Chrome has temporarily stopped allowing requests to the server.

If you think this behavior is undesirable, for example, you are debugging your own website, please visit the chrome://net-internals/#httpThrottling page, where you can find more information or disable the feature.
Error 139 (net::ERR_TEMPORARILY_THROTTLED): Requests to the server have been temporarily throttled.

I’ve checked my permissions, config and database files are set to 666, and I’ve even tried setting all files to 777 nothing seems to correct this error.

Any ideas as to what could be causing this would be much appreciated.

Thanks,
Jannis

Hi Jannis,

I’m honestly stumped on this one. I don’t believe I’ve ever seen it before. Could you use the tool here to test and see if another, reliable server can access your page? If so, then it looks like it would be something specifically related to your Internet connection.

If the Pingdom tool cannot connect to your /admin.php page either, then it’s likely something on the server side. Could you take EE out of the equation for the sake of troubleshooting and just attempt to load a stand-alone test page in your browser from your server’s web root?

Hi Kevin,
sorry about the delay in getting back to you.

I’ve run through all imaginable scenarios, including disabling extensions, uninstalling addons, updating all addons before the upgrade, triple checking permissions, you name it I’ve tried it.

All of this is running on my local Mac Pro (MAMP Pro + Mac OS X Lion) dev machine which all other EE sites also run (for local testing only obviously) on without issues.

Oddly, while the /admin.php file still gives me the error “The page you requested was not found.” even though it is in the filesystem and the permission of both the file and the parent folders are intact.

What I would like to do is give you read access to my private Git repository since I have exhausted all possible upgrade scenarios without a resolution, so perhaps there is something else going on that might be easier to debug if you had access to the files and the SQL db itself?

If that is something you’d be able to do with me, it would be great if you could give me your email (feel free to PM it if you don’t want it public) so that I can invite you to the private BitBucket repo and email you the DB.sql file for the site.

I’d really appreciate your support with this,
kindest regards,

Jannis

Just a quick note, while I remain unable to upgrade locally, I uploaded the entire broken project onto my Linux server and in the live environment the update worked.

So while I am now running the latest version EE, I still cannot perform this update locally even though I used to be able to do so.

Very odd.

I’m very glad to hear that you were able to successfully upgrade. Unfortunately, we’re not really set up to help troubleshoot servers, and it sounds like there’s something configured incorrectly with your local development server. The only thing I could recommend there would be to work with the folks at MAMP to make sure you have your dev server properly configured.

Is there anything else I can do to help?

My situation’s the opposite. I ran the update from 2.3.0 to 2.4 fine on my local install, but when I try to do it on the live server, I get the same ‘The page you requested was not found’ error message when accessing the admin but only when the installer folder is in place. If I rename the installer folder on the live server I can access the admin login page but I obviously can’t complete the database upgrade.

I ended up recreating the db changes manually for this update.

Hello John,

It sounds like your manual changes made the update successful. Is that the case.

Is there anything else we can help you with?

Cheers!

The manual changes got me over the line with that particular site but I’d rather not have to go that route for every upgrade I do. I haven’t attempted another upgrade so far but will be doing another later today.

I’m glad your current situation’s resolved, John, but obviously that’s not a long-term solution. Let me ask you to do this: try out a test upgrade on that server and let me know what happens by opening up a new thread. Try to be as detailed as possible and we’ll take it from there. Thanks!