Connection Refused with Krakend

Hi,

I have a gateway on Docker Web Service with Krakend. This have 1 endpoint /healthz and proxy the /healthz path of 3 microservices on Docker Private Web Service and merge the response. In local works fine but in Render.com throws an error on Krakend:

Get "http://microservice-1:3001/healthz": dial tcp 10.202.18.181:3001: connect: connection refused
Get "http://microservice-2:3002/healthz": dial tcp 10.202.18.181:3002: connect: connection refused
Get "http://microservice-3:3003/healthz": dial tcp 10.202.18.181:3003: connect: connection refused

where microservice-n:300x is the host and the port of render gives me to connect.

On local, i fix this using the public IP of my machine and not de host “localhost”.

How can i fix this in Render.com?

Thanks,

It’s solved, but i don’t know why. Automatically, magically. :smile:

1 Like

It should have worked, but if this resolves itself, it may be that your other microservices weren’t yet available.

2 Likes

This seems like a bug to me. Is this behavior intentional?

Hi Muneeb,

I think Adrian’s original comment alluded to the fact that the 3 micro-services behind the proxy were probably failing Render’s health checks. If you are running into a similar issue, I’d be happy to dig deeper.