This means Tyk couldn’t reach your Key Cloak instance. The error is typically caused by the target not being available to receive the request or a network issue.
As we’ve seen on this community before, the connect: connection refused error could be related to docker. So you might want to try replacing 0.0.0.0 with host.docker.internal or the private IP of your machine.