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

Node version doesn't update on MMN #3373

Closed
etherunit opened this issue May 10, 2021 · 6 comments
Closed

Node version doesn't update on MMN #3373

etherunit opened this issue May 10, 2021 · 6 comments
Assignees

Comments

@etherunit
Copy link
Collaborator

etherunit commented May 10, 2021

Describe the bug
ID: 0xa20504db0b6790715509a04aa70a2e0459c0e6e6
Pulled latest docker image (updated).

docker exec -it myst /bin/bash
bash-5.0# myst version
Mysterium Node
  Version: 0.46.1
  Build info: Branch: 0.46.1. Build id: 290620211. Commit: 39954d3a

my.mysterium.network shows 0.42.6. Getting this message:

Screenshot 2021-05-10 at 15 26 52

Expected behavior
Version is updated on MMN.

Environment (please complete the following information):

  • Node version: 0.46.1
  • OS: Alpine Linux v3.12
@benv666
Copy link

benv666 commented May 17, 2021

Seeing the same thing here while running the latest docker image (mysteriumnetwork/myst:latest):
image

$ docker exec -it myst myst version
Mysterium Node
  Version: 0.46.1
  Build info: Branch: 0.46.1. Build id: 290620211. Commit: 39954d3a

Container has been deleted and recreated, no effect.

@eugenegoncharuk eugenegoncharuk self-assigned this May 18, 2021
@adpandhare
Copy link

Upgraded to version 0.46.1 still showing version 0.44.0

Node number 0x5510c92dc0fb9d5bf88149a55c568e1be24d7309

MMN

@NebNitram
Copy link

I have upgraded also.. with exactly the same issue
Node: 0x8ebeb4e76767d7dbfdd39a8115ec32d3dfb06fb6
Screen Shot 2021-05-20 at 21 53 42

@soffokl
Copy link
Member

soffokl commented May 21, 2021

@benv666 @adpandhare @NebNitram @etherunit
Could you please try to go to the nodeUI settings and set MMN integration API Key once again?
Looks like it solved the problem for me.
image

@adpandhare
Copy link

Thanks @soffokl, It worked for me too!

@chompomonim
Copy link
Contributor

Closing issue as it is most probably fixed. Please open new one if it will repeat.

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

No branches or pull requests

7 participants