1. Caddy version (caddy version):
2.4
2. How I run Caddy:
a. System environment:
Manjaro Gnome clean install with docker compose
c. Service/unit/compose file:
version: "2.4"
services:
caddy:
container_name: web-proxy
image: lucaslorentz/caddy-docker-proxy:ci-alpine
restart: always
networks:
- web-proxy
environment:
- CADDY_INGRESS_NETWORKS=web-proxy
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- $DOCKERDIR/caddy/caddy_data:/data
- $DOCKERDIR/caddy/config:/config
labels:
caddy.email: $EMAIL
ports:
- 443:443
#
onlyoffice:
container_name: onlyoffice
image: onlyoffice/documentserver
stdin_open: true
restart: always
networks:
- web-proxy
tty: true
volumes:
- $DOCKERDIR/onlyoffice/data:/var/www/onlyoffice/Data
- $DOCKERDIR/onlyoffice/log:/var/log/onlyoffice
- $DOCKERDIR/onlyoffice/database:/var/lib/postgresql
- /usr/share/fonts:/usr/share/fonts
environment:
JWT_ENABLED: true
JWT_SECRET: $ONLYOFFICEJWT
labels:
caddy: office.$DOMAIN
caddy.reverse_proxy: "{{upstreams 80}}"
# Required extra headers
caddy.file_server: ""
caddy.encode: gzip
networks:
web-proxy:
#driver: bridge
external: true
3. The problem I’m having:
The above compose worked fine last year. I reinstalled my server, ran the same compose file again and now the page is blank. When I use dev options in Firefox, I do see something about 502 error, but there is no 502 error page.
4. Error messages and/or full log output:
see next post (too many characters).
Note there are 3 other containers for which I use caddy (Firefox, Vault, Files), those will be shown in the log as well. Firefox is Firefox Sync server, Vault is Vaultwarden (bitwarden) and Files is FileRun.
5. What I already tried:
This forum and github issues is filled with my posts of the past 3 years playing with Caddy to get OnlyOffice playing nicely with Docker. I finally had it working last year. Not sure what changed now. I am hoping there are others in the community that use Caddy with OnlyOffice successfully.
: