Answered Upgrade 2.6.4 to 2.6.5 > Error 503: Site temporarily unavailable.

Running Setup:

http://yoursite.com/setup

Also, I assume you meant you meant these:

/www/all-folders-here-except-core/config.inc.php
/www/all-folders-here-except-core/config.core.php

/www/all-folders-here-except-core/connectors/config.inc.php
/www/all-folders-here-except-core/connectors/config.core.php

/www/all-folders-here-except-core/manager/config.inc.php
/www/all-folders-here-except-core/manager/config.core.php

Make sure the core path is correct and ends with a slash in all three.

Indeed, my mistake, it's config.core.php.

Yes:

Did you run setup?

Yes and still the same problem: after the step "Install Options", choosing option "Upgrade Existing Install", then "Error 503" : Site temporarily unavailable.

Sooooo ! Still nothing, I'm stuck.

Why at this step, it's working?



But not at the next one.

I wish I had an answer for you. I don't know what might cause that.

Try watching the network tab in dev. tools in Chrome or FF (Ctrl-shift-i) as you run setup.

You might also go into the DB and look at site_status record in the modx_system_settings table. It should be set to 1.

It might also be worth checking that you don't have any php.ini files causing incompatibilities with MODX. Or that you don't need any php.ini files to make your environment compatible. Time zone being set wrong by the hosting company can be a problem.

Could there be an old .htaccess file present from a previous installation that is causing a problem?

Quote from: andytough at Sep 05, 2018, 12:17 PM

It might also be worth checking that you don't have any php.ini files causing incompatibilities with MODX. Or that you don't need any php.ini files to make your environment compatible. Time zone being set wrong by the hosting company can be a problem.

Could there be an old .htaccess file present from a previous installation that is causing a problem?

What should I search in my php.ini file?
And, more important, why it's perfectly working with the actual website? I don't remember if I told you this point, but the actual web site is www.website.com and the updated site is 265.website.com. Maybe it's the origin of the issue.

Hi!

I asked to my host provider if this 503 error problem could be on their side. This is their answer:

I did some tests, but nothing works. I note that the errors do not come from Apache, which suggests that a parameter is changed in the configuration of this site.
Sometimes it's just a missing file, or a (connection) defect in the site database.

What do you think? Please :'(