Posts by TheRiddler1982

    Hi Nuxwin,


    I just updated from 1.2.16 to 1.2.17 and I have noticed that I cannot connect to my domain https://ziin.de any longer. In the backend, everything looks perfect. Once I had a look at


    Code
    1. /etc/apache2/sites-available


    I have noted that the ssl config file for ziin.de is missing:


    Code
    1. -rw-r--r-- 1 root root 1,4K Feb 1 2015 000-default.conf
    2. -rw-r--r-- 1 root root 1,3K Mär 13 22:22 00_nameserver.conf
    3. -rw-r--r-- 1 root root 705 Mär 13 22:21 01_awstats.conf
    4. -rw-r--r-- 1 root root 6,3K Feb 1 2015 default-ssl.conf
    5. -rw-r--r-- 1 root root 1,7K Mär 13 22:22 foto-schwabach.de.conf
    6. -rw-r--r-- 1 root root 1,8K Mär 13 22:22 hochzeit-schwabach.de.conf
    7. -rw-r--r-- 1 root root 1,8K Mär 13 22:22 schwabach-fotografie.de.conf
    8. -rw-r--r-- 1 root root 1,5K Mär 13 22:39 ziin.de.conf


    I have restored it from my backup and restarted the Apache2 service but the file is not taken into account.


    Next, I have updated the certificates in the backend, but it still does not work. My restored file has been deleted by the config.


    Do you know what is causing that error?


    In case you want to have a direct look at the server: your public key is installed at menkisyscloudsrv29.menkisys.de.



    Thanks,
    Sven

    Hi Nuxwin,


    we had a discussion back in January this year where you told me that the new version of phpSwitcher supports php-fpm which gives better performances:


    https://i-mscp.net/index.php/T…7/?postID=39722#post39722


    By analyzing an error in PHP I have noticed the following:


    Code
    1. [Fri Mar 04 18:59:28.001099 2016] [proxy_fcgi:error] [pid 3962:tid 139674936923904] [client 66.249.93.229:56413] AH01071: Got error 'PHP message

    Does this mean that I am using the fcgi mode and not the php-fpm? If so, how do I change that?



    Thanks,
    Sven

    Hi,


    just have a question: can you explain why is normal to lose the settings of rainloop after each update? I have the same problem. After each i-mscp update, I have to update my theme, gpg keys, language settings, etc. Is there a way to keep them?



    Thanks,
    Sven

    Hi Nuxwin,


    since the update to 1.2.14 I have noticed that the I-MSCP installer adds the following lines



    Code
    1. deb http://repo.mysql.com/apt/debian/ jessie mysql-5.7deb-src http://repo.mysql.com/apt/debian/ jessie mysql-5.7

    to the main sources.list file:


    Code
    1. /etc/apt/sources.list

    As I have already added them to my custom list file before to




    Code
    1. /etc/apt/sources.list.d/



    directory manually before the update, I ran into apt-get update errors. I have removed that from the main source file after the 1.2.14 update and just thought that I forgot about removing it. But after the 1.2.15 update, it reappeared. As I have not done anything there, I would assume Sherlock Holmes' logic that the remaining thing must be the cause as unrealistic it might be :-)


    I would suggest do implement a check, if the added sources are already present in the user adjusted directory.


    What do you think?


    Thanks,
    Sven

    Hi Nuxwin,


    I have just updated to the latest version of PHPSwitcher plugin, i.e. I have downloaded the latest version and uploaded it through the backend. It told me that it updated it successfully. After that, I rebuilt the PHP7.0 module using


    perl /var/www/imscp/gui/plugins/PhpSwitcher/PhpCompiler/php_compiler.pl 7.0


    Next, I have regenerated the PHPinfo in the backend and it showed me 7.0.3. After that, I have reselected the PHP7.0 version for each of my domains.


    So, everything looks fine but after loading my startpage https://ziin.de it just renders blank (no source code given). When I switch back to PHP5.6.17 (which comes with my system), the sites loads fine again.


    Did I miss something?


    I have checked the apache2 logs and this is the result:


    • [Sun Feb 28 17:59:31 2016] [alert] i-MSCP Vlogger: unable to connect to MySQL server: Can't connect to MySQL server on '127.0.0.1' (111)
    • [Sun Feb 28 17:59:31 2016] [alert] i-MSCP Vlogger: Tracker feature turned off
    • [Sun Feb 28 16:59:31 2016] [notice] i-MSCP Vlogger: started CustomLog Handler -- resuming normal operations

    Do you know what the error means? I can connect manually on the console as root to mysql.


    Can you help me? If needed, your public key is still available on my server menkisyscloudsrv29.menkisys.de/.


    Thanks,
    Sven