Support intro
Sorry to hear you’re facing problems. 
The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.
If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.
Getting help
In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.
Before clicking submit: Please check if your query is already addressed via the following resources:
- Official documentation (searchable and regularly updated)
- How to topics and FAQs
- Forum search
(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).
Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. 
The Basics
- Nextcloud Server version (e.g., 29.x.x):
32.0.1
- Operating system and version (e.g., Ubuntu 24.04):
Ubuntu 24.04
- Web server and version (e.g, Apache 2.4.25):
Apache2
- Reverse proxy and version _(e.g. nginx 1.27.2)
Caddy
- PHP version (e.g, 8.3):
8.4
- Is this the first time you’ve seen this error? (Yes / No):
yes
- When did this problem seem to first start?
immediately
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
bare metal
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
noSummary of the issue you are facing:
This is driving me crazy!
I have a Nextcloud install behind a Caddy server running a reverse Proxy. Here is the relevant block:
int-nc.xxxxxxxxx.com {
@denied not client_ip x.y.z.w/16
abort @denied
reverse_proxy 10.1.10.251:80 {
header_up Host {http.reverse_proxy.upstream.hostport}
header_up X-Forwarded-Host {host}
}
#Handle WebDAV redirects for CardDAV and CalDAV
redir /.well-known/carddav /remote.php/dav 301
redir /.well-known/caldav /remote.php/dav 301
header {
Strict-Transport-Security max-age=15552000;
}
}
I am trying to map a drive using Webdav in Windows 11. It will sometimes work after a lot of tweaking. But almost always (and for sure after a reboot) I get an error that the network name cannot be found.
Is there something I can do to fix this? I don’t want this server open to the internet as I am using it as a internal share resource and our data is very sensitive. Caddy gives me the ability to keep certs up to date, but block anything that isn’t coming in over our VPN.