Dav endpoints redirecting incorrectly about nextcloud-snap HOT 4 OPEN

Hey, thanks for the quick response
I was thinking to hand off ssl to haproxy and do the redirecting there, but just wanted to report this since i couldnt find any isue about it with a quick search (apearantly not a good enaugh searcher). If im aware, the apache config is read only in the snap, would there be a way to have those port settings be available for apache as well somehow?
When i get my config i can add a PR to add it to the config on the guide with steps for ssl if needed to help out.

from nextcloud-snap.

Welcome @008kevin and thanks for your request

Haproxy is using a somewhat modified reccomended config, and is acting as pass through

maybe following Link helps https://stackoverflow.com/questions/71171414/haproxy-breaks-dav-well-known-redirects-in-nextcloud

see also issue #1042

@Pilzinsel64 could you assist please?

from nextcloud-snap.

@008kevin, yeah the apache config is read only. feel free to make a PR.

please close here when you're happy

from nextcloud-snap.

@008kevin, i've tried to understand what you're trying to do. not being familiar with haproxy i'd like to point you to config using NPM. I am aware that NPM is handling termination in this example and you're wanting to pass through the reverse proxy which is explained here.

its not clear though if your setup is configured to port444 or not. if so, why if you're wanting to pass through anyway?

also have you set overwritehost or overwriteprotocol because surely the snap would not redirect to port444 if it hasn't been told to?

possibly @kyrofa could assist since he has haproxy setup

from nextcloud-snap.