After attempting to connect to an ssh target with all 0.14.* boundary client versions, the worker failed to connect to boundary worker by its public_addr (currently set to SERVER IP). As the app is deployed as a container doesn't resolve the SERVER IP bridge to the network interface.
setting up a reverse proxy might help tackling this issue:
[ ] trying other boundary desktop and client versions to troubleshoot this bug
After attempting to connect to an ssh target with all 0.14.* boundary client versions, the worker failed to connect to boundary worker by its public_addr (currently set to SERVER IP). As the app is deployed as a container doesn't resolve the SERVER IP bridge to the network interface.
setting up a reverse proxy might help tackling this issue: