Invision Community 4: SEO, prepare for v5 and dormant account notifications Matt November 11, 2024Nov 11
Posted February 16, 20223 yr 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.
February 17, 20223 yr Community Expert 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..........
February 17, 20223 yr 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
February 22, 20223 yr Author Solution 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, 20223 yr by Frederick Gams
February 22, 20223 yr 25 minutes ago, Frederick Gams said: 2) Disable SELinux. I opted for the latter. Thats by far the better option