Posts by Mr.X

    Hi all,

    sorry to stress this again but I have a strange behavior now.

    As posted yesterday, I installed the letsencrypt plugin and got it working. Small issue with the PanelRedirect plugin was solved after a hint from Nuxwin.

    Thanks again !

    Now the issue is that the ssl cert is working for the admin page but I get a message that the cert is not valid.

    Reason for that is that the cert is created for the last created domain via letsencrpyt plugin and not for the original admin domain.

    Here is an example to understand it better.

    Admin panel is running with domain name

    But the used ssl cert is named for Domain2 was the last successful domain created by the letsencrypt plugin.

    Did I missed here something?

    In an other thread nuxwin in refering to use the ServerDefaultPage, Is this the trick here as well?



    Hi all,

    I hope you can help me out here.

    Running since a long time vhcs and imscp in my environment. Made a descission to upgrade from 1.3.0 to the lastest 1.5.3 version yesterday. All went well except a few smaller issues. But they were fixed.

    Now, after purchasing the Letsencrypt plugin I was looking forward to generate my SSL with it but it failed.

    In the logfiles I can read the following message:


    FailedChallenges: Failed authorization procedure. (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from…nceREym3A_EWKbZjevGB4S3A: "<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">


    <title>500 Proxy Error</title>


    <h1>Proxy Error</h1"

    First I thought it's a wrong DNS Setting that it cannot reach out to the server, but thats not the case. Ping is working as expected.

    Then I opened up the Link in a browser and could see a proxy 500 error message.


    Proxy Error

    The proxy server could not handle the request GET /.well-known/acme-challenge/KQCHHv1Uu0T3zujhfzEnceREym3A_EWKbZjevGB4S3A.

    Reason: Error during SSL Handshake with remote server

    Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

    Subdomain is working fine with letsencrypt ssl cert.

    Maybe you can guide me in a direction to fix the issue. .-)

    Running all my systems with latest stable debian (9)

    Thanks !



    please check the owner of the directory.


    Hi all,

    I did an update from 1.2.11 to 1.2.17 today and got the following error message:

    Any ideas how to fix it?