Posts by Phinous


    I'm using i-mscp 1.1.14 under debian wheezy
    I'm also using FCGI (I think)

    I need to display all php error on a website.
    I used to edit /var/www/fcgi/ and uncomment E_ALL line before upgrade i-MSCP version
    But after apache2ctl restart I still have blank page.

    What's wrong ?

    I follow the doc to install php 5.2 under PhpSwitcher but I have this error during the .configuration :

    1. checking for MySQL support... yes
    2. checking for specified location of the MySQL UNIX socket... /var/run/mysqld/mysqld.sock
    3. checking for MySQL UNIX socket location... /var/run/mysqld/mysqld.sock
    4. configure: error: Cannot find MySQL header files under yes.
    5. Note that the MySQL client library is not bundled anymore

    Maybe it's because I have installed MariaDB instead of MySQL ?

    Any news about the support for FPM ?
    During the installation of i-MSCP I select FPM instead of FCGI, but maybe it was not a good idea as I need several php version for one customer :huh:


    During installation, I have disabled auto backup because I use a personnal script.
    But one customer want to have his own backup.

    What is the way to activate the autobackup, but only for one customer ?

    * Distribution in use : 7.0 (Wheezy)
    * i-MSCP version in use : 1.1.14 (eagle)
    * Server implementation in use : dovecot, Apache FPM, Mysql

    Sorry :o/


    ls -la /var/www/virtual/
    lrwxrwxrwx 1 vu2005 vu2005 14 oct. 2 21:02 /var/www/virtual/ -> /var/www/munin


    With iscp 1.0.3, I was running Munin 1.x inside a subdomain
    I made a symlink from /var/www/munin to /var/www/virtual/domain/munin/htdocs

    Now, with my new server with i-MSCP 1.1.14, I try to do the same.
    But I have a 403 error :


    Symbolic link not allowed or link target not accessible: /var/www/virtual/

    I read a lot and a lot of google result about this error, and finaly I'm asking myself if there is not a specificty with i-MSCP...

    Is someone here use with success Munin 2.x with i-MSCP ?


    This can stay only a dream because i-MSCP must know at least the relay
    (server which is responsible to send mails for the domain). Nothing is

    OK. I can understand.

    Nevertheless, I remember on my old ispCP, I used a tip like this :


    1/ edit /etc/postfix/ispcp/domains
    2/ comment domain (to have the behavior described here on it)
    3/ cp /etc/postfix/ispcp/domains /etc/ispcp/postfix/working
    4/ cd /etc/postfix/ispcp
    5/ postmap domains

    Until my migration to i-MSCP, I use this tip as roundabout with success.


    What you need is a per sender transport map (with SASL authentication). This is currently not supported by i-MSCP. I'll see if I can implement that ASAP.

    OK thanks, because it's not very confortable for now :o/
    I'll stay connected :)