Closed emilianozublena closed 3 years ago
Hi @kpacha me again, did any of you had any time to take a look at the issue mentioned above here?
Thanks again!
check your startup logs. I think you'll find an error regarding your amqp connection (it's the most common scenario). Depending on the reason, it could be a line like this:
▶ ERROR AMQP: getting the channel for amqp://XXX:YYY@rabbit:5672/queue-name: dial tcp: lookup rabbit: Temporary failure in name resolution
Will check tmw and get back to you, thanks a lot!
We nailed it, basically our docker was initializing krakend before rabbitmq was up, thus throwing those errors... Thanks for pinpointing in the right direction @kpacha
Hi everyone! first of all, awesome products you've been building. So we're thinking on using KrakenD as our API Gateway, and since we have a message-driven API built on top of RabbitMQ for our internal communication between services, we've been looking into using this plugin to allow external parties to call a rest endpoint and Kraken to transport to AMQP and so on.. Everything looks good, we've installed Kraken as a standalone daemon and the plugin works fine, but as soon as we put together a Docker image (we have everything containerized) we started hitting this error with the exact same configurations for everything:
Running kraken with --debug throws a more descriptive error. Still unsure what's causing it though
I haven't been able to find anything anywhere about this, any ideas??
Thanks a lot!