mirror of
https://github.com/Dokploy/templates.git
synced 2026-07-14 18:35:24 +02:00
448d4ba76d
The container was restart-looping because the built-in IdP fatals with "invalid iss value, URL must start with https://" when OCIS_URL uses plain http, which caused the sustained 502. - Set owncloud_url to https://${main_domain} so the IdP issuer is valid and ocis server stays up. - oCIS 8.x unconditionally answers 308 -> https:// whenever it receives X-Forwarded-Proto: http (services/proxy https_redirect middleware), so the domain check then died on a redirect loop into a non-existent 443 router. Add a small nginx gateway in front of oCIS that forwards requests with X-Forwarded-Proto: https (what a TLS-terminating proxy sends) and point the Dokploy domain at gateway:8080. - Update the README notes accordingly. Verified on a live Dokploy instance: deploy done, GET / returns HTTP 200 with title "ownCloud". Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
