Posts by Pimbo

    Did anything change here? regarding to errata imscp included well known in every webfolder skeleton, domain alias, subdomain. I was using letsencrypt with the change in apache2 conf you can see above. Since the update to letsencrypt 3.0.0 and IMSCP 1.4.1 the browser are not automatically leading me to the https page, which itself works fine. HSTS is active

    PHP 5.6-FPM
    Debian 8

    Apache2 vlogger script
    Due to an important bug found in vlogger script, and that has been fixed in this new version, it is recommended to runthe following command to make sure that there is no vlogger process left on your system before upgrading:

    # pkill -KILL -f vlogger

    Was this bug already existent in I-MSCP 1.3.16 cause I forgot to execute the command before updating 1.3.16 to 1.4.1

    My solution:

    1. ProxyPass "/.well-known/acme-challenge" "!"
    2. ProxyPass /seafhttp
    3. ProxyPassReverse /seafhttp
    4. RewriteRule ^/seafhttp - [QSA,L]

    is this a good solution?

    IMSCP 1.3.14
    Letsencrypt 2.0.5
    Seafile 6.0.7
    Debian Jessie 64 bit

    I have a similar problem with my letsencrypt and seafile configuration:

    1. Saving debug log to /var/log/letsencrypt/letsencrypt.logStarting new HTTPS connection (1): acme-v01.api.letsencrypt.orgObtaining a new certificatePerforming the following challenges:http-01 challenge for cloud.***.dehttp-01 challenge for***.deUsing the webroot path /var/www/virtual/LetsEncrypt for all unmatched domains.Waiting for verification...Cleaning up challengesFailed authorization procedure.***.de (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from***.de/.well-known/acme-challenge/KBCLDbx3AqlORK6h2zR5YEmAe8Pf__AdDrkfo7oz-hY: "<!DOCTYPE html><html lang="en"><head><title>Private Seafile</title><meta http-equiv="Content-type" content="text/html; ch", cloud.***.de (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://cloud.***.de/.well-known/acme-challenge/JZ6TEnIaXGlbAJtWT-3I1PGoPqUo38_cEn_DLIflKNg: "<!DOCTYPE html><html lang="en"><head><title>Private Seafile</title><meta http-equiv="Content-type" content="text/html; ch"

    Apache CONF

    Obviously the module fastcgi was deactivated during the upgrade process. Is this normal?

    After manual activation of the mod apache runs normal, but the imscp controlpanel is not working anymore.

    Deleting The FASTCGIExternal command, running the upgrade, activatung mod fastcgi, insertig the FASTCGIExternal commadn, restart apache works fine. What do I have to do that the mod fastcgi is not deactivated during the IMSCP Upgrade?

    Debian 8 64bit

    During the Upgrade from 1.3.11 to 1.3.13 an error occured (have a look at the picture).

    The status apache output is:

    1. Drop-In: /lib/systemd/system/apache2.service.d└─forking.confActive: failed (Result: exit-code) since Mo 2016-12-26 15:36:17 CET; 6min agoProcess: 27916 ExecStart=/etc/init.d/apache2 start (code=exited, status=1/FAILURE)Dez 26 15:36:17 server1 apache2[27916]: Starting web server: apache2 failed!Dez 26 15:36:17 server1 apache2[27916]: The apache2 configtest failed. ... (warning).Dez 26 15:36:17 server1 apache2[27916]: Output of config test was:Dez 26 15:36:17 server1 apache2[27916]: AH00526: Syntax error on line 222 of /etc/apache2/apache2.conf:Dez 26 15:36:17 server1 apache2[27916]: Invalid command 'FastCGIExternalServer', perhaps misspelled or defined by a module not included in the server configurationDez 26 15:36:17 server1 apache2[27916]: Action 'configtest' failed.Dez 26 15:36:17 server1 apache2[27916]: The Apache error log may have more information.Dez 26 15:36:17 server1 systemd[1]: apache2.service: control process exited, code=exited status=1Dez 26 15:36:17 server1 systemd[1]: Failed to start LSB: Apache2 web server.Dez 26 15:36:17 server1 systemd[1]: Unit apache2.service entered failed state.

    The Problem is this line for my seafile configuration in line 222

    1. FastCGIExternalServer /var/www/virtual/ -host

    What exactly do I have to do now?


    Im going to upgrade within the next few days.

    But I think I am not going to delete this rewrite condition:

    RewriteCond %{REQUEST_URI} !(.*/\.well-known/acme-challenge/.*)

    This is not going to make it worse and it worked once only with this condition.

    1. Alias /.well-known/acme-challenge/ /var/www/virtual/LetsEncrypt/.well-known/acme-challenge/
    2. <Directory /var/www/virtual/LetsEncrypt/.well-known/acme-challenge/>
    3. <IfModule mpm_itk_module>
    4. AssignUserId www-data www-data
    5. </IfModule>
    6. Require all granted
    7. Satisfy any
    8. </Directory>

    @Nuxwin mentioned that this rewrite rule is not normal. So I am posting now my apache config. Maybe someone of you find teh problem. I used the Apache Vhost Config from UncleSams How to Host your own SeaFile cloud (with ssl support)

    Thisis my modified apache vhost:

    I think the other rewrite rules in the conf could lead to my experienced error with the LetsEncryptt Plugin