You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the ipv4 protocol, everything works great, but for a mixer running on ipv6, there is always an error.
Nym Mixnode 0.9.2
$ nym-mixnode unregister --id MixNode
_ __ _ _ _ __ ___
| '_ \| | | | '_ \ _ \
| | | | |_| | | | | | |
|_| |_|\__, |_| |_| |_|
|___/
(mixnode - version 0.9.2)
Attempting to unregister mixnode MixNode...
2021-01-29T22:31:21.038 ERROR nym_mixnode::commands::unregister > failed to unregister node 'MixNode'. Error: ValidatorError("node\'s mix host does not match the remote address")
the second problem is that after restarting the daemon, the mixer cannot connect to the network, because it believes that the mixer is already there. More than 6 hours have passed since the moment when I restarted the daemon, but the mixer is still present in the dashboard.
nym-mixnode[9207]: 2021-01-29T21:20:39.679 WARN nym_mixnode::node > We seem to have not unregistered after going offline - there's a node with identical identity and announce-host as us registered.
it turns out a vicious circle :)
Do I need to wait until the rating drops to 0 for the mixer to disappear from the network and I can reconnect? :)
The text was updated successfully, but these errors were encountered:
I also had this same issue, could not unregister an ipv6 mixnode, with same error message you noted. Eventually the mixnode is 'removed' and you can re-register (if there is capacity). Workaround is to only run nodes that announce an ipv4 address for now.
For the ipv4 protocol, everything works great, but for a mixer running on ipv6, there is always an error.
Nym Mixnode 0.9.2
the second problem is that after restarting the daemon, the mixer cannot connect to the network, because it believes that the mixer is already there. More than 6 hours have passed since the moment when I restarted the daemon, but the mixer is still present in the dashboard.
nym-mixnode[9207]: 2021-01-29T21:20:39.679 WARN nym_mixnode::node > We seem to have not unregistered after going offline - there's a node with identical identity and announce-host as us registered.
it turns out a vicious circle :)
Do I need to wait until the rating drops to 0 for the mixer to disappear from the network and I can reconnect? :)
The text was updated successfully, but these errors were encountered: