node
node copied to clipboard
Node offline since 1.6.4 update
Tuesday morning I've updated the Node from 1.6.3 to 1.6.4. From what i ''see'' its in an endless loop of trying to connect to Myst network. Since then it doesn't stay online
Environment:
- Node version: 1.6.4
- OS: Windows 10
- Desktop app version (if applicable): 1.0.27
- Docker Desktop 4.6.1 (76265)
- Identity: 0x4011c66a07c6526ca3839b1aaf4e2ef4325f6b22
I've attached a log from the node New Text Document.txt
It stopped publishing proposal ±2-3 days ago.
its hard to say why it failed that particular day from the 1st glance at logs because it start only at
2022-04-19T19:39:01.281 INF
from current logs its clear that your node is failing to reach the blockchain, broker and other services.
e.g. failed to lookup host: "broker.mysterium.network" error="lookup broker.mysterium.network on 192.168.65.5:53: dial udp 192.168.65.5:53: operation was canceled"
Try to: reboot your node / reboot your device running it / restart firewall
updated to 1.6.5 rebooted laptop + network + changed networks (have 2 different ISPs here) same issues doesn't connect... :(
Is there any possibility to migrate the node from this laptop to another ?
How did you update it? It still shows offline on mystnodes.com I need to understand whether its something badly executed on your side or its an issue on our side.
its stays on like 10-15sec - while trying to connect to the MYST network
in that time, the Myst Node Launcher manages to install the update
It seems like the node automatically crashes within 10-15 seconds because unable to reach the Mysterium services, Sadly I don't have any idea to resolve this error.
@Friguletz can you try the newest version?
it looks like a DNS-related issue
@Friguletz
if the problem still persists could you try query a server address in a terminal:
nslookup polygon1.mysterium.network
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had activity for a long time. If this issue is still valid, please ping a maintainer and ask them to label it as "pinned". Thank you for your contributions.
Hi @Friguletz Can you try the latest version?