ocis: Unable to access files through WebDav

Describe the bug

Although I can access to the web interface, cannot access files through WebDav. Tested with Nautilus on Ubuntu 22.04 and cadaver CLI

$ cadaver https://10.44.66.22:9200
WARNING: Untrusted server certificate presented for `127.0.0.1':
Certificate was issued to hostname `127.0.0.1' rather than `10.44.66.22'
This connection could have been intercepted.
Issued to: Acme Corp
Issued by: Acme Corp
Certificate is valid from Sat, 25 Feb 2023 13:12:52 GMT to Sun, 25 Feb 2024 13:12:52 GMT
Do you wish to accept the certificate? (y/n) y
Could not access / (not WebDAV-enabled?):
405 Method Not Allowed
Connection to `10.44.66.22' closed.

I have also tried to access through Nautilus without success

Steps to reproduce

Install cadaver WebDav CLI. On Debian based OS apt install cadaver
Connect to Ocis Proxy over my LAN (https://10.44.66.22:9200)
I got an error ‘not WebDAV-enabled?’

Expected behavior

As an end user I expect to be able to access my files through WebDav. I would like to mount a directory with davfs2 and work as if the remote files were local.

I can see here this is easily done with classic OwnCloud. Is that possible as well for Ocis?

Setup

ocis.env

OCIS_URL=https://10.44.66.22:9200
OCIS_INSECURE=true
OCIS_CONFIG_DIR=/etc/ocis
OCIS_BASE_DATA_PATH=/var/lib/ocis

About this issue

Original URL
State: closed
Created a year ago
Comments: 40 (18 by maintainers)

Most upvoted comments

@Ke1i @kulmann @micbar finally i can access both “remote.php/webdav” and “dav/spaces/{space-id}”. the environment file provided by @Ke1i saves my days. thx!

Princelo on Jun 18, 2023

This is incredibly helpful, thank you! It would be even better to have the webDAV URLs provided in the OCIS web interface.

johnstonjs on Mar 4, 2023

I have been product owner of oc10 for some years, now for oCIS and i know Nextcloud. There seems to be a strong opinion in the oc10 or NC world that bare metal installations are “easier”.

Baremetal NC was never easy unless done via Snap route. Apache, php, redis, using a ‘proper’ database, imagemagick, optimizations, hardening etc. What I love about OCIS is the fact that I can get things running in less than ten (10) minutes with just a single binary. All I need to do is to create the ocis user, create some directories and copy over sample environment and systemd unit files. And I can’t stress enough about this one other thing, OCIS is way faster 😃 I like OCIS mostly because of this, speed and ease of deployment.

It is missing in the docs example. ocis.url/webdav/ works (needs a trailing slash). It is the same handler, just routing.

Good to know, it should be documented so folks wouldn’t need to keep guessing if it’s officially supported or not. it’s a lot cleaner and easier to remember IMHO. I hope it’ll be supported in the long run going forward.

Yes, very simple: Lookups by ID are much faster.

Maybe for machines, I’m just a simple self-hoster. But what do I know ¯_(ツ)_/¯ Anyway thanks for your input, much appreciated.

Ke1i on Sep 20, 2023

The webdav paths are available under https://10.44.66.22:9200/dav/spaces/<space-id>

To find them out, you need to either know the spaceID beforehand or do an authenticated (OpenIDConnect) request against https://10.44.66.22:9200/graph/v1.0/me/drives/ . This will return a JSON response with a list of all available spaces (drives). Each space has its own webDAV URL.

micbar on Feb 27, 2023