Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error 502 Bad Gateway #265

Open
schpvs92 opened this issue Sep 30, 2024 · 5 comments
Open

Error 502 Bad Gateway #265

schpvs92 opened this issue Sep 30, 2024 · 5 comments

Comments

@schpvs92
Copy link

Hey guys,

i got the following issue:
using Grafana v11.2.0 (c57667e448)
grafana-checkmk-datasource 3.3.0
and
checkmk RAW 2.2.0p9

Im getting the error 502 Bad Gateway when im trying to test the grafana-checkmk-datasource connection to my checkmk instance.
The Firewall isnt blocking, grafana is running in a docker.

Does anyone have any idea what might be the issue?

@BenediktSeidl
Copy link
Contributor

Can you check if you can reach your Checkmk instance from inside the Grafana docker container?
The 502 Bad Gateway should be visible in your Grafana logs. What error message do they show exactly?

@schpvs92
Copy link
Author

@BenediktSeidl hey. thanks for the fast answer.

Pinging from docker works fine. Im also able to see the requests in our firewall.
Actually by using
docker logs grafana i found the following error:
level=error msg="Proxy request failed" err="tls: failed to verify certificate: x509: cannot validate certificate for "IP of our checkmk server" because it doesn't contain any IP SANs"

@BenediktSeidl
Copy link
Contributor

So you are using a self-signed certificate, but Grafana or the docker container does not trust the CA? Or something similar?

@schpvs92
Copy link
Author

schpvs92 commented Oct 4, 2024

Yes, it seems like grafana is not trusting the CA. To check that, is it possible to disable that security mechanism?

@BenediktSeidl
Copy link
Contributor

I don't know, this is independent of the checkmk data source, we just use the Grafana API for this.

But you can use something like https://mitmproxy.org/ and use a http:// URL for the data source instead of a https:// one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants