Posts by Nuxwin

  • Problem at installing i-mscp

    Quote from TheCry

    I'd the same problem with some server which are not upgraded to Debian 9 atm.

    I'm using now this source.list

    Code
    1. deb http://deb.debian.org/debian/ oldstable main contrib non-free
    2. deb-src http://deb.debian.org/debian/ oldstable main contrib non-free
    5. deb http://security.debian.org/ jessie/updates main
    6. deb-src http://security.debian.org/ jessie/updates main
    9. deb http://archive.debian.org/debian jessie-backports main
    10. deb-src http://archive.debian.org/debian jessie-backports main

    Almost same as my solution, isnt't it? Excepted the fact that you make use of backports repositories. I wonder why they removed that jessie-updates "previously known as volatile" repository...

  • Max Execution Time of PHP in PHP Script

    reitbrud


    Assuming* that you're using FPM with the per_site PHP configuration level, and without considering the PhpSwitcher plugin, you need to modify the default FPM pool configuration template file if you want be able to change the max_execution_time INI directive at runtime, using the ini_set() PHP function. Why? Because i-MSCP set the value by default through php_admin_value rather than php_value, meaning that you cannot change the value at runtime. Of course, this is the expected behavior for most hosting providers since they want not let's their customers eat all available resources. That's also why the previous advice from Dylan was to use the PHP Editor to set the value for your customer.


    For instance, by default, you can have such a FPM pool configuration file:


    As you can see here, the max_execution_time INI directive is set with php_admin_value. If you want be able to change the value at runtime, using the ini_set() PHP function, you need set the value with php_value in the FPM pool configuration file instead. Best in your case would be to modifiy the FPM pool configuration template file which is located at: /etc/imscp/php/fpm/pool.conf. Then once done, you should trigger an i-MSCP reconfiguration. Another solution is to make use of the following listener file: https://github.com/i-MSCP/imsc…p_confoptions_override.pl but you would have to modify that listener to set the value with php_value rather than php_admin_value.


    See also https://www.php.net/manual/en/configuration.changes.php for detailed explanation regarding usage of php_admin_value rather than php_value, and all other equivalent.


    BTW: When other people give you an answer, try to stay calm. They only want help you on their free time.


    * Next time please, provide all relevant information, as asked by FloRet88. Else, we can only make assumption...


    Thanks you.

  • Problem at installing i-mscp

    Good evening,


    the jessie-update repository has been removed recently. You need first remove it from your /etc/apt/sources.list file. Once done, run apt-get updates and retry. Basically put, you should end with something like:



    As you can see, I've commented the related repositories.


    BTW: Best would be to start with Debian Stretch.

  • Wann ist mit der neuen imscp Version zu rechnen?

    Bulli  flames  FloRet88


    Good evening,


    The PhpSwitcher plugin is only one part of my work. It is one plugin that is hard to maintain and deliver. Adding support for a new Php version require a lot of work (patching) due to debian specific layout. If you think I'm just sleeping, you're wrong. I'm working every days hard on i-MSCP.


    The support for PHP 7.2 and 7.3 has been already added to i-MSCP core, including new i-MSCP Package for PhpMyAdmin which rely on latest PhpMyAdmin composer package. So, awaiting next i-MSCP version, you can always give a try to the 1.5.3-maintenance branch. You'll at least be able to have PHP 7.2 or PHP 7.3 as default PHP version.


    For the next maintenance release, I want to provide updated version of all addons, that is: Roundcube, RainLoop, PhpMyAdmin, MonstaFTP... That explain why I'm so long to provide a new version. One another reason is: I want drop support for Ubuntu Trusty which will be EOL by April.


    Please, don't be so rude. Those people that are following me known how I'm working hard. I cannot be on every fronts at the same time.


    Bulli


    If you follow me on facebook or twitter, you'll have more up-to-date information about what I'm working on day to day.


    Thank you for your understanding.


    flames FloRet88


    Thank you both for your support.


    References:

  • PhpSwitcher error install MAKE

    Quote from root666

    What do you mean exactly with this? Do you mean avoid at live systems (this is my test-intranet-server without access from the Internet) or do you mean avoid compiling with the updated libssl-dev and openssl?

    You should avoid to compile those PHP versions, that is, make them available for your customers. Those PHP versions don't support FPM and are really too old. Support for them will be removed in next PhpSwitcher plugin version, according poll result we made some months ago. Of course you do as you want.

  • PhpSwitcher error install MAKE

    Quote from root666

    I dont know if i can use this solution from this Thread --> Error Compiling PHP Versions for PHP Switcher


    Ubuntu based at Debian but i dont do experiments in apt what can eventually corrupt my whole system.

    Good evening,


    Please, edit the /etc/apt/preferences.d/imscp APT preferences file, then remove the first stanza (3 lines) which describe a pinning on ssl packages, then run apt-get update && apt-get dist-upgrade. Once done, retry. Note that you should avoid PHP 4.4 and 5.2.