Writeable custom director - Arch Linux and Nginx

I’m stuck on the install page with the following text

Writeable Custom Directory

The Custom Directory exists but is not writeable. You may have to change permissions on it (chmod 766) or right click on it and uncheck the read only option, depending on your Operating System. Please take the needed steps to make the file writeable.

Writable Cache Sub-Directories

The files or directories listed below are not writeable or are missing and cannot be created. Depending on your Operating System, correcting this may require you to change permissions on the files or parent directory (chmod 755), or to right click on the parent directory and uncheck the ‘read only’ option and apply it to all subfolders.

Please fix the following files or directories before proceeding:

Writable Modules Sub-Directories and Files

Warning: Not Writable

Please fix the following module directories and the files under them before proceeding:

Writable Upload Directory

Warning: Not Writable

I’ve run the chmod / chown commands exactly as they are on the install instructions page. Nginx user is http (master = root, worker = http, confirmed by both the nginx config and running ps aux|grep nginx)

What else could be making the suitecrm think these directories don’t have the right permissions? I know nginx isn’t officially supported but I’ve also read it works with suitecrm well.

Running the latest Arch Linux and latest nginx (and latest php for that matter)

oh and another thing, it doesn’t seem to matter what permissions I give the suitecrm files, the error is the same…

When you say you used the commands exactly as in the documentation, did you change www-data into http? Sorry for the silly question, I just need to confirm this.

If that’s not it, then try looking for other nginx posts here in the Forums.

nginx is not a supported configuration, but I can attest that many people do use it with SuiteCRM successfully. But it does seem to require some extra tweaking.

Yeah I did change the users to reflect my system, so thats not it

I literally just found that php-fpm has some security restrictions on anything in /usr directory - here’s the stackexchange thread https://serverfault.com/questions/996397/failed-to-open-stream-read-only-file-system-when-trying-to-create-file-outsid/997496

seems to be working fine now

1 Like