Posts by Nuxwin

Quote from T0mcat

Hello everyone,

I just searched the forum but haven't found an answer. As php5.6 is becoming more and more outdated, I wanted to upgrade it to version 7.1.

During the first setup, the installer asked me which version. Unfortunately, I chose 5.6. Now when rerunning the setup, I don't get the option anymore to install 7.1. I don't want to spoil my actual environnement, but I haven't found a HowTo to safely upgrade. So any help is appreciated.

Is it a good idea to install 7.1 for everyone or should I stick with phpswitcher?

You need rerun the distribution installer with the --reconfigure option and php item:

As long as you provide older PHP versions (5.6 , 7.0) to your clients through the PhpSwitcher plugin, that should be OK. Regarding PHP versions that are not longer supported by upstream PHP team (5.3 , 5.4, 5.5), the choice is up to you.

101host

Should I really update the patches for self-compiled versions or can you live with the following solution: PhpSwitcher plugin - Howto install PHP versions from Ondřej Surý repository

Basicallly put, making use of PHP versions as provided by Ondry Sury make you able to beneficiate of latest versions without waiting for newest PhpSwitcher plugin version. This make you also able to install PHP extension using APT, enabling/disabling them using distribution PHP tools such as phpenmod/phpdismod.

Right now, you cannot use the PHP versions from Ondřej Surý repository with the latest available PhpSwitcher version (4.0.3) as the version matching pattern is too restrictive but there will be a new version (4.0.4) fixing that issue that will be released either this evening or tomorrow. If this solution is fine for you, this could save me a bit time even if in near future, I'll update the pacthes for self-compiled versions.

So?

101host

I'll try to refresh the patches for the already supported versions this week.

Quote from rgabor73

No, that will not fix the issue... You should stop to do things without thinking...

If you do not want get such answers from me, stop to make assumptions and running commands without further thinking. Also, read the documentation. Regarding the git issue, the message was clear enough. I'm not here to teach the linux "administrators". You should down your ego a bit because with me, you'll be well served

There is something called logs Google is your friend

Quote from rgabor73

I have an error popup as well when I log into the dashboard:

unable to get update info from github

Looks like all working, but the plugin cannot be activated, uninstalled or anything

I have already run the following, but issue remain.

Code

1. perl imscp-autoinstall -d

I think I will switch back to Currier, then remove all dovecot I installed manually as that might cause these issues. Then I run the installer with reconfig again to see if that fix it or not

Display More

No, that will not fix the issue... You should stop to do things without thinking...

Quote from rgabor73

- Is the option for managesieve_plugin is set by default to no because is only compatible with dovecot?

- if I re configure I-MSCP and select DOVECOT as mail server, are the current inboxes will keep their current emails, etc.. ?

Regarding your first question

Yes, the option is set to no by default because sieve require dovecot. From the plugin README file:

Quote

The following packages are required only if you want install the managesieve plugin for the Roundcube Webmail.

* dovecot-sieve

* dovecot-managesieved

You can install these packages by running the following commands:

```

# apt-get update

# apt-get install --no-install-recommends dovecot-sieve dovecot-managesieved

```

Prior executing the command above, be sure that you're using the i-MSCP Dovecot server implementation.

Display More

Regarding your second question

You can switch to dovecot by running the installer (from the i-MSCP archive - same version) with the --reconfigure po option. Then, when asked, you need select dovecot. The current mailboxes will be migrated to dovecot without lose and Courier will be purged.

Quote from rgabor73

Thank you. I should read the manual, right ?

Anyhow, I have done that, and when I update the plugins, there is an error:

- The `dovecot-sieve` package is not installed on your system

I guess because I am not using dovecot ?

If I remember well, during I_MSCP install, there was a question about emails, and I have not selected dovecot as mail server

I tried to install dovecot manually, then the dovecot-sieve package as well, however when I reload the plugin, it does display the same error.

Display More

Installing dovecot manually is an error as i-MSCP is not aware of that... You must now rerun the i-MSCP installer with the --reconfigure po option.

Good morning,

The error isn't clear enough? Look like there is a DNS problem (no DNS A record for mail.xxx.xxx). This can be either due to temporary error or you have done something wrong with your DNS configuration. Since you don't provide us with real domain name, we cannot check resolving.

Good evening,

Suhosin features were merged into PHP core so, you can safetely ignore the warning. The php-suhosin package has been removed from Debian repository long time ago. Furthermore, it is neither provided by the Ondřej Surý PHP repositories.

See also:

• https://lists.debian.org/debian-user/2013/08/msg00062.html
• https://packages.qa.debian.org/p/php-suhosin.html
• https://packages.qa.debian.org…ews/20161202T134730Z.html

Next time please, do a search before posting