Nextcloud connecting issue

Questions
1

Describe the problem/error/question

I’am facing the same issue like Can't connect to nextcloud but the former topic was closed without any resolution. Are there any news regarding connection issues with nextcloud webdav?

Btw. I saw in another thread

→ Don’t use /remote.php/dav/files — that endpoint won’t work for n8n

I’d like to ask why? It’s the proper way to do that: Accessing Nextcloud files using WebDAV — Nextcloud latest User Manual latest documentation

My provider for my managed Nextcloud gave me a webdav URL like this:
https://nc-123.nextcloud-ionos.com/remote.php/dav/files/userXYZ

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

Hey @Stefan_F,
Welcome to the community!

From what’s documented and what users have confirmed working with the n8n Nextcloud node, you should use the /remote.php/webdav/ endpoint and not /remote.php/dav/files/…

n8n’s Nextcloud credntials/docs consistently use https://your-domain/remote.php/webdav/ (If Nextcloud is on the root domain) and https://your-domain//remote.php/webdav/ (If Nextcloud is in a subdirectory)

So in your case, try this in the Nextcloud credentials WebDAV URL field: https://nc-123.nextcloud-ionos.com/remote.php/webdav/

Even though /remote.php/dav/files/… can work in genric WebDAV clients, the n8n Nextcloud node is built/tested around /remote.php/webdav/. So when people try the “dav/files” style path, they often hit “Bad request / check parameters” type errors simply because the node isn’t expecting that base URL.

If you’re running n8n in Docker and Nextcloud is self-hosted (or behind something that changes the host), another common cause is Nextcloud trusted domains. The fix is adding whatever host n8n uses (like host.docker.internal, container name, etc.) into Nextcloud’s trusted_domains.

3

I dropped IONOS and switched to Hetzner. Now I am paying half the price, and everything is working perfectly in n8n :slight_smile:

But my fix was to build Lamdbas in AWS which managed my IONOS Nextcloud. But that was a lot of hassle – I wouldn’t recommend it.

4

Danke @roNn23 I just switched over to wolkesicher and it works out of the box.