Host your own SeaFile cloud (with ssl support)

    Quote from UncleSam


    [size=small]Feel free to use the "Thanks" Button :D[/size]



    You want some donuts too? :D :P :D

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

    SSH key for online support

    Edited once, last by Nuxwin ().

    So, I´m trying to setup seafile. But once in a while my http.conf gets overwritten. or how can/should I prevent that?


    What would be even more amazing would be python and or proxy pass support in imscp :)


    And I can´t get fcgi to work :/ so far I only use proxy pass completely...

    This tutorial is only for installing SeaFile on a I-MSCP environment. If you are searching for a tutorial to install SeaFile without I-MSCP have a look at the developer homepage (there is a wiki with realy good examples).

    Quote from UncleSam

    This tutorial is only for installing SeaFile on a I-MSCP environment. If you are searching for a tutorial to install SeaFile without I-MSCP have a look at the developer homepage (there is a wiki with realy good examples).


    As written, I got it allready running, with SSL support and via Proxy revery (to port 8000) because I can´t manage to get it run via fcgi support (start-fastcgi)


    Another problem is: if i edit, lets say the ssl_subdomain.domain.conf file (i need to remove the unused stuff or proxy reverse won´t work. IMSCP reverts once in a while (or after a restart) to the original version which cuts out all reverse proxy stuff...

    Quote from Qefx

    As written, I got it allready running, with SSL support and via Proxy revery (to port 8000) because I can´t manage to get it run via fcgi support (start-fastcgi)


    Another problem is: if i edit, lets say the ssl_subdomain.domain.conf file (i need to remove the unused stuff or proxy reverse won´t work. IMSCP reverts once in a while (or after a restart) to the original version which cuts out all reverse proxy stuff...


    Have you performed this step?

    Quote

    Open the apache2 config file "/etc/apache2/apache2.conf" and add this line at the bottom (where 127.0.0.1:8000 is the default seafile port)Quellcode

    Code
    1. FastCGIExternalServer /var/www/virtual/domain.tld/seafile/htdocs/seahub.fcgi -host 127.0.0.1:8000


    But I have no idea why you have a http.conf you edit. I-MSCP supports debian and ubuntu and both uses apache2.conf files. (I think http.conf is centos or fedora). What OS are you using?


    (I added my information about reverse proxy to the howto - please check if this is working for you)

    Thank you for your great manual. I have managed to get seafile-server working and seahub partially. I could start seahub over https thats working. I also could login and so on, but when I upload or download something on the seahub webinterface I got the following security message:


    Mixed Content: The page at 'https://xxx.tld/#my-libs/lib/725e3802-89c7-4f6d-845a-b81da679b550' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://www.xxx.tld/seafhttp/upload-aj/6cfe49e5-d3c2-46b2-8348-754683607d5b'. This request has been blocked; the content must be served over HTTPS.


    Could someone help?

    Open the file seahub_settings.py (probably located in /home/seafile/haiwen if you followed the usual howtos). Look for FILE_SERVER_ROOT and check if it contains https:// instead of http://


    edit: Do the same thing for ccnet.conf and the SERVICE_URL

    Hi,


    I do have those config files like you wrote
    seahub_settings.py

    Code
    1. HTTP_SERVER_ROOT = 'https://xxx.tld/seafhttp'FILE_SERVER_ROOT = 'https://xxx.tld/seafhttp'




    ccnet.conf

    Code
    1. SERVICE_URL = https://xxx.tld


    imscp Apache conf


    Maybe I missed something else?

    Seafile Server 5.1.0 is currently in beta phase - I think it would be better to stay on stable channel.


    FYI: instead of linking your seafile server directly (/opt/seafile/seafile-server-5.1.0/seahub/media) use the link seafile generates on install/update to be sure that an update is not breaking your configuration. This link should point to the exact same direcory: /opt/seafile/generates seafile-server-latest/seahub/media (please check before using)


    Seafile updated their https documentation. There are some entries different from the last documentation which I used in here. Please check http://manual.seafile.com/deploy/https_with_apache.html