Posts by DrCarsonBeckett

    That is why you actually need to read the howtos and errata files before you do something which might affect i-MSCP.

    There are ways how to downgrade again, which might need a bit of work.

    So far, I think the issue isnt directly the phpswitcher module. Its more like an issue raised by the upgrade.

    Did you tried to uninstall and remove that plugin and after that re-install it?

    Either you downgrade or try to fix the issue which you got now. Or you do wait till Nuxwin or other projects-members are seeing this topic.^^

    Debian 10 isn't supported officially (but another user reported its working). I think thats the issue here at the moment.

    The needed phpswitcher version will re released with or close after / before the new i-MSCP version. Which got support for newer php versions.

    Importing the mail data isnt the problem.

    Simply backup the mail folder, in general: "/var/mail/virtual/*" .

    Create the domains again and then the mail accounts, after that copy every folder back to: "/var/mail/virtual/*".

    The next step is runing this command: "perl /var/www/imscp/engine/setup/imscp-reconfigure --fix-permissions" after it.

    If you use roundcube or similar and you created contacts and so on, you should create a backup of that database too. Thats not getting saved automatically.

    After that, you can see the mails like nothing happened (I already did that myself and it works pretty much fine).


    Btw, if you are going to install Debian. Make sure to use Stretch at least, but please dont use Buster. Buster isnt (at the moment) not really supported from i-MSCP.

    Its saved in a configuration file as far as I know. I only checked the plugin ones, so that might not be correct.

    And that configuration file might get changed during an upgrade. Since you manually upgrade the plugins, you can always make sure to change the files before you upload the archive.

    I read something about a database, but I think thats just for integration and configuration of SpamAssassin itself.


    Instead of changing the config file in a very tiresome and costly way, you should create a blacklist config file and include it in the main spamassassin config.

    The file name should be local.cf and it should be located in : /etc/spamassassin/ (if I am correct).

    Well, technically that seems to be correct. That tutorial is only meant for a direct switch to another server (same OS). So you need to keep that in mind. Means it may differ from the tutorial.

    I wouldnt do that without a full back. Means, save the databases manually (every one as a single backup).

    Plus, make sure to backup the /var/www/virutal/*domains*/backup folders.

    Do a manual backup from your mail system as well and if needed, from the roundcube/etc db as well.



    Do you use the server just for your self? If yes, I would do something else to keep it as clean as possible.

    1. I would check if the packages which are used for i-MSCP are still compatible with it and check if any i-MSCP related parts are changed. But I wouldnt recommend it (to fully upgrade).

    2. If it works like it is not, let it this way. If something doesnt work, try "apt-get install -f".

    3. I would check for errors and abnormal behaviors. If somethings off and you cant fix it the easy way then you should search how to downgrade (which is possible with a bit of work).

    4. My guess is that he waits a bit till everything is a bit smoothed out.



    Edit:

    I am still wondering why did you use dist-upgrade? Simply update and upgrade should be fine enough. :-/