node Node Status : Test Failed

Describe the bug I'm Experiencing this issue from past 5 days. i have tried all the methods by restarting the node and changing internet methods.

Screenshots

Environment (please complete the following information):

Node version: 1.12.2
OS: Debian GNU/Linux 11 (bullseye)
Your identity (if applicable): 0xc35e91a92d88cfe6692d250268b478e81c3d9f8c
Payment (top-op) reference (if applicable): NIL

Sep 06 '22 18:09 kabirzohaib22

Same issue for me. I've raised this: https://github.com/mysteriumnetwork/node/issues/5409

Sep 07 '22 08:09 lollapalooza1973

Getting the issue : Node status : Test Failed from last 3 days

Node version: mainnet (1.13.1-0245c7bb) NodeUI version: 1.17.2 ID 0x7e52414c858e9ce530f85b7bf1e177faf5692a36

Sep 08 '22 16:09 hbkwant

@kabirzohaib22 Hello there!

Do you happen to have logs so we can check them?

Sep 13 '22 13:09 isaackielma

NODE LOGS.txt

Sep 13 '22 14:09 kabirzohaib22

Screen Shot 2022-09-14 at 09 26 32 It looks like UDP hole punching is used to establish a connection instead of manual port forwarding. The problem is that it doesnt work with your network, Screen Shot 2022-09-14 at 09 34 15

Please try to switch back to manual and see if it helps.

Sep 14 '22 06:09 etherunit

It looks like UDP hole punching is used to establish a connection instead of manual port forwarding. The problem is that it doesnt work with your network,
Please try to switch back to manual and see if it helps.

How do i do that, can you please guide me.

Sep 14 '22 07:09 kabirzohaib22

Could you specify how it's currently configured in NodeUI? Go to Advanced Settings

Sep 14 '22 08:09 etherunit

Could you specify how it's currently configured in NodeUI? Go to Advanced Settings

Sep 14 '22 09:09 kabirzohaib22

Thanks, could you also check it under args for myst service -- > cat /etc/default/mysterium-node Specifically DAEMON_OPTS and SERVICE_OPTS lines

Sep 15 '22 06:09 etherunit

cat /etc/default/mysterium-node

Sep 15 '22 06:09 kabirzohaib22

Thanks, could you also check it under args for myst service -- > cat /etc/default/mysterium-node Specifically DAEMON_OPTS and SERVICE_OPTS lines

Any updates yet ?

Sep 19 '22 10:09 kabirzohaib22

There are upcoming monitoring service changes which should help to reduce such issues. We expect them to be released next week.

@kabirzohaib22 can you also try to start completely new node on the same network? It might be related to somehow corrupted DB/config of existing node.

Sep 20 '22 07:09 Donatas-MN

Thanks, could you also check it under args for myst service -- > cat /etc/default/mysterium-node Specifically DAEMON_OPTS and SERVICE_OPTS lines

my node is not yet fixed, it's been a month now :(

Sep 27 '22 18:09 kabirzohaib22

Have you tried to setup completely new node?

Sep 27 '22 18:09 Donatas-MN

Have you tried to setup completely new node?

No i haven't yet

Sep 27 '22 18:09 kabirzohaib22

Please try. If possible on multiple devices.

Sep 28 '22 06:09 Donatas-MN

Please try. If possible on multiple devices.

Tried it, still not working.

Oct 04 '22 03:10 kabirzohaib22

guys, team did quite a few important bug fixes included in the latest node releases. Please update and check if that helps.

Oct 15 '22 17:10 etherunit

1.19.0 is not availalbe yet via apt

Oct 16 '22 08:10 lollapalooza1973

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.

Jan 14 '23 13:01 stale[bot]

@lollapalooza1973 @kabirzohaib22 @hbkwant Are you still experiencing "Test failed" issue?

Feb 28 '23 08:02 Donatas-MN

@lollapalooza1973 @kabirzohaib22 @hbkwant Are you still experiencing "Test failed" issue?

Yes, it's been a long time now. My node is still running,but not generating anything because of this. It's not showing up ON

Feb 28 '23 12:02 kabirzohaib22

@kabirzohaib22 can you reinstall node from scratch with newest version and then submit logs here?

Feb 28 '23 14:02 Donatas-MN

@kabirzohaib22 can you reinstall node from scratch with newest version and then submit logs here?

Okay, will try that. Currently the node is running over Docker platform.

Feb 28 '23 14:02 kabirzohaib22

@kabirzohaib22 can you reinstall node from scratch with newest version and then submit logs here? nodelogs.zip i have re-installed the node. couple of months earlier it was running on docker.

Mar 01 '23 20:03 kabirzohaib22

Thanks @kabirzohaib22 . I will check your node logs and reply back.

Mar 02 '23 05:03 etherunit

@kabirzohaib22 can you reinstall node from scratch with newest version and then submit logs here?

i got no reply yet

Mar 14 '23 19:03 kabirzohaib22

@etherunit could you please update the status of this? Thank you

Jun 12 '23 08:06 ZygintasBudrys

@kabirzohaib22 Apologies for a delayed response on this ticket. Based on the previous log output and current metadata, your node is still struggling to establish p2p connections while using hole_punching (current active traversal method). Please see below:

ar 02 01:01:12 raspberrypi myst[826]: 2023-03-02T01:01:12.655 DBG eventbus/event_bus.go:101                > Published topic="Traversal" event={ID:remove this id Stage:hole_punching Successful:false Error:too few connections were built}
Mar 02 01:01:12 raspberrypi myst[826]: 2023-03-02T01:01:12.656 ERR p2p/listener.go:168                      > Could not ping peer error="too few connections were built"

I suggest to improve it by configuring on of the following traversals: UPnP, port forwarding or DMZ (in a very rare cases as in general it's not recommended due to security reasons). See the explaining article by following this link.

Jun 22 '23 05:06 etherunit

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.

Sep 23 '23 14:09 stale[bot]