502 Bad Gateway + Empty reply from server

[craigp318]

I'm trying to deploy in ec2. When i visit the port specified in my conf.yaml (5050), I get "502 Bad Gateway".
When I ssh onto the ec2 host and enter (interactively) into the docker container, and run curl commands, I get these errors:

• curl -k https://localhost:5050 => no output
• curl https://localhost:5050 => url: (60) SSL certificate problem: self-signed certificate More details here: https://curl.se/docs/sslcerts.html
• curl http://localhost:5050 => curl: (52) Empty reply from server

Given that localhost:5050 has the login portal, I expect to get HTML reply.
This makes my think that there's an issue with the gateway on my ec2 instance (rather than something with ibeam itself)
Have you seen anything like this? Is this expected behavior?

[Voyz]

hey @craigp318 please provide more details using the bug template provided, as well as the full output log from the IBind instance. As for these endpoints:

curl -k https://localhost:5050/ => no output

As expected, I don't think root route returns anything. Try: curl -X GET "https://localhost:5050/v1/api/iserver/auth/status" -k

curl https://localhost:5050 => url: (60) SSL certificate problem: self-signed certificate

This indicates you can communicate with the gateway but it lacks certificates. Please see: https://github.com/Voyz/ibeam/wiki/TLS-Certificates-and-HTTPS