search

mysteriumnetwork / node

Mysterium Network Node - official implementation of distributed VPN network (dVPN) protocol
https://mysterium.network
GNU General Public License v3.0
1.11k stars 313 forks source link

Your identity is being registered, please be patient.. #3003

Closed etherunit closed 3 years ago

etherunit commented 3 years ago

Provider: 0xa84a29a32bb38c2694a1fe35a0c691a662bd8d30; Migrated node from V1 to V2 network but stuck on identity registration screen;

Screenshot 2021-01-18 at 14 13 31 Screenshot 2021-01-18 at 14 16 05 Screenshot 2021-01-18 at 14 15 35

Node logs: https://testnet2.mysterium.network/admin/issues/download/1628

vkuznecovas commented 3 years ago

Identity was registered, see https://testnet2-transactor.mysterium.network/api/v1/identity/0xa84a29a32bb38c2694a1fe35a0c691a662bd8d30/status

Registration tx: http://goerli.etherscan.io/tx/0x1e47cc2ab9ece36d6cf910373cedc114d997a13918dad415e33cedf47b4824a5

Seems like the bug is related to the reporting of the status.

etherunit commented 3 years ago

Adding another provider facing registration reporting issues. 0x485a502e4c08ae22e0bfac282453941a2b72cb29

Jan 16 16:29:44 raspberrypi myst[2268]: 2021-01-16T16:29:44.378 INF identity/registry/provider_registrar.go:183 > Provider "0x485a502e4c08ae22e0bfac282453941a2b72cb29" not registere
d on BC, will check if elgible for auto-registration
Jan 16 16:29:44 raspberrypi myst[2268]: 2021-01-16T16:29:44.582 DBG config/config.go:196 > Returning default value chain-id:5
Jan 16 16:29:44 raspberrypi myst[2268]: 2021-01-16T16:29:44.713 ERR identity/registry/provider_registrar.go:218 > Registration failed for provider "0x485a502e4c08ae22e0bfac282453941
a2b72cb29" error="server response invalid: 429 Too Many Requests (https://testnet2-transactor.mysterium.network/api/v1/identity/register)Limit exceeded"
Jan 16 16:29:44 raspberrypi myst[2268]: 2021-01-16T16:29:44.716 ERR identity/registry/provider_registrar.go:149 > Could not complete registration for provider "0x485a502e4c08ae22e0b
fac282453941a2b72cb29". Will retry. Retry 1 of 10 error="could not register identity on BC: server response invalid: 429 Too Many Requests (https://testnet2-transactor.mysterium.net
work/api/v1/identity/register)Limit exceeded" stack=[{"func":"(*ProviderRegistrar).registerIdentity","line":"219","source":"provider_registrar.go"},{"func":"(*ProviderRegistrar).han
dleEvent","line":"184","source":"provider_registrar.go"},{"func":"(*ProviderRegistrar).handleEventWithRetries","line":"144","source":"provider_registrar.go"},{"func":"(*ProviderRegi
strar).start","line":"239","source":"provider_registrar.go"},{"func":"(*ProviderRegistrar).handleNodeStartupEvents","line":"110","source":"provider_registrar.go"},{"func":"Value.cal
l","line":"460","source":"value.go"},{"func":"Value.Call","line":"321","source":"value.go"},{"func":"(*EventBus).doPublish","line":"158","source":"event_bus.go"},{"func":"(*EventBus
).doPublishAsync","line":"166","source":"event_bus.go"},{"func":"goexit","line":"868","source":"asm_arm.s"}]
masterdot commented 3 years ago

0xba22f43595d4c6c6ccc4090298b86b41b758d07f

mysterium-node.service - Server for Mysterium - decentralised VPN Network
   Loaded: loaded (/lib/systemd/system/mysterium-node.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2021-01-19 12:37:20 GMT; 30min ago
     Docs: https://mysterium.network/                                                                                                                                                                                 Main PID: 929 (myst)                                                                                                                                                                                                    Tasks: 18 (limit: 3861)
   CGroup: /system.slice/mysterium-node.service                                                                                                                                                                                 ├─929 /usr/bin/myst --config-dir=/etc/mysterium-node --script-dir=/etc/mysterium-node --data-dir=/var/lib/mysterium-node --runtime-dir=/var/run/mysterium-node --keystore.lightweight service --agreed-ter           └─956 openvpn --port 47482 --server 10.8.0.0 255.255.255.0 --topology subnet --tls-server --dh none --explicit-exit-notify --ca /var/run/mysterium-node/ca.crt --cert /var/run/mysterium-node/server.crt -
Jan 19 13:07:01 raspberrypi myst[929]: 2021-01-19T13:07:01.587 DBG eventbus/event_bus.go:81                 > Published topic="balance_change" event={Identity:{Address:0xba22f43595d4c6c6ccc4090298b86b41b758d07f} PJan 19 13:07:01 raspberrypi myst[929]: 2021-01-19T13:07:01.729 DBG config/config.go:196                     > Returning default value chain-id:5
Jan 19 13:07:02 raspberrypi myst[929]: 2021-01-19T13:07:02.293 DBG config/config.go:192                     > Returning user config value terms.provider-agreed:true                                                 Jan 19 13:07:02 raspberrypi myst[929]: 2021-01-19T13:07:02.294 DBG config/config.go:192                     > Returning user config value terms.consumer-agreed:true
Jan 19 13:07:02 raspberrypi myst[929]: 2021-01-19T13:07:02.294 DBG config/config.go:192                     > Returning user config value terms.version:0.0.27                                                       Jan 19 13:07:28 raspberrypi myst[929]: 2021-01-19T13:07:28.165 DBG config/config.go:196                     > Returning default value chain-id:5                                                                     Jan 19 13:07:28 raspberrypi myst[929]: 2021-01-19T13:07:28.166 INF identity/registry/provider_registrar.go:183 > Provider "0xba22f43595d4c6c6ccc4090298b86b41b758d07f" not registered on BC, will check if elgible foJan 19 13:07:28 raspberrypi myst[929]: 2021-01-19T13:07:28.307 DBG config/config.go:196                     > Returning default value chain-id:5
Jan 19 13:07:28 raspberrypi myst[929]: 2021-01-19T13:07:28.395 ERR identity/registry/provider_registrar.go:218 > Registration failed for provider "0xba22f43595d4c6c6ccc4090298b86b41b758d07f" error="server responselines 1-19/20 87%
scysys commented 3 years ago

Same here after upgrade from 0.39 to 0.41.

Your identity is being registered, please be patient..

Gui message is never ending. But node is sucessfully registered.

chompomonim commented 3 years ago

@mdomasevicius could you look deeper at this issue? It seems that it is some bug in NodeUI.

@scysys have you tried to restart node? Are you still getting this issue?

si458 commented 3 years ago

@chompomonim i too am getting this issue,

already reported to @etherunit

my node is 0x485a502e4c08ae22e0bfac282453941a2b72cb29

A reboot of my pi makes no difference

mdomasevicius commented 3 years ago

Seems that after non 2xx registration response identity status in bolt is never updated.

https://github.com/mysteriumnetwork/node/pull/3029 - should re-fetch status from blockchain if it was persisted InProgress

Data-Gremlin commented 3 years ago

UI displaying same "Your identity is being registered, please be patient " overlay. Node showing as offline via main account . Device rebooted with no change. Mysterium notified. @0700 on 21.01.2021

Data-Gremlin commented 3 years ago

@chompomonim I have rebooted the node a few times now and are issued a new IP.

Mine is still showing as Offline

chompomonim commented 3 years ago

The problem should be fixed with next release 0.41.2. Now it is in release candidate stage (https://github.com/mysteriumnetwork/node/releases/tag/0.41.2-rc0), should be released today or tomorrow.

Data-Gremlin commented 3 years ago

@chompomonim I've just checked and still not available so will recheck in the morning.

Mine is saying up to date on Ver 0.41

Running on RP4

Data-Gremlin commented 3 years ago

@chompomonim I have my RP4 shh open what do I need to type to get the newest update please.

I've tried.

Sudo apt-get update && sudo apt-get upgrade myst

But still not working.

Linux raspberrypi 5.4.83-v7l+ #1379 SMP Mon Dec 14 13:11:54 GMT 2020 armv7l

The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: myst@raspberrypi:~ $ sudo apt-get update && sudo apt-get upgrade myst Ign:1 http://ppa.launchpad.net/mysteriumnetwork/node-testnet2/ubuntu focal InRelease Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease Hit:3 http://archive.raspberrypi.org/debian buster InRelease Err:4 http://ppa.launchpad.net/mysteriumnetwork/node-testnet2/ubuntu focal Release 404 Not Found [IP: 91.189.95.85 80] Hit:5 http://deb.debian.org/debian buster-backports InRelease Hit:6 http://deb.debian.org/debian unstable InRelease Reading package lists... Done E: The repository 'http://ppa.launchpad.net/mysteriumnetwork/node-testnet2/ubuntu focal Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. myst@raspberrypi:~ $

chompomonim commented 3 years ago

@Data-Gremlin you should change repository to 'http://ppa.launchpad.net/mysteriumnetwork/node-/ubuntu in your apt.sources.

You can try:

sudo add-apt-repository ppa:mysteriumnetwork/node
sudo apt-get update
sudo apt-get upgrade
Data-Gremlin commented 3 years ago

@chompomonim added what you suggested to my sources.list but keep getting this.

Have I added it wrong? Or is as informed 403 Forbidden.

myst@raspberrypi:~ $ sudo apt-get update && sudo apt-get upgrade myst Err:1 http://ppa.launchpad.net/mysteriumnetwork/node-/ubuntu buster InRelease 403 Forbidden [IP: 91.189.95.85 80] Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease Hit:3 http://archive.raspberrypi.org/debian buster InRelease Ign:4 http://ppa.launchpad.net/mysteriumnetwork/node-testnet2/ubuntu focal InRelease Hit:5 http://deb.debian.org/debian buster-backports InRelease Err:6 http://ppa.launchpad.net/mysteriumnetwork/node-testnet2/ubuntu focal Release 404 Not Found [IP: 91.189.95.85 80] Hit:7 http://deb.debian.org/debian unstable InRelease Reading package lists... Done E: Failed to fetch http://ppa.launchpad.net/mysteriumnetwork/node-/ubuntu/dists/buster/InRelease 403 Forbidden [IP: 91.189.95.85 80] E: The repository 'http://ppa.launchpad.net/mysteriumnetwork/node-/ubuntu buster InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://ppa.launchpad.net/mysteriumnetwork/node-testnet2/ubuntu focal Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details.

scysys commented 3 years ago

@mdomasevicius could you look deeper at this issue? It seems that it is some bug in NodeUI.

@scysys have you tried to restart node? Are you still getting this issue?

@chompomonim Yes. This message was never gone. After restart and reboot this message is there. I just reinstalled. It´s fast and solved the error.

Data-Gremlin commented 3 years ago

Can anyone help please. Really want to get working again

masterdot commented 3 years ago

Can anyone help please. Really want to get working again

Your repository link is wrong, should be http://ppa.launchpad.net/mysteriumnetwork/node/ubuntu

yours is http://ppa.launchpad.net/mysteriumnetwork/ node- /ubuntu/dists/buster/InRelease

si458 commented 3 years ago

@Data-Gremlin make sure /etc/apt/sources.list.d/mysterium.list has the following inside deb http://ppa.launchpad.net/mysteriumnetwork/node/ubuntu focal main then apt update and apt upgrade it should auto-upgrade the myst package

just upgraded my pi and now web-panel works perfectly, same with the registration!

masterdot commented 3 years ago

Same here, fixed for me

Data-Gremlin commented 3 years ago

@masterdot I now have it working and have my node transferred. However all my previous transactions and earning haven't transferred over?

masterdot commented 3 years ago

@Data-Gremlin Same here. @chompomonim told me that the previous earnings are on testnet1 and are only transferable, if they exceed the minimum amount. Testnet2 earns for itself.

chompomonim commented 3 years ago

Earning on testnet1 stays on testnet1. Testnet2 is completely separate network. Anyway, discussion about earnings is out of context of this issue.

With release of 0.41.2 this issues should be already fixed. Closing it.

Data-Gremlin commented 3 years ago

@si458 quick question out of context but when mysterium is on my network does VPN and any other protection stop them gaining access to my Lan ?

si458 commented 3 years ago

@Data-Gremlin the only thing i have spotted is when i connect to my node from my tablet (using 4g)

i cant access anything on my home network using any ports as expected

HOWEVER if i goto the node ip and a port, then that is accessible

for example i ran a pi node but then installed sonarr or apache on the pi, i was able to access those no problem via the mysterium network

you get the node ip when you look at ur routing table and see what the default gateway is after u connect to your node

si458 commented 3 years ago

@chompomonim my node has deregistered and wont register again now?

Jan 25 18:29:50 raspberrypi myst[1258]: #033[90m2021-01-25T18:29:50.494#033[0m #033[1m#033[31mERR#033[0m#033[0m #033[1mcmd/mysterium_node/mysterium_node.go:68 #033[0m#033[36m >#033
[0m Failed to execute command:  #033[31merror=#033[0m#033[31m"could not get hermes url: daily request count exceeded, request rate limited"#033[0m
smmsadrnezh commented 3 years ago

I have this problem with the latest docker version.

chompomonim commented 3 years ago

@smmsadrnezh this should be caused be temporary problems by our meta transactions delayer and growing even goearli testnet becoming full.

vishawsingh commented 2 years ago

I have it for last 20 hours or so and its not going away. On my Nodes Network I can see this machine has been registered but sitting offline with status : Last Seen Never.

image