bad gateway error when running this plugin in a local instance of grafana and where to change base url?
See original GitHub issueHi,
I’m playing with this with the end goal of being able to query a couple sprinklr api’s directly from grafana. I have the plugin loaded, but when I use it as a datasource for a dashboard, I get this:
Bad Gateway Object status:502 statusText:"Bad Gateway" data:Object error:"Bad Gateway" response:"" message:"Bad Gateway" config:Object url:"api/datasources/proxy/1" method:"GET" retry:0 headers:Object hideFromInspector:false message:"Bad Gateway"
Any tips on what to try to solve that?
Also, I’ve searched fairly extensively through the package files to determine where to change the base url, but am not finding it. Can you help with that?
Thanks!
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
bad gateway error when running this plugin in a local instance ...
Hi, I'm playing with this with the end goal of being able to query a couple sprinklr api's directly from grafana. I have...
Read more >Bad Gateway Errors - Configuration - Grafana Community
Just go into Add Datasource and select Influx and put in the details there. Then click the Test button at the bottom. If...
Read more >Trying to add Authentication for data source plugin leads to ...
In plugin.json I've added the following: "routes": [ { "path": ... to add Authentication for data source plugin leads to Bad Gateway Error....
Read more >Run Grafana behind a reverse proxy
In this tutorial, you'll configure Grafana to run behind a reverse proxy. When running Grafana behind a proxy, you need to configure the...
Read more >Grafana HTTP Error Bad Gateway and Templating init failed ...
Hi, I use docker installed Prometheus and Grafana at local. prometheus localhost:9090 => OK Grafana localhost:3000 => ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks again! I must have gotten mixed up somewhere but your explanation (and the screen shot) got me past this error.
I can imagine you’d get this if you left the data source config empty and only used the path in the query editor as well.