install fails since there is no install/status.json

I downloaded Suite 7.10.6, unziped to my server and tried to install.
But it gives error:

GET http://site/install/status.json?0.04175215747296601 404 (Not Found)

Directory install doesn’t have any status.json !!!


I don’t have that file either, in my installed version. If I’m not mistaken, it’s just a small file the installer writes to save information about the installation it’s doing:"status.json"&unscoped_q="status.json"

You probably have an error in php_errors.log or install.log complaining that it can’t write that file. This could be due to permissions issues, or web server configuration issues (.htaccess).

Anyway please check the logs so we can have some more clues about this issue. Thanks

1 Like

Thank you!

The permissions on the
should have also

sudo chmod -R 775 install
(for the installation at least)

sudo chmod -R 775 config_override.php 2>/dev/null
is incorrect, it should be
sudo chmod 775 config_override.php 2>/dev/null

Thanks, I’ll fix the Docs to remove that “-R”.

About giving 775 to the install directory, I wasn’t aware that that directory needed to be written to, during the installation. Anyway, 755 and 775 are the same thing in practical terms, if your files are owned by the same user that your web server is running under.

If however, in your set up the files are owned by the same group (not user) that your web server uses, then 775 will make a difference. Can you please confirm if that is the case?

And have you installed successfully now?

Yes the installation was sucessfull.

After install the permissions were re-established (755 for install):

drwxr-xr-x 58 apache sg_suitecrmdev 4096 Jun 18 15:30 include
-rwxr-xr-x 1 apache sg_suitecrmdev 2374 Jun 5 11:21 index.php
drwxr-xr-x 6 apache sg_suitecrmdev 4096 Jun 19 14:43 install
-rwxr-xr-x 1 apache sg_suitecrmdev 25325 Jun 19 14:43 install.log
-rwxr-xr-x 1 apache sg_suitecrmdev 31893 Jun 5 11:21 install.php

And what is the user that your web server is running under?

(I’k just trying to understand what happened)


Ok, I don’t understand, then :slight_smile:

Because if web server is Apache, and files are owned by Apache, it’s always the first digit in the permissions that will take effect, so 755 is the same as 775, it shouldn’t make a difference, 700 should work just as well. Unless some .htaccess is interfering…

But ok, we don’t have to understand everything…