Posts by TheRiddler1982

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

    However, I have some issues with LetsEncrypt using Debian 10

    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/", line 5, in <module>
    5. import logging.handlers
    6. File "/usr/lib/python2.7/logging/", line 26, in <module>
    7. import sys, os, time, cStringIO, traceback, warnings, weakref, collections
    8. File "/usr/lib/python2.7/", line 14, in <module>
    9. from _weakref import (
    10. ImportError: cannot import name _remove_dead_weakref at /var/www/imscp/gui/plugins/LetsEncrypt/backend/ 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).

    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.

    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?

    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!

    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 :-).


    Hi Nuxwin,

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


    And the sources.d files:


    2. # You may comment out this entry, but any other modifications may be lost.
    3. deb stable main


    1. deb stretch nginx
    2. deb-src stretch nginx

    Thanks again!

    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):


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

    1. deb stretch main
    2. deb-src 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 :-)


    just noticed while browsing the file system that my domain using umlaute ("ü") gets somehow different mapped to the file system:


    Is this by design?

    I would expect


    Can I rename it differently manually? If so, where do I have to change it in I-MSCP config?



    Apologies for that. Now that I know the port :-):

    It has been an issue with Portainer which has been victim of an attack on a specific port and they changed their proxy port to a new one to stop the attacks. That happened 3 days ago. A restart of the swarm updated the docker file and there was port 9876.

    I would have never found the reason for that error! Thanks!

    I was setting up Kibana today to get a better look on my logs, that was clearly a chicken and egg problem :P