Posts by Martini

  • Installing IMSCP without using outside repositories - composer, github, etc.

    Hello,
    I need to deploy imscp servers in a local network that has no internet access. I'm using Debian 8.6 Jessie as my server OS. I've successfully created my local APT repository so Debian grabs all necessary system packages from it and doesn't need internet to download it. But i've run into difficulty with imscp. I've noticed Imscp 1.3.x installer is not self-contained - at a certain setup stage it wants to download "composer" packages or "github" packages. I wanted to alter the imscp 1.3.x setup to include the tools such as phpmyadmin, roundcube and monstaftp so that I don't have to depend on internet to fetch those packages.
    Could someone please help me or give advice on how to include tools from composer packages inside the imscp package so the setup doesn't try to download them from the internet?
    Best Regards,
    Martini

  • PHPMyAdmin import file size

    Hello,
    I've just installed the newest IMSCP 1.3.1 panel from scratch on a fresh debian 8.5 jessie. I've managed to configure most of the stuff as needed, but I have problem with one thing: I can't change the import file size in phpmyadmin. Up until imscp 1.3.0 altering values in a single php.ini in /var/www/fcgi/master directory did the trick perfect, but in 1.3.1 something seems to be different. I've tried to alter all php.ini files I could find on the system changing upload_max_filesize and post_max_size values in each of them, then I did a server reboot, unfortunately the size in phpmyadmin stays at 64MB (previously 20MB before php.ini changes) and won't budge. Can someone please tell me which file should be changed or what else should be done to successfuly increase the phpmyadmin import file size?
    Best Regards,
    Martini

  • SSL Certificate import error

    It seems extremely unlikely IMSCP would have a root certification authority list, and even if was so I think it would be possible to add my own root CA to it. Besides I wouldn't want to be dependent on an outside SSL authority.
    I wonder if somewhere in the process there is an error I've made that make's IMSCP flip like that, but there probably is a way to fix it, I just don't know what it is (at least for now).
    Please advice.

  • SSL Certificate import error

    Hello,
    I'm using I-MSCP 1.3.0 (Debian Jessie 8.5 - fresh install) and I'm trying to enable SSL for a domain created.
    I've followed this tutorial to the letter:


    https://jamielinux.com/docs/op…thority/introduction.html


    I've setup my Root CA, Intermediate CA, Chain Certificate and a cert for my domain (for test purposes it's koy.org). Of course I'm using the appropriate dialog in I-MSCP Panel to implement these changes, but each time I try to import an SSL cert for my domain I get an error message saying: At least one intermediate certificate is invalid or missing.



    Could someone please have a look at my issue and hopefully offer some advice how to fix it.
    I'm attaching all the relevant certs I've created so you can see what they look like.
    All these certs were created with OpenSSL on the newest possible Debian Jessie distro.


    Please advice and thank you in advance,
    Martini

    Files

  • 1.2.17 - FTP directory listing problem

    I completely understand - one hitch though - both the computer that I'm using to access my imscp-based server and this server are inside the LAN, and the LAN IP address of the server is of course set to be static via /etc/network/interfaces so they are obviously on the same NAT side so I don't think this setting matters. I am well aware of dynamic IP issues and that's why I didn't try to access the server from the outside of my network.


    BTW: I've just run a check and it seems my FTP Client (FileZilla) is set to passive transfer mode by default - these settings weren't altered.

  • 1.2.17 - FTP directory listing problem

    Hello,
    The FTP directory listing is a pain in the newest (as of today) version of IMSCP - 1.2.17
    It takes an agonizing average of 60 seconds for the directories and files to simply get listed in an FTP client (in my case FileZilla).
    I've checked the proftpd.conf for the MasqueradeAddress setting to see if it was to blame, but this setting was absent in any proftpd.conf file I have on the system (Debian 8.3 Jessie). I also have SSL enabled for panel and all services alike (TLS for ProFTPd) but I don't think that's related. I've already submitted an issue in the imscp bug report system and would hopefully love to see it fixed once and for all.


    Martini