wrapper-manager | time="2026-05-02T21:17:20Z" level=info msg="wrapperManager running at 0.0.0.0:8080"
wrapper-manager | time="2026-05-02T21:17:28Z" level=info msg="decrypt stream from 172.19.0.1:58456"
wrapper-manager | time="2026-05-02T21:17:28Z" level=info msg="status request from 172.19.0.1:58456"
wrapper-manager | time="2026-05-02T21:17:40Z" level=info msg="login stream from 172.19.0.1:58456"
wrapper-manager | time="2026-05-02T21:17:40Z" level=warning msg="Wrapper exited with error: exit status 1\n"
wrapper-manager | time="2026-05-02T21:17:40Z" level=info msg="[wrapper f72fa3c1] Wrapper Down"
wrapper-manager doesn't seem to restart the wrapper automatically, so we wait for a response that will never arrive.
Passing --debug or -debug to wrapper-manager unfortunately does not give me any additional details.
wrapper-manager doesn't seem to restart the wrapper automatically, so we wait for a response that will never arrive.
Passing --debug or -debug to wrapper-manager unfortunately does not give me any additional details.