Posts by Nuxwin

    I did re-generate the files using the WebUI, so I thought that this will be enough to show the correct values.

    You miss the following part:


    Quote from documentation

    Be also aware that because those files are static, some information such as memory could not matches with those that you have set for your customers (e.g. using the PHP editor provided by i-MSCP).

    but I suspect something went wrong with the secondary IP of the server during the upgrade, which I also had to remove manually from the sql database before being able to successfully install i-MSCP, but by removing the IP manually after your reply I realize that most likely that was the cause why the subdomains kept failing and giving the error because they were assigned to the secondary IP and the secondary IP was deleted. At least now I have a better understanding of some things.

    Exactly ;)

    Good evening,


    The module that is responsible for subdomains processing join many database tables while retrieving data. Therefore, if one of required data is not found in a specific table, this can lead to such error. Data not found generally mean that data from another table doesn't exists.


    Anyway, you should really avoid removing database rows manually. By doing this, you can end with corrupted database, producing worse result. So here, you have a subdomain with ID 4. For that subdomain please check the following:

    • The parent domain exists: In the subdomain table, search for the domain_id column value, then check that the corresponding ID exists in the domain table.
    • The IP address assigned to the parent domain exists: In the domain table, search for the domain_ip_id column, then make sure that the referenced ID exist in the server_ips table.

    Please next time, ask us before doing anything... Asking us after playing with something you don't understand is not really the right way. A customer that is processing such way would lose free support.

    Hallo zusammen

    ich habe gerade festgestellt, dass auf meinem Server ein Angriff läuft. Offensichtlich versuchen die Angreifer auf phpmyadmin zuzugreifen. Gibt es da eine Schwachstelle?

    Jemand eine Idee?


    Gruß

    Fan-Com

    The bbcode tags are not for dogs. This is the first and last warning. Next time, you'll get a ban. Please fix, else, the full post will be deleted.

    yap a friend of mine bought the plugin 2 weeks ago too and we installed it and got certs. one day later we got the same email as the rcrave.

    pls update this plugin to use the latest certbot or we will not be able to get new certs starting from feb 13. 2019. 5 days to go...

    thank you

    You should really refrain yourself when you start talking something that you don't understand... The message you did received doesn't say that your certificates won't be issued/renewed cause of the old version of Certbot that you're using. That message simply state that the TLS-SNI-01 validation method will stop working. The fact is that the plugin doesn't use (and never has used) that validation method. The plugin make use of the HTTP-01 validation method.


    If you received that message, that is either because you issued SSL certificates manually, using the TLS-SNI-01 validation method, either because the message is a generic one sent to all people using a Certbot version supporting the TLS-SNI-01 validation method. Certbot will be updated in next plugin version anyway. In any case, this doesn't cause any problem.

    Good morning,


    This has nothing to do with i-MSCP. If you cannot access the control panel locally, that's either because you have not setup your router correctly or because that last doesn't support NAT loopback.


    One thing you could try is to setup a DMZ instead of makeing NAT/PAT.

    Good morning,


    The github status link has changed. This has nothing to do with us. Regarding i-MSCP, it is under heavy development and it would be useless to create a new theme from current version as we are currently rewritting the frontend. Development take time. The development of the new frontend is done in private repository to avoid useless comment till a version is usable. If you look at my facebook, you'll see that , I'm often posting related screenshots.