WebDAV

Does it work if you run: sudo systemctl restart nginx

Zitat von fredu

Am I configuring it correctly?

No idea. I don't use whatever app that is. I always test in a browser. http or https is determined by the OMV web interface. If you access OMV via http, then webdav will be http. Same for https. Do you have OMV on a non-standard port?

I have installed the plugin. I have set up a shared folder and enabled the webdav-users group.

For the connection to work I restarted the server (windows style, sorry ), before that it didn't work. I guess the plugin should restart the nginx service after enabling the shared folder. The response before restarting was this:

Failed to connect: The server returned the error code 405 (MethodNotAllowed), indicating that the server does not support WebDAV connections 

I'm not sure about this, I did a few things at once, but I think I also needed a reboot after adding a user to the webdav-users group for the connection to work. The response prior to this reboot was not a connection issue like the previous one, it had something to do with permissions. After the new reboot the connection was established.

Now I can read the folder but I can't write. Is this the expected behavior or is it some other permissions issue? Should you be able to write to that shared folder?

Zitat von chente

For the connection to work I restarted the server (windows style, sorry ), before that it didn't work. I guess the plugin should restart the nginx service after enabling the shared folder.

It is supposed to restart nginx. I will have to look at it again.

Zitat von chente

I'm not sure about this, I did a few things at once, but I think I also needed a reboot after adding a user to the webdav-users group for the connection to work. The response prior to this reboot was not a connection issue like the previous one, it had something to do with permissions. After the new reboot the connection was established.

I would curious if restarting nginx instead of a reboot fixed this.

Zitat von chente

Now I can read the folder but I can't write. Is this the expected behavior or is it some other permissions issue? Should you be able to write to that shared folder?

That is likely a permissions issue.

Zitat von ryecoaaron

I would curious if restarting nginx instead of a reboot fixed this.

ok, I'll try it and let you know.

Zitat von ryecoaaron

That is likely a permissions issue.

Any idea what to do?

The user is in the users and webdav-users groups. The user has write permissions on that shared folder and the webdav-users group does as well. I can't think of anything else to try.

OMV limits the use of the GUI to the admin user. Could that have something to do with it since webdav is using the same nginx as the OMV GUI?

Zitat von ryecoaaron

I would curious if restarting nginx instead of a reboot fixed this.

Yes, Restarting the service works but I still have read-only permissions for no apparent reason.

_________________________________________________________________________

new vm and webdav plugin installed. The GUI is on port 80 with http.

Shared folder created -> "backup"

User peter created.

- peter can write to the backup folder.

- peter belongs to the users and webdav-users groups.

The webdav-users group can write to the backup shared folder.

I enable the webdav service from the GUI by configuring the backup shared folder and the default webdav-users group.

I try to create a connection from a container on another IP on the local network and get this error:

Failed to connect: The server returned the error code 405 (MethodNotAllowed), indicating that the server does not support WebDAV connections

I check the status of the nginx service and it is correct. I restart the service.

systemctl restart nginx

The service is still active and without errors:

~# systemctl status nginx
● nginx.service - A high performance web server and a reverse proxy server
     Loaded: loaded (/lib/systemd/system/nginx.service; enabled; preset: enabled)
     Active: active (running) since Tue 2024-04-30 20:43:23 CEST; 59s ago
       Docs: man:nginx(8)
    Process: 13648 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
    Process: 13649 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
   Main PID: 13650 (nginx)
      Tasks: 3 (limit: 4632)
     Memory: 2.9M
        CPU: 17ms
     CGroup: /system.slice/nginx.service
             ├─13650 "nginx: master process /usr/sbin/nginx -g daemon on; master_process on;"
             ├─13651 "nginx: worker process"
             └─13652 "nginx: worker process"

abr 30 20:43:23 omv7limpio systemd[1]: Starting nginx.service - A high performance web server and a reverse proxy server...
abr 30 20:43:23 omv7limpio systemd[1]: Started nginx.service - A high performance web server and a reverse proxy server.

After restarting the nginx service the connection is established at http://192.168.10.118/webdav Message:

The connection worked!

I force the creation of a folder from the container. This is Duplicati. I'm just trying to connect to http://192.168.10.118/webdav/test. Duplicati informs me that this folder does not exist and asks me if I want to create it. This works for me with a webdav folder on a remote Nextcloud instance. I answer yes. Duplicati should create that folder but I get this error:

Failed to connect: The remote server returned an error: (403) Forbidden.

If I can help with anything else, tell me.