Hello everyone, I hope you have a good start of the week.
Doing a more thorough review, I could detect that my error was that my services running on docker containers were detecting the address of the same docker container id, so adding the following line in my properties file (spring.cloud.consul.discovery.preferIpAddress= true) I could solve the error that showed Krakend, but I came up with 3 new details which I expose below:
1. I deployed krakend in a container to not have it installed directly as a service on my test server, but it was not detecting the dns of my services in consul.
2. Connect the krakend container to the network of my consul container, and it can see the services, but the only way to get krakend working was to make requests directly to the krakend container, if I try to make requests from another machine to the server or from an external network, I get the message, that the connection is blocked to the krakend port. Check ports and firewall and everything is ok.
3. With krakend installed directly as a service on my fedora 35 server, I can load the krakend.json file without problems and I can make requests from other machines even from outside my network and krakend works, only when making wrong requests my backend for example answers 400 not found and krakend returns 500 internal server error, is there any way for krakend to return the error that my backend answers.
Thank you very much to all, I am very excited to learn and use krakend in my implementations.
Kind regards.
Carlos Sánchez
El sábado, 19 de febrero de 2022 a las 12:30:57 UTC-3, Carlos Alberto Sanchez Perez escribió: