Posts by xavh90



    I tried to upgrade iMSCP from 1.3.16 to 1.4.0 on debian 8.

    An error occured when the installer tried to restart apache2 service

    1. [ERROR] Servers::httpd::apache_php_fpm::start: Could not start the `apache2' service: iMSCP::Provider::Service::Sysvinit::_exec: Job for apache2.service failed. See 'systemctl status apache2.service' and 'journalctl -xn' for details. at /usr/local/src/imscp-1.4.0/engine/PerlLib/iMSCP/ line 185.[ERROR] autoinstaller::Functions::install: An error occurred while performing installation steps

    systemctl status apache2.service results :

    1. Mar 27 16:09:18 ds01 apache2[11882]: Starting web server: apache2 failed!
    2. Mar 27 16:09:18 ds01 apache2[11882]: The apache2 configtest failed. ... (warning).
    3. Mar 27 16:09:18 ds01 apache2[11882]: Output of config test was:
    4. Mar 27 16:09:18 ds01 apache2[11882]: AH00526: Syntax error on line 14 of /etc/apache2/sites-enabled/xxx.be_ssl.conf:
    5. Mar 27 16:09:18 ds01 apache2[11882]: Invalid command 'AssignUserID', perhaps misspelled or defined by a module not included in the server configuration
    6. Mar 27 16:09:18 ds01 apache2[11882]: Action 'configtest' failed.
    7. Mar 27 16:09:18 ds01 apache2[11882]: The Apache error log may have more information.
    8. Mar 27 16:09:18 ds01 systemd[1]: apache2.service: control process exited, code=exited status=1
    9. Mar 27 16:09:18 ds01 systemd[1]: Failed to start LSB: Apache2 web server.
    10. Mar 27 16:09:18 ds01 systemd[1]: Unit apache2.service entered failed state.

    Can you help me please ?


    J'ai un certificat sur mon serveur pour l'accès au panel, l'envoi des mails, le ftp etc.

    J'ai besoin là de renouveler ce certificat, est-ce que je peux le faire en téléchargeant certbot-auto ? (sans utiliser celui du plugin)

    Est-ce que ça ne risque pas d'interférer avec le plugin let's encrypt ?

    Je veux juste m'en assurer avant de faire les manipulations ...

    est-ce que, si le certbot que je télécharge renouvelle des certificats qui ont été générés par le plugins, ça ne posera pas de problème ?


    So, Nuxwin resolved the problem of php compilation on my server but

    I registered the PHP7.0 version in PhpSwitcher plugin

    When I switch to PHP7.0 on a domain or subdomain, I have a 503 error service unavailable

    The phpinfo in PhpSwitcher is good with php7.0.8 and the status is "OK"

    Edit :

    I have this error in the /var/log/phpswitcher/psw7.0-fpm.log file

    [14-Jul-2016 12:29:16] ERROR: unable to bind listening socket for address '/var/run/phpswitcher/': No such file or directory (2)


    I've tried to create a LetsEncrypt certificate for a subdomain with the LetsEncrypt plugin.

    I use an external DNS server, not the DNS server implemented in i-MSCP and I just configure the DNS record for that subdomain like, but not [www.]

    In this case, I have this error with the let's encrypt plugin in the status

    1. N/A 2016-07-14 09:32:46,722:INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1):

    The LetsEncrypt plugin try to create a certificate for the and [www.] but can't verify the [www.]

    I just commented the line 215 (and the comma at line 214) of /var/www/imscp/gui/plugins/LetsEncrypt/backend/ file, deleted and recreate the subdomain in i-MSCP, create a new certificate and it's worked fine.

    Maybe it's not a good solution, the good solution is to create the [www.] in the DNS records because if you comment that line and try to create a certificate for the domain, I think it will not create the certificate for the domain [www.] ...

    It will be great if the plugin can catch this error and don't block the subdomain certificate creation if let's encrypt can't verify the subdomain and it will be great if the certificate creation for subdomain create a certificate only for and not [www.]

    (Sorry for the [www.], the forum catch an url and create a link automatically and delete the www.)

    Edit : Aaaaannnd, I just found other thread about this problem, sorry