We run Iguana on AWS, on a Linux EC2 instance behind a classic Elastic Load Balancer.

Whenever we visit the logs page (/logs.html on the server), in the Javascript console, we see a 502 error from a POST to the path /javascript/logs. When I use Postman to POST directly to the server to that same path, I get back a response like the one below. My guess (from reading this article, is that the response Iguana is returning doesn’t meet the HTTP spec, and so the ELB is choking on it.

Has anyone ever seen anything like this, and if you resolved it, what did you do?

{
"error": {
"return_code": null
},
"server_label": "My Iguana Server Name",
"status": "error"
}