WordPress Can't Start Up If WP-Config.php Using 444 chmod

[IniBudi]

I find the issue when I used security recommendations from iThemes Security plugin to set wp-config.php to 444 chmod.

After restarting the app or boot the server, the WordPress managed, developer, and LAMP can't start up if we used 444 chmod for wp-config.php.

It's on my machine only or is it bug on Cloudron 8.3?

Thank you
Regards

[nebulon]

Is there some error thrown anywhere, and what is the reasoning to change the access rights of that file to 444 ? Presumably those are too restricted for the unix user running apache.

[IniBudi]

The app won't start up, but after change the file to 644 chmod. The app can run smoothly.

[nebulon]

To clarify here, the file in question is basically a config file and will get updated with for example database credentials during app startup. Not too clear what kind of recommendation this is in the first place, but at least this does not really apply to a Cloudron setup here.

[jdaviescoates]

@IniBudi said in WordPress Can't Start Up If WP-Config.php Using 444 chmod:

iThemes Security plugin

FWIW I used to use that plugin years ago, but I much prefer and recommend WordFence these days.

[girish]

So, this happens because the package wants to re-configure WP with the correct domain , database etc on start up. Making the config file read only makes it not work. Not sure if this is fixable.