Can not update node on Ubuntu 22

[sag333ar]

Describe the bug
Can not update my node on Ubuntu 22

To Reproduce
Steps to reproduce the behavior:

1. Clicked here
2. Ran command - sudo apt update
3. Then ran command - sudo apt install myst

~ sudo apt install myst
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
myst is already the newest version (1.9.2+build570175622+jammy).

Expected behavior
It should update to latest 1.9.5 but it isn't

[isaackielma]

@sag333ar @mysteriumnetwork/node-happiness Looks like Ubuntu issue:

https://askubuntu.com/questions/692775/cannot-initiate-the-connection-to-in-archive-ubuntu-com80-when-trying-to-run

Ubuntu is not able to update using this commands - sudo apt update; sudo apt install myst - which are given in document - https://docs.mysterium.network/for-node-runners/updating-your-node

[Zensey]

@sag333ar @isaackielma
There's no surprise, 1.9.2 is the latest myst build available in myst repo on launchpad.

https://ppa.launchpad.net/mysteriumnetwork/node/ubuntu/pool/main/m/myst/

[sag333ar]

@isaackielma - then why does my node says "Connection failed"

[Zensey]

@sag333ar
You can switch to the node-dev repo https://launchpad.net/~mysteriumnetwork/+archive/ubuntu/node-dev
Then 1.9.5 will become be available for update.

[Zensey]

@sag333ar
But I would recommend using node-pre than dev
https://ppa.launchpad.net/mysteriumnetwork/node-pre/ubuntu/pool/main/m/myst/

[sag333ar]

@Zensey - please provide exact command which I can run on my Ubuntu.

[etherunit]

sudo add-apt-repository ppa:mysteriumnetwork/node-pre
sudo apt-get update
sudo apt install myst

[sag333ar]

sudo apt install myst

worked like charm. thank you.

[sag333ar]

No. Now it says
Node status: Test Failed

@etherunit , @isaackielma , @Zensey

[isaackielma]

Looks like these 2 nodes are sharing the same IP. Please choose to have only 1 of them and the issue will likely go away. Mysterium Network only allows 1 node per IP address

[sag333ar]

but @isaackielma , you can clearly see that the Desktop node says connection failed and M1 13 says offline.
It means The other node (M1 13) is offline. I turned it off. If other node (M1 13) is turned off, Desktop node should work fine, shouldn't it?

[etherunit]

We should check it. please provide your node identity, the one that fails. thanks!

[sag333ar]

@etherunit it's 0x16940f45ee5f0d52ecbe968bc131e5c93c738267

[etherunit]

I can connect to your node, but unable to resolve any pages.

ping google.com
ping: cannot resolve google.com: Unknown host

might be an issue with DNS settings

[sag333ar]

@etherunit What DNS settings do you recommend?

[etherunit]

You can try Google DNS
8.8.8.8
or Cloudfare 1.1.1.1

[sag333ar]

@etherunit
Worked fine for me

➜  ~ ping google.com
PING google.com(bom07s18-in-x0e.1e100.net (2404:6800:4009:80c::200e)) 56 data bytes
64 bytes from bom07s18-in-x0e.1e100.net (2404:6800:4009:80c::200e): icmp_seq=1 ttl=118 time=5.25 ms
64 bytes from bom07s18-in-x0e.1e100.net (2404:6800:4009:80c::200e): icmp_seq=2 ttl=118 time=5.27 ms
64 bytes from bom07s18-in-x0e.1e100.net (2404:6800:4009:80c::200e): icmp_seq=3 ttl=118 time=6.76 ms
64 bytes from bom07s18-in-x0e.1e100.net (2404:6800:4009:80c::200e): icmp_seq=4 ttl=118 time=5.91 ms
64 bytes from bom07s18-in-x0e.1e100.net (2404:6800:4009:80c::200e): icmp_seq=5 ttl=118 time=6.25 ms
64 bytes from bom07s18-in-x0e.1e100.net (2404:6800:4009:80c::200e): icmp_seq=6 ttl=118 time=5.55 ms
64 bytes from bom07s18-in-x0e.1e100.net (2404:6800:4009:80c::200e): icmp_seq=7 ttl=118 time=5.17 ms
64 bytes from bom07s18-in-x0e.1e100.net (2404:6800:4009:80c::200e): icmp_seq=8 ttl=118 time=5.61 ms
64 bytes from bom07s18-in-x0e.1e100.net (2404:6800:4009:80c::200e): icmp_seq=9 ttl=118 time=6.06 ms
64 bytes from bom07s18-in-x0e.1e100.net (2404:6800:4009:80c::200e): icmp_seq=10 ttl=118 time=7.70 ms
64 bytes from bom07s18-in-x0e.1e100.net (2404:6800:4009:80c::200e): icmp_seq=11 ttl=118 time=5.15 ms
64 bytes from bom07s18-in-x0e.1e100.net (2404:6800:4009:80c::200e): icmp_seq=12 ttl=118 time=7.49 ms

[sag333ar]

You can try Google DNS 8.8.8.8 or Cloudfare 1.1.1.1

@etherunit - I updated DNS settings. Try now.

[etherunit]

Hello @sag333ar I'm experiencing the same issue. Can you please submit the latest node log for review?

[sag333ar]

I stopped every node of mysteriumnetwork