I'm using Grafana with Prometheus as DataSource. Those environments are behind a proxy, the communication was already open and I can test Telegram notification with success, but testing an alert in a dashboard I get the following error:
"tsdb.HandleRequest() error client_error: client error: 407"
Any ideia why is this happening?
HTTP 407 status code = Proxy Authentication Required, so it looks like your proxy doesn't like that request for some reason. I guess you can check proxy logs to see more details.
Related
I have set up a API gateway in AWS, and when I am able to call it from an application running in my laptop without any issue. However, it's giving me 403 forbidden error when I deploy the app in ECS on Fargate and call the same URL of API gateway.
I've confirmed the API gateway has been deployed and I am passing the stage name correctly.
This is the error message I am getting with 403 HTTP status code.
header([Server:"Server", Content-Type:"application/json", Content-Length:"24", Connection:"keep-alive", x-amzn-RequestId:"7e198xx8-5386-4xx7-axxf-a38cf78618b7", x-amzn-ErrorType:"ForbiddenException", x-amz-apigw-id:"cWxx5GSWXXcFuVg="])
{
"message": "Forbidden"
}
And I am using this base endpoint URL
https://{api-id}.execute-api.(region-id}.amazonaws.com/{stage}
I have tried with various endpoint types (Regional, Edge, Private), but none of them were successful. I might have used wrong URL though.
Do you have any idea what could be wrong in this case?
I am trying to perform a test against an endpoint with 1 thread. I configured a HTTP request with JSON Monk endpoint URL using JMEter.
But when I run the test I get Response code:504 in the Sampler result. The same when I use the URL in a browser I get also 504 Gateway Time-out
Can anyone help me with this issue? - I tried in another pc and I got the same error!
I have installed JMeter correctly and my code is correct too. I am working on a Windows 10.
HTTP Request:
As per HTTP Status Code 504 description
The HyperText Transfer Protocol (HTTP) 504 Gateway Timeout server error response code indicates that the server, while acting as a gateway or proxy, did not get a response in time from the upstream server that it needed in order to complete the request.
Note: A Gateway might refer to different things in networking and a 504 error is usually not something you can fix, but requires a fix by the web server or the proxies you are trying to get access through.
So it indicates the problem with the server you're trying to test, if you own the website - go and fix it, if you know someone who is responsible for it - inform him/her/them.
There is nothing you can do from JMeter perspective. If you know how response should look like you can use a Dummy Sampler to return this response so you could play with the response data
By the way, it's down for me as well:
I am trying to test a Spring Boot project using HTTP Client of IDEA to send a GET request, but it return "500 Internal Server Error":
But under the same conditions, it is no problem to send by browser:
There's no problem using postman:
But using postwoman will cause a CORS problem. By default, postwoman run on port 3000, so I add #CrossOrigin(value = "http://localhost:3000") on the controller class. After that, there was no problem with the test:
At the same time, there is no problem sending GET request using VSCode's REST Client plug-in:
The controller class code is as follows:
It's confirmed that it's not a firewall problem, so is this a bug of HTTP Client?
Or does the HTTP client need to set some configuration?
It's a proxy problem. It is HTTP proxy set in IDEA. 500 is returned by the proxy server.
while during load testing for one site through j meter getting below
error:Response code: Non HTTP response code:
org.apache.http.conn.ConnectTimeoutException Response message: Non
HTTP response message: Connect to 172.17.4.213:80 timed out
You most probably didn't configure the proxy for JMeter as per:
http://jmeter.apache.org/usermanual/get-started.html#proxy_server
Look at your browser (where request works) proxy configuration for the settings.
I think you should check your URL/ip address is pointing to your code properly by some online ping tool. And If it is working, check if your network is not blocking site access.
I am trying to subscribe to datastream updates via the xively-js javascript library.
However, all I am getting is a 503 error right after creating the websocket:
WebSocket connection to 'ws://api.xively.com:8080/' failed: Unexpected response code: 503
The same error is produced by the xively-js sample-app at
http://xively.github.io/xively-js/sample-app/
Both IE10 and Chrome give the same result.
I can't seem to find any working xively websocket sample. Does somebody have any?
I have found the answer to my own question. It looks like non-secure websockets don't work for some reason.
The secure version wss://api.xively.com:8094 is working fine.