Cannot download or upload with https behind nginx proxy but i can nagivate webui

Seafile Server
,
1

I have a nginx proxy server on docker on the same machine of the seafile server on docker, i can navigate the webui but when i try to download or upload i obtain the HTTP ERROR 404.

I configured the fileserverroot correctly but it doesnt work

My ngix config:

# ------------------------------------------------------------
# xxx
# ------------------------------------------------------------


server {
  set $forward_scheme http;
  set $server         "192.168.1.173";
  set $port           8000;

  listen 80;
#listen [::]:80;

listen 443 ssl http2;
#listen [::]:443;


  server_name xxx;


  # 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-4/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/npm-4/privkey.pem;




# Asset Caching
  include conf.d/include/assets.conf;


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



  # HSTS (ngx_http_headers_module is required) (63072000 seconds = 2 years)
  add_header Strict-Transport-Security "max-age=63072000; preload" always;





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




proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
proxy_http_version 1.1;


  access_log /proc/1/fd/1 proxy;
  error_log /proc/1/fd/1 warn;



  location /seafhttp {
   
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-Scheme $scheme;
    proxy_set_header X-Forwarded-Proto  $scheme;
    proxy_set_header X-Forwarded-For    $remote_addr;
    proxy_set_header X-Real-IP		$remote_addr;
    proxy_pass       http://192.168.1.173:8082;

    

    # Asset Caching
  include conf.d/include/assets.conf;

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

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


    

  # HSTS (ngx_http_headers_module is required) (63072000 seconds = 2 years)
  add_header Strict-Transport-Security "max-age=63072000; preload" always;





    
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;
    


    
  }





  location / {





  # HSTS (ngx_http_headers_module is required) (63072000 seconds = 2 years)
  add_header Strict-Transport-Security "max-age=63072000; preload" always;





    
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;
    

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


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

`
2

If you’re encountering HTTP 404 errors when attempting to download or upload files via Seafile server through your nginx proxy, several potential issues could be causing this. First, ensure your Nginx configuration is correctly set up to proxy requests to the Seafile server by checking location blocks. Verify the fileserverroot configuration in Seafile settings points to the correct directory. Ensure file permissions are set appropriately for the files Seafile is serving. Check Seafile logs for error messages and confirm there are no firewall or network configurations blocking communication between containers. Ensure both containers are on the same Docker network and configured to work with HTTPS if applicable. Pass necessary headers from Nginx to Seafile and confirm you’re using the correct hostname or IP address. Finally, restart services after making any configuration changes. By addressing these points, you should be able to resolve the issue with file downloads/uploads via your Nginx proxy to the Seafile server.