04-04-2024 11:10 AM
I am trying the following and get a 502 Bad Gateway response:
curl -k https://devnetsandboxiosxe.cisco.com:443/restconf/data/ietf-interfaces:interfaces/interface=GigabitEthernet1 -u admin:C1sco12345 --header 'Accept: application/yang-data+json'
<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx/1.13.12</center>
</body>
</html>
I know the router is up beacuse I can ssh into it and restconf seems to be enable.
Any ideas?
Thanks in advance
04-05-2024 03:03 AM
Look like the device is down right now?
ssh admin@devnetsandboxiosxe.cisco.com
kex_exchange_identification: Connection closed by remote host
Connection closed by 131.226.217.181 port 22
❯ echo "QUIT" | nc devnetsandboxiosxe.cisco.com 443
HTTP/1.1 400 Bad Request
Server: nginx/1.13.12
Date: Fri, 05 Apr 2024 10:01:05 GMT
Content-Type: text/html
Content-Length: 174
Connection: close
<html>
<head><title>400 Bad Request</title></head>
<body bgcolor="white">
<center><h1>400 Bad Request</h1></center>
<hr><center>nginx/1.13.12</center>
</body>
</html>
04-05-2024 07:48 AM
Thanks for your replay. Just try it now but same issue.
I can login to the router but get a 502 with Restconf:
---------------------------------------
The following programmability features are already enabled:
-NETCONF
-RESTCONF
Thanks for stopping by.
shut#
---------------------------------------
ROM: IOS-XE ROMMON
shut uptime is 2 days, 19 hours, 21 minutes
Uptime for this control processor is 2 days, 19 hours, 23 minutes
System returned to ROM by reload
System image file is "bootflash:packages.conf"
Last reload reason: reload
---------------------------------------
curl -k https://devnetsandboxiosxe.cisco.com:443/restconf/data/ietf-interfaces:interfaces/interface=GigabitEthernet1 -u admin:C1sco12345 --header 'Accept: application/yang-data+json'
<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx/1.13.12</center>
</body>
</html>
curl: (6) Could not resolve host: application
---------------------------------------
Only thing I notice is that the hostname of the router has been changed.
04-05-2024 08:49 AM
I was briefly able to access via ssh and saw a rather funky MOTD before i was kicked out. The always on devices get a lot of abuse sadly which impacts other users, i would use the reservation based sandbox instead, as this is a isolated sandbox for your use only.
Hope this helps.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide