Startup failed

[sw-fox]

I have done exactly what is described here in the documentation, but at startup I see this fatal error in the logs which prevent the server from running.

opencloud-1  | {"level":"fatal","service":"proxy","error":"read /etc/opencloud/csp.yaml: is a directory","time":"2025-12-22T15:08:07Z","line":"github.com/opencloud-eu/opencloud/services/proxy/pkg/command/server.go:331","message":"Failed to load CSP configuration."}

I have discovered that opencloud/csp.yaml is a directory instead of a file.

Can you help me with this issue and fix the defaults in the config or document this so that others may not have this error?

[micbar]

This error seems specific to your setup. I cannot reproduce that on docker for Linux and docker for Mac.

[Willyisback]

I have the same problem :/ hope someone can help us.

[kezmdor]

I can confirm this is an issue. The files csp.yaml and banned-password-list.txt are folders instead of files. They also belong to root, not to uid 1000.

[micbar]

I have seen this happening when volumes change and docker compose down was not executed. Please check. We are continuously deploying that setup. It runs on demo.opencloud.eu

they also belong to root, not to uid 1000.

That is a docker issue. Every file mounted via volume mount in docker is per default owned by root.

[kevinpease]

This issues pointed me in the correct direction to fix my error, there was a very restrictive default umask set on my system so the config files and this csp file were being created with only the user having r/w access to them. I initially didn't think that should be the problem so I modified the ACLs on the config directory to force R/W for everyone and the error on that file below went away. Not sure if something permissions related is your issue as well.

[opencloud] | {"level":"fatal","service":"proxy","error":"open /etc/opencloud/csp.yaml: permission denied","time":"2025-12-24T01:23:25Z","line":"github.com/opencloud-eu/opencloud/services/proxy/pkg/command/server.go:331","message":"Failed to load CSP configuration."}

[kezmdor]

I've put some time into this and on my side the issue is raised by the combination with portainer. This stack cannot be deployed using portainer.

[micbar]

@sw-fox Is your original issue fixed?

There a some comments about related topics but the main topic is unclear.

Like i said, we cannot reproduce this problem.

Portainer is also not a problem.

Most things are just boiling down to permissions problems, which are mostly custom issues and cannot be generalized.