oc behind extermal proxy: mistake in documentation?

[rhafer]

Discussed in https://github.com/orgs/opencloud-eu/discussions/2875

^{Originally posted by DonJDelago June 2, 2026}
Hi,

I found something I'd like to tell you. Maybe something's wrong in the documentatoin (link below):

I set up oc with an external NPM. In the .env file it says: "COMPOSE_FILE= [...] external-proxy/opencloud.yml" - this exposes oc to the container only and thus does not work with an external NPM. Chaning it to "external-proxy/opencloud-exposed.yml" works. So, in my understanding the exposed.yml files should also be listed in the "external proxy"-documentation and in the .env file or am I missing something?

https://docs.opencloud.eu/docs/admin/getting-started/container/docker-compose/external-proxy

thank you!

[rhafer]

this exposes oc to the container only

This is not exactly true. It exposes the port on the host on which the container is running. So if your external proxy is running on the same host you won't need to include external-proxy/opencloud-exposed.yml.

and thus does not work with an external NPM. Chaning it to "external-proxy/opencloud-exposed.yml" works

Yeah, if the external Proxy in running on a different machine (or VM) you need to include that file. But only then (see e.g. opencloud-eu/opencloud-compose#160 for why it should not be done unconditionally).

So, in my understanding the exposed.yml files should also be listed in the "external proxy"-documentation and in the .env file or am I missing something?

This needs to be decided on a case-by-case basis. And IMO we need to add some hints to the documentation when including opencloud-exposed.yml is needed. So I'll transfer this discussion to an issue for the docs repo. Thanks for the heads up.