I’m trying to implement the selected solution here in Nginx Proxy Manager gui. Can someone help?
I tried this but doesn’t seem to be correct:
Add a custom location of /seafdav, with the ip pointing to the address and port of the regular seafile server (or do you use the webdav port?).
Thank you for showing a picture of NPM. I’ve been scouring the web trying to find pictures ofhow to use the location with the advanced configs. I’m essentially using the instructions in the seafile documentations.
Now, webdav works for the most part. But I get 502 errors with certain things like swift backup on android, so same issue as you. I don’t understand the point of the local port and the drive thing, but I tried that and it also worked except for the 502. Now I will try the if statement you’ve added.
I cannot get mcking’s config to work for me. In the “solution” post, my question is what does "outside the server context’ mean for nginx proxy manager? I have no idea where to place that code. I know understand how the location setting works and I have that working I feel. But those two lines for outside the server i have no idea what to do with. And can anyone from seafile explain or instruct?
I never had cache assets enabled. I tried enabled and disabled, still get the 502 error.
So far, the only thing I have added to my config as far as advanced stuff is the location block from the official documentation. So nobody has gotten this to work with Nginx Proxy Manager?
It mentions all these files you can add to further tweak nginx. So which is outside server block? I used the one called http_top.conf
I just pasted the relevant stuff in there, and it worked!!!
So there you go. That’s how you do a complex advanced config with NPM gui.
Now, this was running on docker, so i had to do an apt update and install nano, and then create the custom folder and the file named above first, before editing the file.
As for what I pasted, I just used the stuff in the marked solution, exactly the way it is.
After upgrading to Seafile Community 10, simply removing all non-standard configuration (including the “Destionation” fix) fixed all issues I had with SeafDav.
oh great! thanks for this hint. Would have been awesome if the documentation contained this hint. I didn’t read the thread until the end and started adding all the header stuff just to read that it’s not needed anymore.
Can confirm it’s working with SeaFile 10 without the destination workaround. I have just created a pull request for the documentation as well.