mysteriumnetwork/node

Curl/https doesnt work inside docker client but for specific Node

Closed this issue · 2 comments

Describe the bug
Especially for my node 0x009b3514939b657f665fe812ea4c65ca4c784bcb, i usually get Monitoring failed as reason and somehow i saw it marked as Online, but i got lots of connection with less than 100kb usage in 2 min.

To Reproduce
Steps to reproduce the behavior:
Example:

  1. Connect to 0x009b3514939b657f665fe812ea4c65ca4c784bcb form docker client
  2. Try to curl a website or update the packages
  3. Sometimes never works or sometimes works but for some minutes! (2min)
  4. But while running dig command, DNS returns valid IP

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
Client Logs:
image
DNS works:
image
Stuck while adding packages:
image
image
Curl and Ping:
image

Environment (please complete the following information):

  • Node version: 1.27.0
  • OS: Client Docker in Ubuntu 20.04 amd64 and Node in Docker aarch64 Raspberrypi 6.1.21-v8+
  • Your identity (if applicable): 0x009b3514939b657f665fe812ea4c65ca4c784bcb

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.