This is unfortunately is a feature of NextCloud because NextCloud supports basic auth at some level and the general basic auth headers are interfering.

We may be able to force nginx to remove auth headers in the location directive; however this will essentially break NextCloud's basic auth implementation. I can't guarantee there's a real fix here, as a potential fix could potentially inconvenience another user.

A workaround could be to have a subdomain and use that subdomain only for accessing NextCloud as basic auth credentials are cached at the domain level in browsers.

@liaralabs

This is what I assumed - it's a shame it's not an easy fix.

Is it possible to have NextCloud setup as normal (with it accessible through the swizzin web dashboard) on a seperate domain? What configs do I change to make this happen (so that the NextCloud link on the dashboard directs to the new subdomain)

In terms of forcing nginx to remove the headers - could this be something optional during install? I don't even see how you'd enable basic auth in NextCloud so I'd bet it's a real edge-case that someone wouldn't want this functionality.

I recently tried to set up Nextcloud on my swizzin install and I was pulling my hair out trying to debug what was going on, glad someone did and I can stop going crazy.

Hi I have the same problem there. Is there any workaround to fix this ?