WordPress Can't Start Up If WP-Config.php Using 444 chmod
-
wrote on Aug 12, 2024, 2:56 AM last edited by joseph Aug 12, 2024, 2:58 PM
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 -
wrote on Aug 12, 2024, 12:08 PM last edited by
The app won't start up, but after change the file to 644 chmod. The app can run smoothly.
-
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.
-
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
Regardswrote on Aug 12, 2024, 7:29 PM last edited by@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.