Comments on Installing Seafile 6.3.2 inside ISPConfig 3.1

Hi. Thanks for all those instructions: Really helpfull.

I seems that this solution does not support letsencrypt. I got it working with the following Apache Directives right below "RewriteEngine On":

#letsencrypt

ProxyPass "/.well-known/acme-challenge" http://127.0.0.1:80/letsencrypt/.well-known/acme-challenge

        ProxyPassReverse "/.well-known/acme-challenge" http://127.0.0.1:80/letsencrypt/.well-known/acme-challenge

        RewriteRule ^/.well-known/acme-challenge - [QSA,L]

Hi, thank you for that! However, I had to remove 'letsencrypt/' to make it work, so for me it looks like this:

<code>

ProxyPass "/.well-known/acme-challenge" http://127.0.0.1:80/.well-known/acme-challenge

        ProxyPassReverse "/.well-known/acme-challenge" http://127.0.0.1:80/.well-known/acme-challenge

        RewriteRule ^/.well-known/acme-challenge - [QSA,L]

</code>

Hi Daniel,

Are you running an older version of ISPConfig? We are currently running 3.1.12 and did not face any issues activating letsencrypt on the seafile domain. 

Hi, thanks for this tutorial! Sorrowly I always end-up with the following error while setting up the databases:

Generating ccnet configuration ...

Traceback (most recent call last):

  File "setup-seafile-mysql.py", line 1515, in <module>

    main()

  File "setup-seafile-mysql.py", line 1467, in main

    ccnet_config.generate()

  File "setup-seafile-mysql.py", line 817, in generate

    if Utils.run_argv(argv, env=env_mgr.get_binary_env()) != 0:

  File "setup-seafile-mysql.py", line 85, in run_argv

    env=env)

  File "/usr/lib/python2.7/subprocess.py", line 390, in __init__

    errread, errwrite)

  File "/usr/lib/python2.7/subprocess.py", line 1024, in _execute_child

    raise child_exception

OSError: [Errno 8] Exec format error

Would be very friendly if you could give me a hint solving this issue - Thank you very much in advance!!!

The whole installation using your Tutorial: "The Perfect Server - Debian 9 (Stretch) with Apache, BIND, Dovecot, PureFTPD and ISPConfig 3.1"

on a fresh Raspian Stretch 9 environment on a RaspBerry Pi 3+ was running very smooth... A great thanks therefore too!!!

Kind regards, Hermann

Hello,

Thank you for this tutorial.  This looks interesting and I may test this out, soon.  I've been looking for a better way for my users to maintain their files. 

Why Python 2.7 when Python 3 is already on the system?  Is this specific to Seafile?  Python is already a resource hog (fail2ban comes to mind).  I'm a little resistant to installing another version.

Thank

This is a seafile thing... they may be using something different as of this time, but when i wrote this tut, the default was 2.7

I ran into a problem today with this as my updatescript wouldn't run properly. I updated ISPConfig to the newest version as there were some issues with previous versions and LetsEncrypt. In the end, my fix was simply issue the following commands: 

certbot delete --cert-name seafile.mydomain.comcertbot certonly --apache (Run through setup steps)

This will delete all the LetsEncrypt files for your domain, then recreate them. After this, enter ISPConfig for your seafile site. Uncheck the Lets Encrypt checkbox and save. Then make sure the "Skip Lets Encrypt Check" box is checked in the server.config -> web -> ssl section.

Wait a minute until the server.sh cron runs, then go back into your Seafile ISPConfig page and recheck LetsEncrypt.

It doesn't sound like you put the correct database information in when asked to initialize your seafile database.

Hi there

Thanks for the instructions.

After adding the apache directive the server would not restart because mod_proxy was not enabled.

For those that had the same issue, just check if the module is enabled with:

apache2ctl -M

If the module is not enabled you can enable it with the following commands:

a2enmod proxy

a2enmod proxy_http

a2enmod proxy_balancer

a2enmod lbmethod_byrequests

The last three modules are most likely already enabled.

regards

Manfred

I've also set up nextcloud within a site and used it's external storage feature to connect it by ssh to folders it needs to be connected to such as the root of your site.  Simple to set up, too.  better yet, it runs under the website's encryption key.