Seafile Pro 9.0.16 on CentOS 7.
2 weeks ago I enabled the new go fileserver on our seafile cluster. Everything seems to be running fine, until a user complained, that her share links don’t work anymore. When opening a link, the web browser throws the following error:
PDF.js Version 2.10.377 (build: 156762c48) Unexpected server response (400) while retrieving PDF "https://seafile.server/seafhttp/files/8b1d83c4...File.pdf"
I tried this with several browsers, but she was right. Because she was the only user complaining, I didn’t see the real cause of the problem. On one of the cluster servers I disabled the go fileserver and suddenly her links were working again, when using this single server. So in the end I disabled the go fileserver on all servers and the problem was gone.
Do you have any idea what could have caused the problem?