Next time please, do a search on our forums before posting.
See sury.org - public key is not available
Thread closed.
Next time please, do a search on our forums before posting.
See sury.org - public key is not available
Thread closed.
Display MoreGood evening @Nuxwin,
thanks for fast reply - i can wait, no problem - i look only for a way in the next time (1-3 months round about) to get it working together with i-mscp - perfect would be php 7.3
Do you have any schedule for next php-switcher version release as well for the i-mscp 1.5.3, where also php 7.2 & 7.3 will be supported ?
One last question - do you recommend to use already 7.3 as main php version in i-mscp or better only with php-switcher?
thanks in advance
The next PhpSwitcher version, and the next i-MSCP maintenance release for the 1.5.3 version will be both provided before end of april.
When using the PhpSwitcher plugin, I would recommend PHP 7.3 as default PHP version for the customers. But this mostly depend on your current setup and on the version your customers are relying on.
Note that in the next maintenance release, The i-MSCP control panel, including addons such as RainLoop, Roundcube, PhpMyAdmin... will be run through PHP 7.3, regardless of the selected PHP version for the customers. So, if you select PHP 7.2 as PHP version for the customers, the installer will install both PHP 7.2 and PHP 7.3 versions. However, only the selected PHP version will be made available for the customers. Without the PhpSwitcher plugin, there is no way to provide alternate PHP versions to customers.
Another thing to note is that in the next PhpSwitcher plugin version, most of PHP versions will be provided through the Ondrey Sury repository (transitional), and in a near future, they will be provided by our own repository.
In the hope that the situation is clarified.
do you have news for php 7.2 & php 7.3 update/support in this plugin ?
Good evening,
PHP 7.2 and 7.3 versions will be provided in the next PhpSwitcher plugin version. They will be also supported in the next i-MSCP 1.5.3 maintenance release.
If you cannot wait, you can always update your i-MSCP installation to the latest snapshot of the i-MSCP 1.5.3 maintenance branch in which support for these versions has been already added: https://github.com/i-MSCP/imsc…/1.5.3-maintenance.tar.gz
However, you must keep in mind that we don't provide support for the development version of i-MSCP. Of course, if you report a bug, we will fix it.
Good morning,
Please, show us the result of the following command on your system: grep -nr 'ITEM_DISABLED_STATUS' /var/www/imscp/gui/
Good evening,
Result of ifconfig | grep -C 1 127 ?
Good evening,
Mar 29 16:06:18 jupiter spamc[18908]: connect to spamd on 127.0.0.1 failed, retrying (#1 of 3): Connection refused
The problem seem to be that the SpamAssassin service is not reachable.
Please, what is the status of the SpamAssassin service: service spamassassin status
Please, what is the status of the SpamAssassin MILTER service: service spamass-milter status
Those both services should be running.
Merci A votre bon cœur
Heu... Comment dire... Désolé, on fait pas dans la charité chrétienne ici
Concernant votre problème, et si vous êtes vraiment sous Debian Stretch, le fichier de configuration /etc/network/interfaces devrait exister. Voir man interfaces. Ce faisant, certain fournisseur de services, comme OVH, utilisent d'autre méthodes pour la configuration du réseau. Concernant OVH, une petite recherche via votre ami google vous aurez évité de poster inutilement: https://www.virtualmin.com/node/54433
Pour résumer, vous devez simplement créer le fichier manuellement: touch /etc/network/interfaces, et une fois cela fait, vous devez relancer le script d'installation d'i-MSCP.
i-MSCP n'implémente pas de fournisseur pour systemd-network actuellement. Vous pouvez toujours créer un ticket: https://youtrack.i-mscp.net/issues
Good evening,
configure: error: Unable to detect ICU prefix or no failed. Please verify ICU install prefix and make sure icu-config works.
make: *** [configure-7.0-stamp] Error 1
Good morning,
You need to connect as admin and in the letsenrypt interface, you need to enable LetsEncrypt for the services.
Display MoreHello,
I'm triing to install a fresh new Debian 9.8 with imscp 1.5.3-2018120800 with PHP 7.1 by default, and then installed phpswitcher. And when trying to add support to php 5.6 ("perl php_compiler.pl --auto-setup 5.6"), it says that the Bison 3.0 is not supported with php 5.6, so there is no way to add php 5.6. (https://bugs.php.net/bug.php?id=69055)
I have others servers with imscp, and the only thing that it's different is that we added PHP 5.6 by default on imscp (and not 7.1), and I think that then the bison version installed is 2.x.
So I checked the documentation on php and says that php 7 supports bison > 2.4 (https://secure.php.net/manual/en/install.unix.php)
bison:
- PHP 5.6: >= 2.4, < 3.0
- PHP 7.0 - 7.3: 2.4 or later (including Bison 3.x)
- PHP 7.4: > 3.0
So I think that maybe the version installed by default can be the bison 2.x in order to have compatibility with php 5.6 ¿?
The only solution is to add php 5.6 by default on imscp Nuxwin ?
Thanks!
A.
Good morning,
The bison message can be ignored. You shouldn't assume anything without knowning how things are working. When you report a problem on our forums, you need provide us with full information. Next time, just provide us with your distribution /codename and PhpSwitcher PHP compiler output.
You should also search on our forums before posting.
Please read the following thread, apply the fixes and retry: