> docker run  --env RUST_LOG=hq=debug,tako=debug -v .\access.json:/root/.hq-server/hq-current/access.json  -it hyperqueue worker start                                 
[2025-05-20T00:16:20.068Z INFO  hyperqueue::worker::hwdetect] Detected 8183431168B of memory (7.62 GiB)
[2025-05-20T00:16:20.069Z INFO  hyperqueue::worker::bootstrap] Starting hyperqueue worker 0.22.0-dev
[2025-05-20T00:16:20.070Z INFO  hyperqueue::worker::bootstrap] Connecting to: solfunmeme.ddns.net:38171
[2025-05-20T00:16:20.086Z INFO  tako::internal::worker::rpc] Listening on port 33383
[2025-05-20T00:16:20.086Z INFO  tako::internal::worker::rpc] Connecting to server (candidate addresses = [18.222.179.195:38171])
[2025-05-20T00:16:20.118Z DEBUG tako::internal::worker::rpc] Connected to server at 18.222.179.195:38171
[2025-05-20T00:16:20.149Z DEBUG tako::internal::transfer::auth] Worker authorization started
[2025-05-20T00:16:20.149Z DEBUG tako::internal::transfer::auth] Challenge verification started
[2025-05-20T00:16:20.149Z DEBUG tako::internal::transfer::auth] Challenge verification finished

thread 'main' panicked at /build/crates/tako/src/internal/worker/rpc.rs:171:25:
Connection closed without receiving registration response
stack backtrace:
   0:     0x562ee5ca1fe2 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::hc04c8f544ab24d66
   1:     0x562ee5cd0f83 - core::fmt::write::hfe57b7174b7d8eab
   2:     0x562ee5c9d793 - std::io::Write::write_fmt::h154385efa8565236
   3:     0x562ee5ca1e32 - std::sys::backtrace::BacktraceLock::print::h0c8f24e22f5873a8
   4:     0x562ee5ca30fc - std::panicking::default_hook::{{closure}}::hd07d57e6a602c8e4
   5:     0x562ee5ca2eff - std::panicking::default_hook::h63d12f7d95bd91ed
   6:     0x562ee56aae81 - hq::main::{{closure}}::{{closure}}::had94ae80d0db6cb3
Oops, HyperQueue has crashed. This is a bug, sorry for that.
If you would be so kind, please report this issue at the HQ issue tracker: https://github.com/It4innovations/hyperqueue/issues/new?title=HQ%20crashes
Please include the above error (starting from "thread ... panicked ...") and the stack backtrace in the issue contents, along with the following information:

HyperQueue version: 0.22.0-dev

You can also re-run HyperQueue server (and its workers) with the `RUST_LOG=hq=debug,tako=debug`
environment variable, and attach the logs to the issue, to provide us more information.