Good evening,
The upgrade path from 1.1.x version is currently broken. We will fix the problem this week.
Posts by Nuxwin
-
-
Please upgrade to latest plugin version ! ! !
Thread closed.
-
-
Thank you for your answer. We would like to update to MariaDB 10.1 in the first place and we would like to finish the distrubtion update to Debian Stretch later on. So if I understand you correct, it is possible without i-mscp related problems to update from MySQL 5.6 to MariaDB 10.1 with Debian Jessie, if we force the autoinstaller to show all vendors when we override the imscp.conf, right?
I wouldn't take that road but of course, you can always trick the i-MSCP installer by manually setting the SQL_SERVER parameter in the /etc/imscp/imscp.conf file to mariadb_10.1, then rerun the i-MSCP autoinstaller (from version 1.5.3) as follows: perl imscp-autoinstall -d
If you do so, make sure first that there is not a /etc/imscp/imscpOld.conf file resulting of a previous failure. If that file exists, your must remove it prior running the installer.
Note that in the above scenario, MariaDB 10.1 will be installed from the MariaDB repository, not from the Debian repository. That should not pose any problem but the backup is still needed for safety.
-
Hello community,
just a few days ago we updated from mysql 5.5 to 5.6 on Debian Jessie with I-MSCP 1.5.3, thanks to Nuxwin. Today I have a few questions regarding the options to update to MariaDB, since with Debian Stretch, MySQL will be replaced with MariaDB.
We alread have plans for the full distribution update to Debian Stretch, but until this can work, we have to check some of our software. I searched for a I-MSCP Autoinstaller Update to MariaDB and found the following: Von MySQL 5.5 zu 5.6 oder MariaDB 10In latest i-MSCP versions, the installer doesn't allow automatic switch from one SQL vendor to another. The reason behind this is that switching to other vendor is not always an all-in-one task that can be achieved without any administrator intervention. That being said, i-MSCP still provide MySQL for Debian Stretch (version 5.6 and 5.7) through MySQL community repository and so, it's shouldn't be so difficult to upgrade your Debian system and once done, rerun the i-MSCP installer.
If you want really update to MariaDB 10.1 (SQL vendor/version provided by Debian Team), what I would recommend, you must do the job manually, as part of the Distribution upgrade. In order, that means:
- Removing the APT preferences file provided by i-MSCP and which is located at /etc/apt/preferences.d/imscp
- Removing the MySQL 5.6 repository from the APT /etc/apt/sources.list file
- Updating all repositories URI for Debian Stretch in the APT /etc/apt/sources.list file
- Running the apt-update and apt-get dist-upgrade commands
Updating from MySQL 5.6 to MariaDB 10.1 shouldn't pose any problem but as always, you should really considere to backup your data first (/var/lib/mysql directory), including making a real dump of your databases (even the mysql database). Note that there is no need to update to MariaDB 10.0 first.
In any case, after the system upgrade (Jessie to Stretch), you must not forget to rerun the i-MSCP installer as follows: perl imscp-autoinstall -dr sql and when asked, select the MariaDB 10.1 SQL vendor/version.
Does my answer is clear enough for you?
-
-
Dear customers, community,
A new version of the LetsEncrypt plugin has just been released.
CHANGELOG
- Fixed: Cron job for SSL certificates renewal abort due to missing bind variable (SQL statement)
- Fixed: Required distribution packages are not installed while plugin installation (regression fix)
- Review: Default policy for SSL certificate renewal (automation) now set to 21 days to fit with Let's Encrypt expiry notices
- Updated: Certbot from version 0.24.0 to version 0.26.1
The plugin documentation is available at https://wiki.i-mscp.net/doku.php?id=plugins:letsencrypt
Once registered on our forums, you can purchase this plugin at https://i-mscp.net/wcf/paid-subscription-list/ (one time payment).
Thank you for purchasing our plugins.
-
Can you give us access to the server and control panel (admin access) and give us the domain name for which you encounter the problem?
-
Quick fix
Once done, trigger a renewal of your SSL certificate manually through UI.
-
Bug confirmed. Will be fixed in next version:
Display MoreSQL- root@ascii:/var/www/imscp/gui/plugins/LetsEncrypt/frontend/client# mysql
- Welcome to the MariaDB monitor. Commands end with ; or \g.
- Your MariaDB connection id is 135
- Server version: 10.3.8-MariaDB-1:10.3.8+maria~stretch mariadb.org binary distribution
- Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
- Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
- MariaDB [(none)]> use imscp;
- Reading table information for completion of table and column names
- You can turn off this feature to get a quicker startup with -A
- Database changed
- MariaDB [imscp]> select * from letsencrypt \G;
- *************************** 1. row ***************************
- letsencrypt_id: 1
- admin_id: 3
- domain_id: 1
- domain_name: bbox.nuxwin.com
- domain_type: dmn
- letsencrypt_sans: bbox.nuxwin.com
- www.bbox.nuxwin.com
- letsencrypt_status: ok
- letsencrypt_previous_status: NULL
- letsencrypt_status_date: 1531901279
- letsencrypt_expires: 0
- 1 row in set (0.001 sec)
The letsencrypt_expires column is set to 0 while it is expected to be set with expire date...
