by Guest on 2025/09/18 10:34:45 AM
Previous version (1.41) did have cookie file setting to make autorization for control port, current (1.42) - lost it. Why? How does it work without?
I'm having weird problem - suddenly dmx stopped to connect to any network, and i can't debug it. tor itself is properly bootstrapped and have circuits built and i can successfully reach websites (both regular and onions) thru it's socks port.
I already tested previous version - same noconnect problem. Also tested previous tor binaries and no luck.
Diagnostics don't show anything of a help
by Guest on 2025/09/18 01:47:17 PM
Status - Retry in XX
Event log - error: Host unreachable from proxy (49691)
Interesting thing now - i have 2 networks connected it seems.
I also made a fresh node, launched it and there is same behaviour - 2 networks connect fine, other are not.
btw: diagnostics -> tor monitor - apparently only for internal tor, and don't have use for ext.
I wish there was some connectivity check. It could ping some url and tell if it is ok. Beside dmx servers i mean.