Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
Frederick Gams Posted February 16, 2022 Posted February 16, 2022 If I change the email settings in the ACP and hit save, everything looks good. If I then browse elsewhere and come back, the setting revert to what they were before. The system logs have the following error: Could not write to Store-FileSystem (acpNotificationIds) File permissions for datastore and uploads folders/files are 777. Everything else is 775. Please help.
Marc Posted February 17, 2022 Posted February 17, 2022 10 hours ago, Frederick Gams said: %!*&^#^%$&*! SELinux While I understand the sentement there, Im not sure that was the actual solution, so have unmarked that. Please could you state the actual solution and mark that instead? Otherwise people may be searching for that very same issue, and see the solution is indeed to..........
Randy Calvert Posted February 17, 2022 Posted February 17, 2022 It was most likely a permission problem on the folders being 777 or a file ownership issue. https://www.mysysadmintips.com/linux/servers/587-find-if-permission-denied-error-is-caused-by-selinux
Solution Frederick Gams Posted February 22, 2022 Author Solution Posted February 22, 2022 (edited) On 2/17/2022 at 4:25 AM, Marc Stridgen said: While I understand the sentement there, Im not sure that was the actual solution, so have unmarked that. Please could you state the actual solution and mark that instead? Otherwise people may be searching for that very same issue, and see the solution is indeed to.......... Mark, there are two solutions. 1) Configure an SELinux policy to allow apache to write to the document root and subfolders. 2) Disable SELinux. I opted for the latter. Thanks p.s. file permissions should not be 777. I don't want to argue about it, but it is not necessary and poses a security risk. You are giving the public write permissions to a folder on the server. Instead, you should change the ownership of the 'document root' folder to apache:apache (if you use apache) and set file permissions to 775 or even 755. Edited February 22, 2022 by Frederick Gams IveLeft... 1
IveLeft... Posted February 22, 2022 Posted February 22, 2022 25 minutes ago, Frederick Gams said: 2) Disable SELinux. I opted for the latter. Thats by far the better option
Recommended Posts