Thierry Gronchi Posted October 26, 2018 Share Posted October 26, 2018 Hello, I used Froxlor for Years on Debian 7 without any problem. I've just installed Froxlor on a new v-server Debian 8.11 image. Every things are well installed, but Froxlor can't write the folder of a new customer in /var/customers/webs/ folder. I first add a new customer and add a new domain for this customer. On my previous installation, the folder was created automatically at this moment. No new file in /etc/apache2/sites-enabled/ either, so no v-hosting. No error reporting. I'm not experimented in Linux OS, but it seems Froxlor have authorisation problems. I've discovered that my v-server is chrooted by the hosting and don't know if it's a problem. Can someone tell me if I have to adjust some configurations to solve the situation ? Thanks. Thierry Gronchi Link to comment Share on other sites More sharing options...
d00p Posted October 26, 2018 Share Posted October 26, 2018 Sounds like the cronjob did not run, try php /var/www/froxlor/scripts/froxlor_master_cronjob.php --force --debug Link to comment Share on other sites More sharing options...
Thierry Gronchi Posted October 26, 2018 Author Share Posted October 26, 2018 php /var/www/froxlor/scripts/froxlor_master_cronjob.php --force - -debug [information] cron_tasks: Searching for tasks to do [information] cron_tasks: Task2 started - create new home [notice] Running: mkdir -p '/var/customers/webs/Thierry/webalizer' [notice] Running: mkdir -p '/var/customers/mail/Thierry/' [notice] Running: cp -a /var/www/froxlor/templates/misc/standardcustomer/* '/var/customers/webs/Th ierry/' [notice] Running: chown -R 10000:10000 '/var/customers/webs/Thierry/' [notice] Running: chown -R 2000:2000 '/var/customers/mail/Thierry/' [information] apache::createIpPort: creating ip/port settings for 141.101.32.184:80 [notice] 141.101.32.184:80 :: namevirtualhost-statement no longer needed for apache-2.4 [debug] 141.101.32.184:80 :: inserted vhostcontainer [information] apache::writeConfigs: rebuilding /etc/apache2/sites-enabled/ [information] apache::writeConfigs: rebuilding /etc/apache2/htpasswd/ [information] apache::writeConfigs: rebuilding /etc/apache2/sites-enabled/ [information] apache::reload: reloading apache [information] Task4 started - Rebuilding froxlor_bind.conf [information] Cleaning dns zone files from /etc/bind/domains/ [notice] mkdir '/etc/bind/domains/' [information] No domains found for nameserver-config, skipping... [notice] Checking system's last guid Link to comment Share on other sites More sharing options...
Thierry Gronchi Posted October 26, 2018 Author Share Posted October 26, 2018 Hello, thanks for response. I sended the result before... sorry. Link to comment Share on other sites More sharing options...
d00p Posted October 26, 2018 Share Posted October 26, 2018 so, see, everythings fine. Please verify that /etc/cron.d/froxlor exists and nopaste its content so I can see whether everything is fine in there Link to comment Share on other sites More sharing options...
Thierry Gronchi Posted October 26, 2018 Author Share Posted October 26, 2018 Effectively, it seems to work now. I've change a setting in /etc/passwd : www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin -> www-data:x:33:33:www-data:/var/www:/bin/sh Is it possible that was the problem ? Link to comment Share on other sites More sharing options...
d00p Posted October 26, 2018 Share Posted October 26, 2018 eh, no, you should not edit /etc/passwd manually nor should it be required Link to comment Share on other sites More sharing options...
Thierry Gronchi Posted October 26, 2018 Author Share Posted October 26, 2018 I did it by vipw and vipw -s (for the shadow) I have a backup of passwd in case of mistake. But I cannot see what else made the cron job works now and not before. I tryed during four days without success and nows all works fine. Customers folders, v-hosting, ftp acces are ok. Link to comment Share on other sites More sharing options...
d00p Posted October 26, 2018 Share Posted October 26, 2018 www-data has NOTHING to do with the cronjob. Did you set it up correctly like shown in the configuration template steps? You should've created the file /etc/cron.d/froxlor yourself and put shown content into it. Link to comment Share on other sites More sharing options...
Thierry Gronchi Posted October 26, 2018 Author Share Posted October 26, 2018 I have copy and pate in SSH from Froxlor configurations templates step by step, and verified all at least 10 times. /etc/cron.d/froxlor exists since 4 days. at the end of first configuration in web browser, it was demanded in orange to manualy copy userdata.inc.php from /tmp to /froxlor/lib, what I did. Link to comment Share on other sites More sharing options...
d00p Posted October 27, 2018 Share Posted October 27, 2018 /froxlor/lib ? I hope you mean /var/www/froxlor/lib... Link to comment Share on other sites More sharing options...
Question
Thierry Gronchi
Hello,
I used Froxlor for Years on Debian 7 without any problem.
I've just installed Froxlor on a new v-server Debian 8.11 image.
Every things are well installed, but Froxlor can't write the folder of a new customer in /var/customers/webs/ folder.
I first add a new customer and add a new domain for this customer. On my previous installation, the folder was created automatically at this moment.
No new file in /etc/apache2/sites-enabled/ either, so no v-hosting.
No error reporting.
I'm not experimented in Linux OS, but it seems Froxlor have authorisation problems.
I've discovered that my v-server is chrooted by the hosting and don't know if it's a problem.
Can someone tell me if I have to adjust some configurations to solve the situation ?
Thanks.
Thierry Gronchi
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.