Member since
09-22-2023
1
Post
0
Kudos Received
0
Solutions
09-22-2023
09:08 AM
hey bro, I got the exact same response from entering the suggested command by @jsensharma, still cannot open Ambari. did you figure it out? Note: Unnecessary use of -X or --request, GET is already inferred.
* Trying 172.XX.184.YYY...
* TCP_NODELAY set
* Connected to 172.XX.184.YYY (172.XX.184.YYY) port 8080 (#0)
* Server auth using Basic with user 'maria_dev'
> GET /api/v1/check HTTP/1.1
> Host: 172.XX.184.YYY:8080
> Authorization: Basic bWFyaWFfZGV2Om1hcmlhX2Rldg==
> 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: Wed, 20 Sep 2023 16:00:20 GMT
Date: Wed, 20 Sep 2023 16:00:20 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 172.XX.184.YYY left intact
* Closing connection 0
... View more