Posts by Catscrash

  • Debian 10 (Buster)

    Quote from Nuxwin

    Yes since default branch is the 1.5.3-maintenance ;) But you don't say us the error you get... Anyway, there are several changes not committed yet... I'll try to make it working for tomorrow.

    Hi,


    sorry about that, I edited my earlier answer before I saw your message. There's more detail now

  • Debian 10 (Buster)

    Quote from Nuxwin

    joximu



    Which version you tried to install exactly? Give me the exact link you used please ;) I'm asking that because I'm pretty sure that you tried with the wrong branch... The github branch to use is https://github.com/i-MSCP/imscp/tree/1.5.3-maintenance.

    Hi Nuxwin,


    I did a "git clone https://github.com/i-MSCP/imscp.git" on buster - this should lead me to 1.5.3-maintenance, right?


    Edit:

    just did another clean install of buster


    Code
    1. sudo apt-get -y --auto-remove --no-install-recommends install ca-certificates perl whiptail wget


    Code
    1. catscrash@imscp-test:~/imscp$ git branch
    2. * 1.5.3-maintenance


    Code
    1. catscrash@imscp-test:~/imscp$ sudo perl imscp-autoinstall -d
    2. [FATAL] autoinstaller::Adapter::DebianAdapter::_getPackagesDialog: Can't locate XML/Simple.pm in @INC (you may need to install the XML::Simple module) (@INC contains: /home/catscrash/imscp /home/catscrash/imscp/engine/PerlLib /home/catscrash/imscp/engine/PerlVendor /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /home/catscrash/imscp/autoinstaller/Adapter/DebianAdapter.pm line 932.

    I could go and install this package now, but the missing packages just keep coming. That's what I had last time as well. I installed everything from the debian-buster.xml requirements-section manually last time, but then something else failed. I'm happy to try that again if it helps you to get a more detailed error message of what failed later on

  • Debian 10 (Buster)

    right, sorry, it wasn't php-7.2 - that was for stretch, I installed 7.3 from default buster repo, but didn't work either. Error had nothing to do with php... the installation just couldn't continue properly.


    I installed all the requirements from the debian-buster.xml, but no luck

  • Debian 10 (Buster)

    Quote from joximu

    Hi

    I tested the last "nightly" (july 3rd) on devuan ascii - the installation requires lots of packets I had to install manually (this is not common in i-mscp) - and at the end I hat to install PHP - but the only PHP I got from devuan ascii (is equal to debian 9) is a php 7.0.x - which is "to old for i-mscp...


    I think the installation was better in one of the end-may or june nightlies... I hope (don't know) Nuxwin ist working on the plugins and has no time at the moment. The situation is sad...

    I had the same experience, even with manually installing all dependencies and PHP 7.2 via repo, I couldn't get it running.

  • Debian 10 (Buster)

    Hi,


    since Debian 10 is officially stable now, is there a timetable as to when imscp will be installable on it? Is there a dev version which is already accepting it? I'd be happy to help with testing


    Thanks

  • transfer mail accounts to new instance

    Hi,


    are the mail passwords currently reversibly encrypted? If so, how to decrypt them?


    On first glance it looks like some kind of salted hash, is it enough to transfer those into the new database, or is this also peppered in some way and depending on variables on this specific instance?


    thanks!

    Catscrash

  • What is the recommended way for (sub)domains with special apache configuration?

    Hi,


    what is the preferred / recommended way, to use web apps on some domains, that require special apache configurations like reverse proxy settings, perl scripts, etc.? e.g. gitlab, otrs, etc. - How do you solve these situations?


    Currently I created an additional .conf file in sites-available / sites-enabled under an additional subdomain (like service-internal.host) and then create a proper domain / subdomain (like service.host) via imscp with the proxy setting - forwarding to the additional subdomain.


    This way the customer sees the proper service.host domain and I can administrate stuff like letsencrypt, mails etc. for this domain via imscp.


    But this approach has two problems

    a) I always need an additional subdomain for every of these cases

    b) I'm not too sure if the autoinstaller would remove the additional .conf file when doing an update etc. Could you say something about that?


    Thanks