PKIX path building failed unable to find valid certifcate pathto requested target in a Graylog running on POD

[gsmith]

Hello,

@Nitin

unfortunately i tried everything and now running out of ideas

Showing us what you did would be helpful. This way we are not telling you something you have done already. It will also show us any incorrect configuration/commands you have done and maybe we can correct it.
The error tells use Graylog cant find the certificates (unable to find valid certificate path) but the question is how to configure environment to so solve this. Unfortunately, I unfamiliar with Docker/Pods for commands to solve this.

By chance Is your GRAYLOG_HTTP_TLS_* key/cert on that path you have configured available INSIDE the container?

What I’m not seeing is this part of your Graylog configuration.

volumes:
- ./certs/graylog-key.pem:/etc/docker/certs/graylog-key.pem
- ./certs/graylog-cert.pem:/etc/docker/certs/graylog-cert.pem
environment:
- GRAYLOG_HTTP_TLS_CERT_FILE=/etc/docker/certs/graylog-cert.pem
- GRAYLOG_HTTP_TLS_KEY_FILE=/etc/docker/certs/graylog-key.pem

Maybe something in these posts might help.

Configuring HTTPS with a docker container

Thank you for pointing me out in the right direction. My mistake was to take for granted a working configuration made by someone else and even reading the web interface doc did not help me to understand the web_endpoint_uri problem. Removing this variable made it works now. Here is the final working configuration. graylog: image: graylog2/server:latest container_name: graylog hostname: graylog environment: GRAYLOG_IS_MASTER: "true" GRAYLOG_PASSWORD_SECRET: somepasswordpepper:) GRAYLO…

Graylog init pod not completing (Kubernetes Helm Chart)

No worries, it feels like there’s a very specific fault happening. The .snapshot directory it complains about when trying to run chown -R 1100:1100 ... already is owned by 1100:1100 as far as I can see, but for some reason the .snapshot directory complains as it for some reason seems to be set to Read Only… I don’t understand why the .snapshot directory is even there, since afaik it should be and empty volume. I am running an nfs storage for my cluster, where .snapshots seem to be made on a ro…

I’m sorry I cant be more help to give you a direct answer on what to do. I know this error really well on other type of installation and it a very easy fix. Since your using a Pod I’m unsure how you need to proceed. Maybe someone here has a better understand with your environment. Also I am curious on how you fix this so keep us update if you do.