Was anyone able to successfully set up seafile with a reverse proxy (swag or NPM etc.)?
I'm currently trying to set it up but I either break the login "CSRF verification failed" or I can't upload/downlload stuff remotely.

I'm just curious if someone has a configuration that works

Hello
I have got it to work under NPM just fine, but I cant get it to work under swag
No matter what I try with the config file I just get the 500 error at best.

For NMP I just had to make sure the right domain was set in the Seafile settings, else it worked.
For NMP the config file looked like this:

 

# ------------------------------------------------------------
# seafile.domain.com
# ------------------------------------------------------------


server {
  set $forward_scheme http;
  set $server         "unraid server ip";
  set $port           8082;

  listen 8080;
listen [::]:8080;

listen 4443 ssl http2;
listen [::]:4443 ssl http2;


  server_name seafile.domain.com;


  # Let's Encrypt SSL
  include conf.d/include/letsencrypt-acme-challenge.conf;
  include conf.d/include/ssl-ciphers.conf;
  ssl_certificate /etc/letsencrypt/live/npm-20/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/npm-20/privkey.pem;






  # Block Exploits
  include conf.d/include/block-exploits.conf;







    # Force SSL
    include conf.d/include/force-ssl.conf;





  access_log /config/log/proxy-host-21_access.log proxy;
  error_log /config/log/proxy-host-21_error.log warn;

location /accounts { deny all;}





  location / {









    

    # Proxy!
    include conf.d/include/proxy.conf;
  }


  # Custom
  include /data/nginx/custom/server_proxy[.]conf;
}

 

I moved to caddy which was super easy to set up.

No more headache from swag/NPM

After 6 days and over 30+ hours I was about ready to give up when I FINALLY was able to get Seafile (specifically uploads/downloads) working with SWAG. Huge shout out to user tubezleb for providing this solution on GitHub. I did using the official image and following some of the context in this guide.

 

I created a file called seafile.subdomain.conf and the only change I needed to make in this was to update the server name to match my domain. I also had to update the port from 8000 to my port number since 8000 is already in use on my server in the proxy config.

 

I also had to add several variables to the container that I attached in the screenshot.

 

Last thing, in the /seafile/conf directory created after you hit apply I needed to update the web ui port in the following files (this only matters if you don't use port 8000):

• gunicorn.conf
• seafdav.conf

• seahub_settings.py

Total sidenote, email notifications started working after I got the file server working. Follow this guide here. Hope this helps someone.