im a student in computer science and i don’t understand why boundary use 3 ports 9200/9201/9202 ?
actually, i can connect to a redis service(only exposed for boundary on docker) with all these 3 ports with commands:
ok thanks, i understand better now, i do little changes about that.
i said in my first post that i can connect to redis but it was a mistake.
So for the moment it would seem that in can authenticate to the worker (on default port → 9200)but when im on the worker i can’t reach redis
Yeah ty for your precision but now my problem has changed, it’s little bit different:
my host redis is binded via boundary with the docker hostname redis and i can connect to a boundary session but i can’t acces to my redis service throught boundary’s worker
By default the redis-cli command will look on 127.0.0.1:6379 for a connection. At the moment, I can’t see a way to feed the port you get back from boundary into the exec argument, but I’ll ask internally and see what I can find.
What you can do is initiate your connection to the target, then run redis-cli -p <port_from_boundary> and you’ll get a successful connection.