I just detected the UI doesn’t work any more with WSGI and spent some time to find the root cause why it deosn’t work any more.
If you flip between WSGI and FCGI mode on the server you have to clean your browser cache. That’s why I thought UI works with WSGI. When I switched from FCGI to WSGI the UI worked. When I cleared the browser cache it didn’t work any more
WSGI usage for seafdav works perfectly if you follow the doc and change nginx according the tutorial. It didn’t work because I screwed up the configs when switching between UI and seafdav WSGI/FCGI mode back and forth
So now my server still runs FCGI for UI and WSGI for seafdav using nginx port <> 80.
Then I changed my non standard nginx port to 80, configured WSGI for UI and everythings works fine (I also cleared the browser cache )
Actually it seems to be either a missing config statement or a coding issue because the redirection to the login page looses the port number. I’m not familiar with nginx but tried different config changes to make sure port is not lost but failed
Does somebody know what I have to change in the nginx config or should I open an issue for this?
@shoeper I frankly wasn’t aware this doc can/should be updated by the community. Regarding the seafdav and WSGI it’s missing the nginx changes mentioned in the tutorial. Looks like @res80 also didn’t know about this
@DerDanilo Thank you very much for the link. I’m going to provide feedback the next days via PM
Now I can use WGSI for UI and seafdav successfully
There are multiple places you have to update when you want to use a non standard port but unfortunately I forgot one. I checked the doc but I failed to find any description how to use a non standard port. I also didn’t find the update with $server_port in WSGI mode I don’t know nginx in detail but as far as I understand $server_port in host can be used all the time - whether port 80 or a non standard port ist used.
Thank you very much @all helping me to solve this ugly issue with WSGI.
Thanks for the hint to @framp and @shoeper, I really didn’t know that.
I started this tutorial actually as a question, then answered it myself by playing around with nginx and changed the title to tutorial afterwards, hoping that the devs would include it in the manual.