Posts by TheRiddler1982

  • HowTo: I-MSCP 1.5.3 installation on Debian 10

    Here is the output after stopping and starting and having a look at the service status:


    Code
    1. service proftpd status
    2. ● proftpd.service - LSB: Starts ProFTPD daemon
    3. Loaded: loaded (/etc/init.d/proftpd; generated)
    4. Active: active (exited) since Mon 2020-09-07 15:55:31 CEST; 42s ago
    5. Docs: man:systemd-sysv-generator(8)
    6. Process: 132951 ExecStart=/etc/init.d/proftpd start (code=exited, status=0/SUCCESS)
    8. Sep 07 15:55:31 cloudserv111 systemd[1]: Starting LSB: Starts ProFTPD daemon...
    9. Sep 07 15:55:31 cloudserv111 proftpd[132951]: ProFTPD warning: cannot start neither in standalone nor in inetd/xinetd mode. Check your configuration.
    10. Sep 07 15:55:31 cloudserv111 systemd[1]: Started LSB: Starts ProFTPD daemon.

    Does anybody of you know how to get the default configuration or load the one used in I-MSCP?


    Thanks!

  • HowTo: I-MSCP 1.5.3 installation on Debian 10

    Quote from Eyecu

    Thanks for this howto, everything seems to work next to the filemanager and adding ftp users...could not retrieve directory listing. I am working on that part to find and fix the issue. But at least with this plugins work and everything seems to be working the way it should.


    EDIT: Found the cause for file manager and adding ftp accounts not working. proftpd for some reason will not start. Now to find the reason.

    Hi,


    I do not know if this error is related to you observation. After each login as user I get the following error mail:


    My proftpd service is running, though:


    Code
    1. service proftpd status
    2. ● proftpd.service - LSB: Starts ProFTPD daemon
    3. Loaded: loaded (/etc/init.d/proftpd; generated)
    4. Active: active (exited) since Sun 2020-09-06 15:47:23 CEST; 3h 42min ago
    5. Docs: man:systemd-sysv-generator(8)
    6. Process: 938 ExecStart=/etc/init.d/proftpd start (code=exited, status=0/SUCCESS)

    Do you have any idea what is causing the issue? This is new since the Debian 10 upgrade.

  • HowTo: I-MSCP 1.5.3 installation on Debian 10

    Thanks for the Apache link, didn't find it myself.


    However, I have some issues with LetsEncrypt using Debian 10


    Code
    1. Traceback (most recent call last):
    2. File "/usr/local/sbin/certbot", line 6, in <module>
    3. from certbot.main import main
    4. File "/opt/eff.org/certbot/venv/local/lib/python2.7/site-packages/certbot/main.py", line 5, in <module>
    5. import logging.handlers
    6. File "/usr/lib/python2.7/logging/__init__.py", line 26, in <module>
    7. import sys, os, time, cStringIO, traceback, warnings, weakref, collections
    8. File "/usr/lib/python2.7/weakref.py", line 14, in <module>
    9. from _weakref import (
    10. ImportError: cannot import name _remove_dead_weakref at /var/www/imscp/gui/plugins/LetsEncrypt/backend/LetsEncrypt.pm line 834.


    I am not a Python programmer and I do not now the codes behind LetsEncrypt. Can anybody of you help?


    The GUI is not working (buttons etc).

  • HowTo: I-MSCP 1.5.3 installation on Debian 10

    Thanks, I setup everything in a VMware and it worked perfectly. I have now done the upgrade on production without any serious trouble. For some reason, sslcompression is not supported, I had to disable it in order to get apache2 firing up.


    Code
    1. SSLCompression
    2. This version of OpenSSL does not have any compression methods available, cannot enable SSLCompression



    Further, MariaDB 10.4 upgrade worked, too. So, on first sight, everything worked besides SSL compression.


    Does anybody of you know that error with OpenSSL?

  • i-HMS ersetzt i-mscp? Weiter kostenfrei?

    Hi zusammen,


    vielen Dank für den Link zur Debian Buster Installation. ich habe allerdings Debian 9 mit I-MSCP 1.5.3 2018 laufen. Habe ich etwas zu befürchten, wenn ich Debian 9 auf 10 aktualisiere? Oder muss ich vorher was anpassen? Hat jemand hier Erfahrung?


    Danke euch!

  • Random html files are generated on my domain's htdocs folder - malware?

    Hi all,


    I am writing in this forum as I am an active user of I-MSCP :-).


    One month ago, I have noticed a random HTML file listed in one of my domain's htdocs root folders. The file is only present in one of my 5 domains.


    The file name is always "csvjsjd.html".


    The content is always the same:



    At first, I just deleted it but it gets recreated. In some cases a PHP file is created, too. The way the URL is created looks like that somebody tries to hide the target, i.e. it seems to be malware.


    I have no deep Linux skills to analyze the cause of it. Wordpress is running in this particular domain, no other areas of my root server are affected. So, it seems that the malware cannot leave the "userspace" of the domain.


    Any help appreciated :-).



    Thanks!

  • Latest MariaDB repo data seems to be incompatible with Debian 9

    Hi Nuxwin,


    sorry for the late reply, as I had no access to my server. Here is the answer:


    /etc/apt/preferences.d


    And the sources.d files:


    mod-pagespeed.list

    Code
    1. ### THIS FILE IS AUTOMATICALLY CONFIGURED ###
    2. # You may comment out this entry, but any other modifications may be lost.
    3. deb http://dl.google.com/linux/mod-pagespeed/deb/ stable main


    nginx.list


    Code
    1. deb http://nginx.org/packages/debian/ stretch nginx
    2. deb-src http://nginx.org/packages/debian/ stretch nginx



    Thanks again!

  • Latest MariaDB repo data seems to be incompatible with Debian 9

    Hi all,


    first of all, I am using the latest version of I-MSCP and Debian 9 (9.9). I set up I-MSCP from a clean Debian install (9.7). During I-MSCP setup I have chosen to use MariaDB 10.2:


    However, since about a month, MariaDB updates are not installed due to incompatibility (see attached screenshot from the console):


    pasted-from-clipboard.png


    I have not altered any apt sources manually. The one currently in use for MariaDB comes from the I-MSCP installation:


    Code
    1. deb http://mirror.netcologne.de/mariadb/repo/10.2/debian stretch main
    2. deb-src http://mirror.netcologne.de/mariadb/repo/10.2/debian stretch main

    Strech is the right distro name for version 9. I have googled about the library and for some reason the new requested version only runs with Debian 10. How is it possible that a repo built against Debian 9 requests Debian 10 dependencies? Aptitude offers some solutions. As the packages are part of I-MSCP I do not know what to do. Could you help me solve this conflict, i.e. update MariaDB without destroying I-MSCP?


    Thanks :-)