Seafile and LetsEncrypt

**Pimbo** · Dec 24th 2016

Debian Jessie 64bit
IMSCP 1.3.11

Hello,

I am trying to install seafile and using Letsencrypt to support ssl.

I always get this error code:

HTML

IMPORTANT NOTES:- The following errors were reported by the server:Domain: www.cloud.xxx.deType: unauthorizedDetail: Invalid response fromhttp://www.cloud.xxx.de/.well-known/acme-challenge/kUvtuE3C7P33lKDuN0hPKbjumHGuGD9V3DJynDRJ2XQ:"<!DOCTYPE html><html lang="en"><head><title>Private Seafile</title><meta http-equiv="Content-type" content="text/html; ch"Domain: cloud.xxx.deType: unauthorizedDetail: Invalid response fromhttp://cloud.xxx.de/.well-known/acme-challenge/nE_ovYIe41c6ZrBkOPvRVxPpYiXWgvgfWQaMdBtyE5E:"<!DOCTYPE html><html lang="en"><head><title>Private Seafile</title><meta http-equiv="Content-type" content="text/html; ch"To fix these errors, please make sure that your domain name wasentered correctly and the DNS A record(s) for that domaincontain(s) the right IP address.

I tried to allow the acess to this folder. I created this folder in /media and I tried to Redirect the folder in the normal htdocs, but there also does no folder exist like .well-known.

Code

#<Location /media/.well-known>
# Require all granted
#</Location>
#<Directory /media/.well-known/acme-challenge/ >
# Order Deny,Allow
# Allow from All
#</Directory>
RewriteRule ^.well-known/acme-challenge/(.*)$ /var/www/virtual/imscp/cloud.xxx.de/htdocs/.well-known/acme-challenge/$1 [R=301,NC,L]

Display More

maybe someone can help me how to active ssl with the letsecrypt plugin in a proper way.

**Pimbo** · Dec 24th 2016

Solution: Add this Rewrite Condition to the Howto RewriteConditions from UncleSam

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

**Pimbo** · Dec 25th 2016

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

Code

<Directory /home/seafile>
Require all granted
Options FollowSymLinks
</Directory>
Alias /media /home/seafile/haiwen/seafile-server-latest/seahub/media
RewriteEngine On
#
# seafile httpserver
#
ProxyPass /seafhttp http://127.0.0.1:8082
ProxyPassReverse /seafhttp http://127.0.0.1:8082
RewriteRule ^/seafhttp - [QSA,L]
#
# seahub
#
RewriteRule ^/(media.*)$ /$1 [QSA,L,PT]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_URI} !(.*/\.well-known/acme-challenge/.*)
RewriteRule ^(.*)$ /seahub.fcgi$1 [QSA,L,E=HTTP_AUTHORIZATION:%{HTTP:Authorizat$

Display More

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

**Nuxwin** · Dec 25th 2016

Best is to show us the vhost file (unmodified) that you used when the error occurred.

**Pimbo** · Dec 25th 2016

everything the same but without this:

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

**Nuxwin** · Dec 25th 2016

Code

cat /etc/apache2/imscp/before/vhost.conf

???

**Pimbo** · Dec 25th 2016

Code

Alias /.well-known/acme-challenge/ /var/www/virtual/LetsEncrypt/.well-known/acme-challenge/
<Directory /var/www/virtual/LetsEncrypt/.well-known/acme-challenge/>
<IfModule mpm_itk_module>
AssignUserId www-data www-data
</IfModule>
Require all granted
Satisfy any
</Directory>

**Nuxwin** · Dec 26th 2016

Well, this should be ok normally.

Also, request for ACME should not lead to rewrite since you have:

Code

RewriteCond %{REQUEST_FILENAME} !-f

At least, this should work with i-MSCP 1.3.12 and newest.

**Pimbo** · Dec 26th 2016

thx.

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.

Seafile and LetsEncrypt

Share

Daily visitors