mysteriumnetwork / node

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

Mysterium Node issue with connection #5240

Closed sanox1 closed 1 year ago

sanox1 commented 2 years ago

Describe the bug On my nodes I see connection failed,

In log of docker:

022-06-22T12:48:02.380 WRN ../../nat/traversal/pinger.go:138 > One of the pings has error error="ping receiver error: context deadline exceeded" 2022-06-22T12:48:02.380 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} 2022-06-22T12:48:02.380 ERR ../../p2p/listener.go:168 > Could not ping peer error="too few connections were built"

I opened port 4449 on router but no luck. Please assist.

To Reproduce Steps to reproduce the behavior:

  1. I deleted docker image
  2. I deleted docker container
  3. I put new string into docker "docker pull mysteriumnetwork/myst && docker run --cap-add NET_ADMIN -d -p 4449:4449 --name myst -v C:/var/lib/mysterium-node --restart unless-stopped mysteriumnetwork/myst:latest service --agreed-terms-and-conditions" and claimed node, paid 0.03 MYST and it was green for about 10 minutes
  4. After 10 minutes I see error Connection failed in mystnodes.com

Expected behavior I expect green connection. My other node on raspbian is working normally but its currently offline as I have turned raspberry off.

Screenshots not applicable

Environment (please complete the following information):

Additional context not applicable

adinetech commented 2 years ago

Forward default 10000:60000 UDP ports, it might work.

sanox1 commented 2 years ago

Hi, you mean open these ports in router? Or adjust the docker image string? I opened the ports and it was green for about 10 minutes and then it shows connection failed again. EDIT: On port 10000 it just tries to install it and nothing happens

etherunit commented 2 years ago

You need to do both. Go to https://docs.mysterium.network/troubleshooting/troubleshooting-nat-type-related-issues and navigate to view this subsection: Enable Port Forwarding for the Docker container running a node

sanox1 commented 2 years ago

docker run --cap-add NET_ADMIN -d -p 4449:4449 -p 59850-60000:59850-60000/udp --name myst -v myst-data:/var/lib/mysterium-node mysteriumnetwork/myst:latest --udp.ports=59850:60000 service --agreed-terms-and-conditions 614e8fab17c41c76fa8eb272fd7e9cda974c27ac43da0965e5640ae423e8ddb0 docker: Error response from daemon: Ports are not available: exposing port UDP 0.0.0.0:59948 -> 0.0.0.0:0: listen udp 0.0.0.0:59948: bind: An attempt was made to access a socket in a way forbidden by its access permissions.

this error appears

etherunit commented 2 years ago

It looks like ports were not available. Do you still experience this issue till now?

sanox1 commented 2 years ago

For now it works on launcher 1.10.0/docker 4.10.1 by using port forwarding 34500: 50000 and opening those ports in the router.Lets keep the issue open this week to monitor further

sanox1 commented 2 years ago

Hello, stopped working again. Getting this error in docker: image

adinetech commented 2 years ago

Use another port range.

sanox1 commented 2 years ago

Use another port range.

the button in launcher is no longer clickable so I cannot change the port range. Launcher is stucked in an "installing / offline" loop. This happens EVERY TIME I switch from port forwarding to NAT and to Port forwarding again, and is not fixed unless I delete and recreate the container and image in docker and pay another 0.03 MYST. Then it works for a while and again shows "connection failed". Last time I was able to get 1 session before it showed "connection failed". I am wasting my time and money with this project!

stale[bot] commented 1 year ago

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.

stale[bot] commented 1 year ago

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.