Please, one thread per problem.
Remove the /etc/apt/preferences.d/imscp file and then, retry the upgrade.
Please, one thread per problem.
Remove the /etc/apt/preferences.d/imscp file and then, retry the upgrade.
The first (Dom-Alias to new account) is more important - but also the second one can be interesting...
Otherwise there is the manual way...
Maybe it's too hard to move also the databases... they are not connected to a certain subdomain/alias or whatever. And the db prefix changes when moving to another (a news) client account.... this is to complex to have it done automatically.
You're totally right. Database are connected to the main domain aggregate and can have numerical suffix or prefix so yes, for the proposed features above, that's almost impossible. Somehow, this show us that current implementation is not really good. One thing we could do via UI is to ask the user which database he want to move, but if there is a sufixe or prefix, this also mean rename the database which is not always an easy task, depending on many factors such as the database engine type, the database size...
thank you for reply!
as stated above this is a migration from a ispcp installation many years ago, the database is still named ispcp ... maybe something has been hardcodedfor the variable of IMSCP_DBNAME in latest build ...
I have tested in a Vbox because this is our company main server but everything with the same setup, confs and packages.
Are you serious? Please try again and don't forget to replace <IMSCP_DBNAME> by your i-MSCP database name...
That not the same error as shown in your first post... That error look strange too me.
Please show me the DATABASE_NAME parameter value of your /etc/imscp/imscp.conf file.
also run as root user:
where <IMSCP_DBNAME> must be your i-MSCP db name. The, show me the result..
Good evening,
Having dedicated included file for both http and https could do the job but this would break older sites which repose on single included file. So, I"ll not implement that in core. However, you can always override default include statement using a listener file.
Dear community,
The i-MSCP team wishes you and your family the best for the coming year.
Happy new year 2019
Please, don't look at incubator. You need only look at the plugin store.
One Question, i would need the PHP-Switcher.
Should i use it or should i wait for new I-MSCP Update.
If i Use PHP Switcher can i install new coming I-MSCP Update (1.6 or 2.0) which i can convert the PHP-Switcher Versions to integrated Versions?
Thanks
i-MSCP only provide one PHP version at time. The PhpSwitcher plugin allows your customer to switch between several PHP versions on a per site basis. The PhpSwitcher plugin will be provided for next i-MSCP versions as well.
Ok so please remove the /etc/apt/preferences.d/imscp file and execute:
then, retry.
but please, be sure to grab latest 1.5.3 build: https://github.com/i-MSCP/imsc…ases/tag/1.5.3-2018120800
Normally, the imscp APT preferences file is rewritten and there shouldn't longer have such pinning for openssl development library... Can you check that you do not have any listener overriding default distribution packages file? ls -la /etc/imscp/listeners.d ???
Thanks.
Hello YES but this is the standard Setting after UPGRADE to I-MSCP 1.5.3 and makes also on my Software Problems!
Pls check if I-MSCP code is working correct if everybody gets this Settings after Upgrade to 1.5.3.
Thanks.
Yes, in fact, sql_mode is not longer set in config file.. It is set for i-MSCP only at runtime. If you need back to old behavior just do the following:
Create the /etc/mysql/conf.d/sql_mode.cnf file with the following content:
Then restart the service: service mysql restart
Then, the problem should be solved: