Search results

In the end, I managed to find the issue. The Linux ACL (access control list) settings were too restrictive. After running a setfacl command recursively on the wp-content/uploads directory, the issue appears to be sorted.

Yes. I would like to set the umask to 22 but don't appear to be able to. I have tried this via both the cyberpanel and litespeed dashboards via the PHP settings and phpini override respectively, but to no avail. Again, as mentioned previously still not sure that this is the root cause of the...

I didn't think that a caching plugin was causing the issue. It is almost certainly a setting with either litespeed server or cyber panel. Hence posting here. The umask seems to be set to 18 when I check echo umask, though this also appears to be the case for all the wordpress sites I've...

Thanks, but this is not the issue. All files and folders have the correct owner, group and permissions. If this weren't the case, the plugins wouldn't be able to write files in the first place. The plugins can and do write the files, the issue is that for some reason these plugin generated...

Thanks for your reply Eric. Unfortunately I already tried that to no avail. I can upload new plugins and manually create files and folders without issue. It is when the plugins themselves create files automatically that there is an issue.

I recently migrated numerous WordPress sites from a shared hosting to a VPS with AlmaLinux with CyberPanel and Litespeed Server. Most are working fine, but one has a significant issue where any files generated by plugins get created with 660/-rw-r----- permissions, so return a 403 when accessed...