Blank Page after upgrading from 6.3.4 to 7

Hi there, hope you can help me.
I’m trying to upgrade Seafile Server from 6.3.4 to 7.0.4. I’m on ubuntu 16 under nginx and not using fastcgi. The upgrade script ended succesfully, but when I start seafile 7.0.4 version I only get blank pages (totally white) on all the browsers.
Stopping 7.0.4 and switching back to 6.3.4 restores the normal behaviour.

This is part of my nginx configuration

server {
server_name ourserver.com;

proxy_set_header X-Forwarded-For $remote_addr;

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 seafileformat;
     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;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

    proxy_request_buffering off;

    proxy_connect_timeout  36000s;
    proxy_read_timeout  36000s;
    proxy_send_timeout  36000s;

    send_timeout  36000s;

    access_log      /var/log/nginx/seafhttp.access.log seafileformat;
    error_log       /var/log/nginx/seafhttp.error.log;
}

location /media {
    root /home/user/seafile/seafile-server-latest/seahub;
}

Any help to resolve or at least investigate the problem?
thank you in advance :slight_smile:
Giuseppe

Did you find a solution? I have a comparable setup (Ubuntu 16, Nginx, Upgrade from 6.3.4 to 7.0.5) and I’m hesitant to start the upgrade now.

Actually yes, some days ago.
The problem however was not related to 7.0.4 version itself: somehow when updating the seafile-server-latest symbolic link was not correct and as a result it was not running the new scripts. After fixing the link, it worked fine again.