# Am I misunderstanding ssl.termination and the discovery endpoint?

**URL:** <https://forum.collaboraonline.com/t/am-i-misunderstanding-ssl-termination-and-the-discovery-endpoint/3970>\
**Category:** Installation & Configuration\
**Created:** [August 23, 2025, 6:37pm UTC](https://forum.collaboraonline.com/t/am-i-misunderstanding-ssl-termination-and-the-discovery-endpoint/3970 "2025-08-23T18:37:03Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![darshan](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.collaboraonline.com/darshan/32/2230_2.png) [@darshan](https://forum.collaboraonline.com/u/darshan)\
**Post date:** [September 2, 2025, 1:50pm UTC](https://forum.collaboraonline.com/t/am-i-misunderstanding-ssl-termination-and-the-discovery-endpoint/3970/4 "2025-09-02T13:50:21Z")

</div>

- `ssl.enable=true` → CODE does TLS itself → discovery shows `https://`.
- `ssl.enable=false --o:ssl.termination=true` → TLS expected at proxy → CODE trusts `X-Forwarded-Proto`.
- If `X-Forwarded-Proto: https` is missing, discovery shows `http://`.
- Use-case for plain `http://`: internal/no-TLS setups where Nextcloud also talks HTTP.
- `server_name` overrides host; there’s no equivalent for scheme — protocol override relies only on `X-Forwarded-Proto`.

I am not expert on caddy config’s

I’m not too sure about the Caddy side of things you might find a working example in their docs or by asking in their public channel. From what I can tell, the issue looks more like a Caddy configuration problem than a Collabora one.

---

_[View the full topic](https://forum.collaboraonline.com/t/am-i-misunderstanding-ssl-termination-and-the-discovery-endpoint/3970)._