-
Notifications
You must be signed in to change notification settings - Fork 66
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
JSON API: Cannot connect to API #242
Comments
Hello I am having the same error with Grafana version: 8.4 ========The log file======== logger=auth t=2022-03-04T22:49:38.29+0000 lvl=dbug msg="seen token" tokenId=47 userId=1 clientIP=10.60.18.131 userAgent="Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.99 Safari/537.36" authToken=dae460db2fac9f6552925d852bc5dc6c106aa6de01a926d3df42ccb35f89a37e ============================ |
Hello Checking if there are any updates on this request |
Sorry can you clarify, what does these term status really mean -- "Kind/support Priority/awaiting-more-evidence" |
@neerajnagpal0408 It basically means I need to reproduce this myself to be able to set better status labels. Is there any URL that I can use to replicate this behavior? Sounds like something is blocking Grafana from accessing the URL. Do you have any VPNs or firewalls set up? |
Thanks! I found out that this was was a warning only, the plug-in did work fine with the dashboard, despite this warning. |
What happened:
Json API not working and showing an error "JSON API: Cannot connect to API"
What you expected to happen:
I am trying to pull the API data directly through https://XXXX but not providing the data.
If I execute through cURL, it shows the data.
How to reproduce it (as minimally and precisely as possible):
Create a new data source JSON API and hit the Save and Test button.
Anything else we need to know?:
I am executing the curl command directly through the Grafana Linux server. There is no proxy involved between Grafana and Oracle EOM which I am trying to access the data.
Error logs:
Environment:
The text was updated successfully, but these errors were encountered: