Hello all!
How to configure DAVx5 for file access over webDAV?
When I use the Link given in the settings menu of the browser app the DAVx5 seems to connect to the cloud, but no files are displayed and it is not possible to copy files to this DAV folder. Can some one help me?
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services
deleted post since wrong
Didn’t know that DAVx5 provides WebDAV mounts.
So thanks for your question about this (new?) feature.
I run my own Nextcloud server and use the F-Droid version of DAVx5 because I do not want to use Murena cloud services to store my personal data and prefer to use original and up to date apps instead of Murena wrapper apps or OS integrations. Currently I use the Nextcloud app to access files on my Nextcloud server but I do not need backgroud synchronization and everything else that comes with it. So a lightweight WebDAV client in DAVx5 would suit my needs perfectly.
The configuration process and restrictions (compatible apps) is described in the DAVx5 manual quite well:
https://manual.davx5.com/webdav_mounts.html
If you want to access files on a Nextcloud server the WebDAV URL is built of the server’s base URL +
/remote.php/dav/files/USERNAME/
https://docs.nextcloud.com/server/latest/user_manual/en/files/access_webdav.html
If you want to access files on other WebDAV servers you might find client configuration details in the respective manual.
There’s no difference between the F-Droid and the Google Play version in terms of functionality.
@Sunpower link given in the browser app, I’m curious at what place it is offered, could you screenshot?
you’re explicitly not asking about webdav sync? that eDrive can do with the static folders.
As to just webdav mounting, /e/OS can do that out of the box, accountmanager is mostly a davx5 (
) fork:
Settings → Accounts → murena / nextcloud account → My Account overview → Settings, Additional settings for account → sidebar, Tools, Webdav mount → (+)
enter address, as in:
https://murena.io/remote.php/dav/files/username@murena.io/
and username@murena.io again + password
(It then shows up in the Files App sidebar.)
Maybe the mount option should be made more obvious or automatically set up to address those users that struggle with the static folder sync in eDrive.
Thank you all!
With the built in webDAV client there is no problem on A14. But the DAVx5 I didn’t get to work with murena cloud files. In former times I used it with another webDAV provider and it worked.
I have another mobile with /e/OS A12. There the Account shows no calendar. I hope it will be upgraded to A15 soon and then the calendar sync will work again.
One thing I want to add:
When using the built in webDAV client it happens that it syncs all contacts to the cloud without asking. Fortunately, in wise foresight, I tested the procedure on a user space without contacts. Then I had a look at the app settings of the account manager which asks for the pass word for the webDAV account and found all permissions granted. I revoked the permission for my contacts. Then with creating the new account no contacts were synced. The behavior I wanted to have. After the account was installed it was possible to deselect contact syncing.
Thank you for your answer!
Can you please edit the https adress and take the @murena.io away?
Thank you!
You asked for a screenshot of the browser app with the link for webDAV access. I highlighted the button in yellow.
I see, thanks! the screenshot (or rather when I opened that dialog) will offer it url encoded with %40 instead of @ - that is an issue - you’d need to name the full address with @ and domain for the murena instance. On other nextcloud instances, the sole username can suffice.
(the fork) AccountManager will do some auto-auth-things, CalDav and Mail even. Bugs too… but it can make sense from a least-friction-onboarding perspective?
If this is OG bitfire @rfc2822, us users owe you to have built davx.
Thank you for clarifying the username. Maybe this was my problem. I can’t tell you, because I tried so many variations of username and URL (without documenting), but I think I did not write an @ into the URL.
But I’m wondering that the given URL without @ works well in Ubuntu file manager.
ubuntu file manager… that is due to the url schema.
You provide the username in front of the host part, so
davs://username%40murena.io@murena.io/remote.php/webdav (for GNOME / gvfs) is proper. Without that encoded @ symbol the host-part would falter to something invalid.
That too does work in that inputfield (with https:// as protocol in front)
With the built in webDAV app I get only read access to the folders. What should I do for write access?
we’re still in the “webdav mount” scope?
You won’t have an issue copying files (writing) to the webdav mount within (a) Files app. If you use an App that writes directly, apparently it can’t use more advanced filemodes (I’m not sure if that is up to each SAF backend, SAF itself or the App needing to use a newer file writing API to support SAF).
As to the modes - for the webdav mount, that’s “rw” and apparently not “rwt” (t as in truncate, more here).
I cycled through a few of opensource editors and half of them would write directly to the mount. I could dig in and look how they write out files. rcx, an rclone App, described this a few years ago. I’m not that familiar with SAF if this still applies.
The linked post describes exactly my issue. The written files have 0 B.
Meanwhile I tried writing a file from another app and it worked correctly. The file was written to the webDAV folder.
Another test I did was copying a file from one murenacloud folder to another folder in the same account and it worked, too.
The problem arises when I copy or move a local file with the Files app to the webDAV.
0 bytes, that is failing chunked uploads on nginx/php-fpm setups (which is what murena runs too). Apache apparently got a fix:
will look into docs
But what does that mean for /e/OS? How can I copy files from the phone to the Cloud?
if you want to do selective upload, roundsync works - it can create “sync tasks” too to do both: syncing and selective upload.
It works because roundsync asks for the permission to manage all files and doesn’t go through a SAF mount (the latter, as I surmise, doesn’t give the library doing the file upload the file size, thus needing chunked uploads, thus failing at the fcgi part of nginx-fastcgi-php that powers most nextclouds, it won’t accept content-lenth: 0 - apaches can).
