Nginx Reverse Proxy

[DWhell2]

Have upgraded to Seafile Server 6.2.1 and read the information that recommends moving away from fastcgi to WSGI.
Changed my nginx conf from the previous fast cgi one to WSGI but nothing works.

I have switched back to the fastcgi conf and all is okay again.

One thing I haven’t been doing is starting seahub with the -fastcgi option.

Here is my new conf, any reason this isn’t working? so i need to install a different nginx module?

server {
listen 443 http2;
ssl on;
ssl_certificate /etc/ssl/cacert.pem;
ssl_certificate_key /etc/ssl/privkey.pem;
server_name xxxx.com;
proxy_set_header X-Forwarded-For $remote_addr;

    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains";
    server_tokens off;

location / {
    proxy_pass         http://127.0.0.1:8000;
    proxy_set_header   Host $host;
    proxy_set_header   X-Real-IP $remote_addr;
    proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header   X-Forwarded-Host $server_name;
    proxy_read_timeout  1200s;

    access_log      /var/log/nginx/seahub.access.log;
    error_log       /var/log/nginx/seahub.error.log;
    client_max_body_size 0;
}

location /seafhttp {
    rewrite ^/seafhttp(.*)$ $1 break;
    proxy_pass http://127.0.0.1:8082;
    client_max_body_size 0;
    proxy_connect_timeout  36000s;
    proxy_read_timeout  36000s;
    proxy_send_timeout  36000s;
    send_timeout  36000s;
    proxy_request_buffering off;
}

[jobenvil]

@DWhell2

One thing I haven’t been doing is starting seahub with the -fastcgi option.

Also when you use fastcgi you don’t run with seahub.sh start-fastcgi and it works?

[DWhell2]

yes thats correct

[jobenvil]

thanks for the feedback I will test it on rpi.

[jobenvil]

@DWhell2

Changed my nginx conf from the previous fast cgi one to WSGI but nothing works.

another clarification, only seahub doesn’t work (start without failure) or seafile doesn’t work as well (start without failure)? Both or only seahub doesn’t start?

[Captain_Rage]

I’m having the same issue since uppgrading Seafile server to 6.2.1 on a Raspberry Pi B+.
The old config used to work with the previous version but now I’d like to reconfigure my setup to use WSGI.

Old nginx config (used to start seahub with fast-cgi):

[root@mushroom mushroom]# cat /etc/nginx/servers-available/seahub.bak

server {
listen 8001; # <--------------------------------------- NGINX PORT
ssl on; # <-------------------------------------------- SSL
ssl_certificate /etc/nginx/ssl/seahub.crt; # <--------- SSL
ssl_certificate_key /etc/nginx/ssl/seahub.key; # <----- SSL
server_name some.website.com; # <---------------- CHANGE THIS
error_page 497 https://$host:$server_port$request_uri;

location / {
    fastcgi_pass    127.0.0.1:8000;
    fastcgi_read_timeout 1000s; # <-------------------- REMEDIES '504 GATEWAY TIME-OUT'
    fastcgi_send_timeout 1000s;

    fastcgi_param   SCRIPT_FILENAME     $document_root$fastcgi_script_name;
    fastcgi_param   PATH_INFO           $fastcgi_script_name;

    fastcgi_param   SERVER_PROTOCOL     $server_protocol;
    fastcgi_param   QUERY_STRING        $query_string;
    fastcgi_param   REQUEST_METHOD      $request_method;
    fastcgi_param   CONTENT_TYPE        $content_type;
    fastcgi_param   CONTENT_LENGTH      $content_length;
    fastcgi_param   SERVER_ADDR         $server_addr;
    fastcgi_param   SERVER_PORT         $server_port;
    fastcgi_param   SERVER_NAME         $server_name;
    fastcgi_param   HTTPS   on;
    fastcgi_param   HTTP_SCHEME https;

    access_log      /var/log/nginx/seahub.access.log;
    error_log       /var/log/nginx/seahub.error.log;
}
location /seafhttp {
    rewrite ^/seafhttp(.*)$ $1 break;
    proxy_pass http://127.0.0.1:8082;
    client_max_body_size 0;

}

location /media {
    root /home/seafile/pannkaka/seafile-server/seahub; # <-- change: 2015-08-27
    include /etc/nginx/mime.types; # <--- UNCOMMENT THIS IF CSS FILES AREN'T LOADED
}

}

New nginx config (starting without fast-cgi, to my understanding):

[root@mushroom mushroom]# cat /etc/nginx/servers-available/seahub

server {
listen 8001; # <--------------------------------------- NGINX PORT
ssl on; # <-------------------------------------------- SSL
ssl_certificate /etc/nginx/ssl/seahub.crt; # <--------- SSL
ssl_certificate_key /etc/nginx/ssl/seahub.key; # <----- SSL
server_name some.website.com; # <---------------- CHANGE THIS
error_page 497 https://$host:$server_port$request_uri;

location / {
proxy_pass          http://127.0.0.1:8000;
    proxy_set_header    Host $host;
    proxy_set_header    X-Real-IP $remote_addr;
    proxy_set_header    X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header    X-Forwarded-Host $server_name;
    proxy_read_timeout  1200s;

    # used for view/edit office file via Office Online Server
    #client_max_body_size 0;

    access_log      /var/log/nginx/seahub.access.log;
    error_log       /var/log/nginx/seahub.error.log;
}
location /seafhttp {
    rewrite ^/seafhttp(.*)$ $1 break;
    proxy_pass http://127.0.0.1:8082;
    client_max_body_size 0;

}

location /media {
    root /home/seafile/pannkaka/seafile-server/seahub; # <-- change: 2015-08-27
    include /etc/nginx/mime.types; # <--- UNCOMMENT THIS IF CSS FILES AREN'T LOADED
}

}

Edit:
Sorry for the messed up formatting. Not sure how to fix it. To be clear: the Seafile clients (one desktop and one Android) seem to connect and sync, but now the libraries don’t show up; they just keep loading indefinitely. When trying to access Seafile through the browser, it times out.

[DWhell2]

glad to see I’m not the only one with this issue. Is there any reasoning behind the switch from fastcgi to WSGI? Improved performance or more reliable?

[jobenvil]

@DWhell2

Improved performance or more reliable?

Yes, this is the case. It is mentioned in the announcement of the 6.2.0 release and in the manual. Gunicorn was native delivered with Seafile for a long time ago and is nice to see him back again. Here more Infos regarding gunicorn and wsgi here and here. That should be considered an improvment, not a regresion.

[mercury]

Having same problem here under Ubuntu 16/Nginx on Seafile CE 6.1.2.

Command/script ‘seahub.sh start’ appears to work in terminal but ‘502 Bad Gateway’ in browser. Seafile Client works.

Command seafile-start.sh still works but it says that it is loading using fastcgi. Web interface OK. Hmm…

Anybody got a clue on how to disentangle from fastcgi?

-Thanks!

[thanatos]

@DWhell2 @Captain_Rage

we had the same issue in over here in this thread when moving to wsgi --> link
The thread is in german, but basically the fix was to add your port to the proxy_set_header in your ngingx coniguration

  location / {
         proxy_pass         http://127.0.0.1:8000;
         proxy_set_header   Host $host:8001;                  <------ YOUR PORT HERE
         proxy_set_header   X-Real-IP $remote_addr;
         proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
         proxy_set_header   X-Forwarded-Host $server_name;
         proxy_set_header   X-Forwarded-Proto https;
         proxy_read_timeout  1200s;

         # used for view/edit office file via Office Online Server
         client_max_body_size 0;

         access_log      /var/log/nginx/seahub.access.log;
         error_log       /var/log/nginx/seahub.error.log;
    }