-
Notifications
You must be signed in to change notification settings - Fork 288
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
Unable to connect to grafana oncall from external grafana #1035
Comments
Hi! Thank you for the report. Could you please provide logs from engine and celery worker? |
i have the the same error |
Thanks for the reply , We cannot find any logs related to the above issue in engine or celery worker. " logger=context traceID=00000000000000000000000000000000 userId=4 orgId=5 uname=user@example.com t=2022-12-22T12:25:48.095309245Z level=info msg="Request Completed" method=POST path=/api/plugin-proxy/grafana-oncall-app/api/internal/v1/plugin/self-hosted/install status=404 remote_addr=10.10.x.x time_ms=5 duration=5.555156ms size=24 referer=https://grafana.example.com/plugins/grafana-oncall-app traceID=00000000000000000000000000000000" Curl request from the same grafana machine to engine:8080 is giving a response "OK" |
I got same issue. Can't connect oncall with external grafana, details: https://grafana.slack.com/archives/C02LSUUSE2G/p1672041357673719 |
Use grafana and grafana oncall from docker-compose file also didn't work for me, I got these error from grafana (I tried input localhost:8080, http://localhost:8080 when start plugin):
and these from celery:
|
I have the same error with production EKS setup. After installing and configuring the addon I get the following error message in Grafana after the Sync: The only log message that gets printed out is the following:
|
I was able to fix this with GRAFANA_API_URL: http://host.docker.internal:3000 in docker-compose.yml and adding
to Celery container. |
Got the same error while connecting external grafana to oncall-engine which is installed using helm chart. However, if using provided grafana in the same helm chart, it works. |
Note that you can also get this if you input the OnCall API URL with a trailing slash. Hope this helps someone! When configured with "http://oncall.dev.example.com/":
Successful when configured with "http://oncall.dev.example.com":
|
It worked while running Grafana and Grafana OnCall using the Docker-compose file from this repository.But
Error shows up while connecting to oncall from other grafana sources.
" Error -An unknown error occured when trying to install the plugin. Are you sure that your OnCall API URL, http://xxx.xxx.xx:8080, is correct?
Refresh your page and try again, or try removing your plugin configuration and reconfiguring."
The text was updated successfully, but these errors were encountered: