I have a froxlor installation on an existing server that's causing isses with display of the site through apache. After I installed froxlor on the existing site and migrated the existing apache document root to the first customer guid user and group ownership (chown -R 10000.10000 /web/root ) from the default www-data user and group ownership, the web site displays a 403 forbidden error.
If files are FTP'd up for changes they are owned by the guid group and not the www-data group, which perpetuates the 403 forbidden errors. However, the second customer's files and web root (guid 10001) display just fine via apache.
I'm assuming somehow the first customer did not get associated with the www-data group? How to correct this?
Question
steve_adams
I have a froxlor installation on an existing server that's causing isses with display of the site through apache. After I installed froxlor on the existing site and migrated the existing apache document root to the first customer guid user and group ownership (chown -R 10000.10000 /web/root ) from the default www-data user and group ownership, the web site displays a 403 forbidden error.
If files are FTP'd up for changes they are owned by the guid group and not the www-data group, which perpetuates the 403 forbidden errors. However, the second customer's files and web root (guid 10001) display just fine via apache.
I'm assuming somehow the first customer did not get associated with the www-data group? How to correct this?
Link to comment
Share on other sites
10 answers to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.