After update to 0.4.0 no access to web file manager, only "Invalid URL"

[poVoq]

I was running a fully working main branch pull from early june or so (0.3.11/12) and just updated to 0.4.0, but the internal web file manager became inaccessible.

I can log in fine and manage users etc., but when I click on the "Manage my files" button, I just get a white page with "Invalid URL" written on it.

Webdav clients also stopped working.

I checked the usual suspects, and log files, but I don't really see what could be causing this. The changelog also doesn't mention any breaking config changes that I might have missed.

Any idea what might be causing this?

Edit: Debug logs say: DAV: <= /files/{myusername}/ is not a managed URL

[vmasseron]

Same with clean install

[bohwaz]

Maybe try to set WWW_URL in config.local.php?

This message means that the router cannot correctly detect the requested URL.

[poVoq]

I always had that set and didn't change it when upgrading.

I suspect some recent change does something different with the routing and this breaks the nginx config that I shared some months ago.

Any idea what it could be?

[vmasseron]

Same, WWW_URL is set.

[bohwaz]

Thanks, I'll take a look when I get back from holidays, in 2 weeks. Keep on 0.3 in the meantime :)

[ghost]

bump! I also have this error with clean install. Nextcloud client also not working

[bohwaz]

Thank you all, this should be fixed in 0.4.1 :)

[ghost]

Updated to 1.40.1 and get timeout then go to /files/demo

In nextcloud app it freeze on testing connection

[bohwaz]

This is weird, what does curl -v http://10.10.10.147/ return?

[ghost]

I'm missed ip, seems work but nextcloud writes server not found

[poVoq]

Nextcloud needs additional .well-known end-points configured in the reverse-proxy, otherwise it will not work.

I am still looking into how to configure that best with Nginx.

[ghost]

Can you specify configuration? Can't find this in KaraDAV docs

[bohwaz]

It works for me without .well-known, but please provide info if NextCloud client requires it (and please report which Nextcloud client version requires it).

[poVoq]

https://docs.nextcloud.com/server/latest/admin_manual/issues/general_troubleshooting.html#service-discovery-label

But as I said, I still need to look into this a bit more. I think it needs to be set manually when you reverse-proxy KaraDAV.

[bohwaz]

I don't think that is related, KaraDAV doesn't do CardDAV/CalDAV, nor does the NextCloud app.

[poVoq]

Ah right sorry, was probably the wrong link. But there is definitly something that prevents the Android app to recognize my Karadav server, while normal WebDAV used to work fine.

But unrelated to this: Can you please re-open this issue? The web -based filemanager works fine after updating to 0.4.1, but the webdav access via (non-nextcloud) apps is still not working. It returns a 500 error.

Edit: hmmm, very odd. Oryzly does connect via webdav, but creates directories instead of the orgmode files, and then complaints that it can't sync because the file is a directory (409 error).

Edit: the same happens when I try to manually create text files via the web file manager. It gives an 500 error and when I refresh the page a directory has been created with the name of the text file that I tried to create.