Hi Dear Nextcloud community,
I’ve been experiencing an issue (as many others) where documents don’t open for users who aren’t connected via tunnel:
"Failed to read document from storage, please try to load the document again.".
This problem appeared suddenly today after updating the containers yesterday. One of my colleagues created a document, worked on it for a while, and was then unexpectedly locked out of it (and most other documents as well). Between updating and her first creating the doc were at least 12 hours and it worked for here a few yours.
I’ve read through the documentation, but for a setup that’s marketed as “all-in-one,” there seems to be a lot of manual configuration necessary for what I consider a basic use case.
My current setup is simple:
-
Domain/DNS points to our server
-
Using Caddy as reverse proxy with Docker Compose
Here are my configuration files:
Caddyfile:
https://cloud.example.com:443 {
header Strict-Transport-Security max-age=31536000;
reverse_proxy localhost:11000
}
compose.yml:
services:
nextcloud:
container_name: nextcloud-aio-mastercontainer
image: nextcloud/all-in-one:latest
restart: always
ports:
- "8080:8080"
environment:
- APACHE_IP_BINDING=127.0.0.1
volumes:
- nextcloud_aio_mastercontainer:/mnt/docker-aio-config
- /var/run/docker.sock:/var/run/docker.sock:ro
depends_on:
- caddy
caddy:
container_name: caddy
image: caddy:2
restart: always
network_mode: "host"
volumes:
- ./Caddyfile:/etc/caddy/Caddyfile
- caddy_data:/data
- caddy_config:/config
volumes:
nextcloud_aio_mastercontainer:
name: nextcloud_aio_mastercontainer
caddy_data:
caddy_config:
I believe the Nextcloud project would benefit from a collection of tested, working configuration examples. I’d be happy to contribute to development/documentation efforts if I can help improve this aspect.
Many thanks in advance for any help! <3