Member since
06-15-2020
1
Post
0
Kudos Received
0
Solutions
06-15-2020
01:27 AM
I'm getting the same issue. As you said, I think it might be coming from Nginx server. This is what I get in the response of cUrl request: Andreas-MBP:etc aarrotta$ curl -iLv -u "admin:admin" -H "X-Requested-By: ambari" -X GET http://sandbox-hdp.hortonworks.com:8080/api/v1/check Note: Unnecessary use of -X or --request, GET is already inferred. * Trying ::1... * TCP_NODELAY set * Connected to sandbox-hdp.hortonworks.com (::1) port 8080 (#0) * Server auth using Basic with user 'admin' > GET /api/v1/check HTTP/1.1 > Host: sandbox-hdp.hortonworks.com:8080 > Authorization: Basic YWRtaW46YWRtaW4= > User-Agent: curl/7.64.1 > Accept: */* > X-Requested-By: ambari > < HTTP/1.1 502 Bad Gateway HTTP/1.1 502 Bad Gateway < Server: nginx/1.15.0 Server: nginx/1.15.0 < Date: Mon, 15 Jun 2020 08:23:06 GMT Date: Mon, 15 Jun 2020 08:23:06 GMT < Content-Type: text/html Content-Type: text/html < Content-Length: 173 Content-Length: 173 < Connection: keep-alive Connection: keep-alive < <html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.15.0</center> </body> </html> * Connection #0 to host sandbox-hdp.hortonworks.com left intact * Closing connection 0
... View more