latest image causes bad request

[hasufell]

contradictory scheme handlers

Doesn't happen with 6.2.5.

[shoeper]

I cannot reproduce the issue.

[falkzilm]

I have the same problem and trying to solve this.
I think it has something to do with proxy settings and seafile docker settings, in my env i have a nginx proxy which delegates requests to docker images and maintain letsencrypt certs.

I configured it to use always HTTPS for the outside so if i open the page in browser it will always be https. But internaly he delegates maybe with HTTP and i think this causes with HTTP/2.0 some problems - i am trying to find a way to solve this out..

/EDIT
I couldnt figure it out properly so i rolled back to version 6.2.5

[hutweb]

same problem here with the same configuration as falkzilm (seafile behind nginx-proxy)

[shoeper]

Have you checked the logs?
Execute bash within the container and check /var/log/nginx/* and /opt/seafile/logs/*

[hutweb]

I've checked both directories and no trace of the problem.

So far my solution is to comment "proxy_set_header X-Forwarded-Proto $scheme;" out in /templates/seafile.nginx.conf.template

[shoeper]

So the issue is obvious.

Your proxy sets X-Forwarded-Proto https and the nginx proxy within the image sets another one to X-Forwarded-Proto http. Now you the two are contradictory.

[hasufell]

@shoeper The issue may be obvious, but not the proper solution. It appears this image doesn't give any control over the internal nginx configuration and doesn't account for the most common setup which is people running jwilder/nginx-proxy.

[mplorentz]

I am having the same issue, same setup. @yopbot's workaround fixes the issue for me. I'm happy to attempt a PR if we know what the fix should be.

[crystalnet]

+1
just ran into the same issue. a fix would be much appreciated 😃 👍 🙏

[realies]

it is still an issue

[orangelynx]

Also the bad request says "Contradictory scheme headers" (not handlers, at least for me, for people googling the issue).

In general the docker image leaves much to be desired, if anyone has an alternative option, I'd appreciate a pointer.

[windsource]

I use sunx/seafile with SQLite and an external nginx proxy. That works quite OK.

[melyux]

Still no solution to this? Perhaps the nginx process should be further stripped away from the Seafile like the database and memcached.

Even after patching the template file, I get "Page unavailable due to a server hiccup".