HomePage :: InstallationInstructions :: ConfigurationFile :: Troubleshooting

Requirements:

The web server that web-cp's 'frontend' is running on must have write permission on the /home/webcp/tag directory. This web server must also be able to read all files in /home/webcp/web (this is where it serves pages from). If the web server is webcp-httpd then /var/run/webcp/webcp-httpd.pid should be writable by the user it is running as. The web server may need permission to read from /home/webcp/server/data.

The commands listed below are just guidelines. You should run the web server that is running webcp itself as an unprivileged user, on most systems 'nobody' can be used although it helps to keep things structured if you create a user called webcp exclusively for running the web server.

Note that webcp must know what user is running your httpd because otherwise it does not know what pernmissions are required to keep web files readable. (Note i cannot remember what this affects other than config.php). Please please read config.inc.php and the comments in some detail before deploying web-cp so you have some idea what defaults exist and what to bear in mind when setup runs and after setup runs once installation is complete.

Create permissions:

Add a web-cp user (Linux Only)

useradd -u 90 -s /sbin/nologin -d /home/webcp -c "webcp user" webcp -M

Prepare log directory

touch /var/log/webcp
chmod 600 /var/log/webcp
chown webcp:webcp /var/log/webcp

Prepare status directory

mkdir -p /var/run/webcp
chmod 755 /var/run/webcp
chown webcp:webcp /var/run/webcp

Prepare webcp directory

chmod 755 /home/webcp
chown -R root:webcp /home/webcp

Prepare webcp subdirectories

chmod -R 755 /home/webcp/{httpd,suspended,imap,named}
chmod -R 750 /home/webcp/{headers,web,server}
chmod 755 /home/webcp/server
chmod -R 700 /home/webcp/skel
chmod -R 770 /home/webcp/tag
chmod 755 /home/webcp/server/autoreply.php
chmod 777 /home/webcp/autoresponder

Aside - it is possible and maybe a good idea to define a function that checks permissions to some level before certain operations are attempted, this is probably a better solution than wrapping something around the filesystem functions, just instead run a few checks first such as if something is owned by a user and we need to read it that we are trying with the correct user.