Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unregistration for protocol ipv6 does not work #511

Closed
Yurbason opened this issue Jan 29, 2021 · 2 comments
Closed

Unregistration for protocol ipv6 does not work #511

Yurbason opened this issue Jan 29, 2021 · 2 comments

Comments

@Yurbason
Copy link

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? :)

@EEFF0C
Copy link

EEFF0C commented Feb 8, 2021

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.

@Yurbason Yurbason closed this as completed May 8, 2021
@Yurbason
Copy link
Author

Yurbason commented May 8, 2021

after switching to a new version, this error has ceased to be relevant

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants