isaackielma

isaackielma

Member Since 5 months ago

Experience Points
1
follower
Lessons Completed
1
follow
Lessons Completed
1
stars
Best Reply Awards
0
repos

39 contributions in the last year

Pinned
Activity
Oct
17
1 week ago
Activity icon
issue

isaackielma issue mysteriumnetwork/node

isaackielma
isaackielma

"Test Connection" gets the message "Unauthenticated"

Describe the bug Node's status is marked as test failed. Even after node reboot and update.

0xb0858ca5931a1a1310399dd1ab58f849b00260c1

[email protected]:~#0.67.0 Build info: Branch: 0.67.0. Build id: 386192775. Commit: 8aeb9998

Expected behavior Node should complete a test connection with the node.

Environment (please complete the following information): OS: Ubuntu 20.04.3 LTS Architecture: linux/amd64 Node version: 0.66.3

Additional context

$ sudo systemctl daemon-reload $ sudo systemctl restart mysterium-node $ systemctl status mysterium-node ● mysterium-node.service - Server for Mysterium - decentralised VPN Network Loaded: loaded (/lib/systemd/system/mysterium-node.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2021-10-09 01:03:24 CEST; 564ms ago Docs: https://mysterium.network/ Main PID: 1805054 (myst) Tasks: 10 (limit: 9485) Memory: 10.2M CGroup: /system.slice/mysterium-node.service └─1805054 /usr/bin/myst --config-dir=/etc/mysterium-node --script-dir=/etc/mysterium-node --data-dir=/var/lib/mysterium-node --runtime-dir=/var/run/mysterium-no> Oct 09 01:03:25 vmi683860.contaboserver.net myst[1805054]: 2021-10-09T01:03:25.081 INF cmd/di.go:645 > Using local DNS: testnet3-location.mysteriu> Oct 09 01:03:25 vmi683860.contaboserver.net myst[1805054]: 2021-10-09T01:03:25.082 INF cmd/di.go:645 > Using local DNS: api.ipify.org -> [54.204.1> Oct 09 01:03:25 vmi683860.contaboserver.net myst[1805054]: 2021-10-09T01:03:25.082 INF cmd/di.go:645 > Using local DNS: badupnp.benjojo.co.uk -> [> Oct 09 01:03:25 vmi683860.contaboserver.net myst[1805054]: 2021-10-09T01:03:25.082 INF cmd/di.go:645 > Using local DNS: testnet3-trust.mysterium.n> Oct 09 01:03:25 vmi683860.contaboserver.net myst[1805054]: 2021-10-09T01:03:25.082 INF cmd/di.go:645 > Using local DNS: testnet3-quality.mysterium> Oct 09 01:03:25 vmi683860.contaboserver.net myst[1805054]: 2021-10-09T01:03:25.082 INF cmd/di.go:645 > Using local DNS: feedback.mysterium.network> Oct 09 01:03:25 vmi683860.contaboserver.net myst[1805054]: 2021-10-09T01:03:25.082 DBG communication/nats/connector.go:78 > Connecting to NATS servers: [nats://testnet> Oct 09 01:03:25 vmi683860.contaboserver.net myst[1805054]: 2021-10-09T01:03:25.082 INF firewall/outgoing_firewall_noop.go:57 > Allow URL nats://testnet3-broker.mysterium.> Oct 09 01:03:25 vmi683860.contaboserver.net myst[1805054]: 2021-10-09T01:03:25.083 INF firewall/outgoing_firewall_noop.go:57 > Allow URL nats://testnet3-broker.mysterium.> Oct 09 01:03:25 vmi683860.contaboserver.net myst[1805054]: 2021-10-09T01:03:25.083 INF firewall/outgoing_firewall_noop.go:57 > Allow URL nats://167.233.11.60:4222 access $ systemctl status mysterium-node ● mysterium-node.service - Server for Mysterium - decentralised VPN Network Loaded: loaded (/lib/systemd/system/mysterium-node.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Sat 2021-10-09 01:03:32 CEST; 288ms ago Docs: https://mysterium.network/ Process: 1805054 ExecStart=/usr/bin/myst $CONF_DIR $SCRIPT_DIR $DATA_DIR $RUN_DIR $DAEMON_OPTS service --agreed-terms-and-conditions $SERVICE_OPTS (code=exited, status=1> Main PID: 1805054 (code=exited, status=1/FAILURE) Oct 09 01:03:32 vmi683860.contaboserver.net systemd[1]: mysterium-node.service: Main process exited, code=exited, status=1/FAILURE Oct 09 01:03:32 vmi683860.contaboserver.net systemd[1]: mysterium-node.service: Failed with result 'exit-code'.

Activity icon
issue

isaackielma issue mysteriumnetwork/node

isaackielma
isaackielma

Payment in progress error

Describe the bug should have received two payments, but as of now I still haven't received anything in my wallet. I'm using the trustwallet

0x15f92952234e967c8f8e7a9749ce5fbd72fbef79

Error messages: Payment in progress. It should reach you before 2021-10-07. Payment in progress. It should reach you before 2021-09-07.

To Reproduce Steps to reproduce the behavior:

  1. Go to 'MMN dashboard'
  2. Click on 'bounty payout history'
  3. Scroll down
  4. See error

Expected behavior Payments should have been made by now

Environment (please complete the following information): OS: Raspbian GNU/Linux 10 (buster) Architecture: linux/arm Node version: 0.65.0

Activity icon
issue

isaackielma issue mysteriumnetwork/node

isaackielma
isaackielma

Credit reset from 50 myst to 0

Describe the bug

My credit was reset from 50 myst to 0. But I haven't received a payout in my wallet yet.

The payout has not yet been received on my Metamask wallet.

0xefb4c0a998bc098d9d0a0c137b8d28144b854c92

To Reproduce Steps to reproduce the behavior:

  1. Go to 'MMN Dashboard'
  2. Click on 'bounty payout history'
  3. Scroll down
  4. See error

Expected behavior Balance was reset from 50 to 0.

Environment (please complete the following information): OS: Raspbian GNU/Linux 10 (buster) Architecture: linux/arm Node version: 0.66.4

Oct
14
1 week ago
Activity icon
issue

isaackielma issue mysteriumnetwork/node

isaackielma
isaackielma

MMN Dashboard NOT displaying the list of nodes

Describe the bug

MMN Dashboard NOT displaying the list of nodes, or randomly switching from displaying the list, to this "Setup your first node" page is kind of annoying.

When I overlay "Nodes" I see the full list, but it is truncated because I have many nodes and this smaller list is size-limited by the vertical size of the webpage.

Node ID: 0xd1a45106c9d05b356ae875dbdc68ec2b890a4493

To Reproduce Steps to reproduce the behavior:

  1. Go to 'MMN Dashboard'
  2. Click on 'Login'
  3. Scroll down to 'see nodes'
  4. See error

Expected behavior Node list should automatically display.

Screenshots image

Environment (please complete the following information):

  • Node version: [e.g. 0.19.1]
  • OS: [e.g. raspbian buster, debian 10]
  • Desktop app version (if applicable): [e.g. 2.0.4]
  • Docker (if applicable): specify docker version and image tag

Additional context Add any other context about the problem here.

Oct
12
1 week ago
Activity icon
issue

isaackielma issue mysteriumnetwork/node

isaackielma
isaackielma

Lots of 0 byte connections from Germany. No normal sessions

Describe the bug

I keep getting lots of 0 byte connections, please can you check my node is functioning properly? thanks.

Test sessions seem to be successful but no normal incoming sessions

The specifications of my node are these 👇🏻 Node: 0x9ba274ab7c... Status: Online Last seen: 1 minute ago Node version: 0.66.4

Expected behavior Normal sessions should be happening

Environment (please complete the following information): OS: Ubuntu 20.04.3 LTS Architecture: linux/amd64 Node version: 0.66.4

Additional context mysterium-node-15.log

Activity icon
issue

isaackielma issue mysteriumnetwork/node

isaackielma
isaackielma

Node test failed even after restarting. "Permissive NAT"

Describe the bug

Hello, My node respond with "Test Failed" for two days. I have no idea what to do. The node runs on Oracle arm64 VPS, Ubuntu 20.04. The identity is: 0xcdeb451f572a6f77491086bda2ec15f63667b6e0 The DH2i NAT Test responds with "Permissive NAT". Thanks in advance!

Expected behavior If node is receiving both test and normal sessions, transfer of data and earnings should be increasing.

Environment (please complete the following information): OS: Ubuntu 20.04.3 LTS Architecture: linux/arm64 Node version: 0.66.4

Additional context mysterium-node-13.log

Activity icon
issue

isaackielma issue mysteriumnetwork/node

isaackielma
isaackielma

Long session not reflected into earnings

Describe the bug

ID: 0x7525249fd4ad940829eb538fa3855a9c2f890376

Few days ago i had someone connected to my network for a long time (3 days as you can see). I've seen Live earning as higher than 0 MYSTT. but once connection ended, in Sessions history i see it gave my nothing. Live data was also bigger than 0, bigger than 500mb for sure. Both session time and data transferred are worth something. What happened there? Here are details:

LU 3d 21:31:42 10/7/2021, 6:15:44 PM 0.0000000 MYSTT 0 Bytes d8381320

*Logs can be found on Additional context section

Expected behavior Earnings should be updating.

Environment (please complete the following information): OS: Debian GNU/Linux 10 (buster) Architecture: linux/arm64 Node version: 0.63.0

Additional context mysterium-node.log

Oct
7
2 weeks ago
Activity icon
issue

isaackielma issue mysteriumnetwork/node

isaackielma
isaackielma

Ethereum top up fail issue

Describe the bug

Sent around 15$ in eth to purchase 20myst and It never arrived. i sent the eth to the eth address provided to me, I sent this around 2 days ago and still do not have my top up?" To Reproduce

Steps to reproduce the behavior: https://etherscan.io/tx/0x103267b57e9e7b43b4957d712e282b8665c3beb5d039ec838865965de114acba'

Expected behavior Top up should land in user's balance after a few minutes.

Screenshots

Uploading Screenshot 2021-10-07 at 15.43.11.png…Environment (please complete the following information): Screenshot 2021-10-07 at 15 43 11"

Additional context https://etherscan.io/tx/0x103267b57e9e7b43b4957d712e282b8665c3beb5d039ec838865965de114acba

Activity icon
issue

isaackielma issue mysteriumnetwork/node

isaackielma
isaackielma

Control on the maximum shared data (bandwidth) that can be used per month

Is your feature request related to a problem? Please describe.

No control over the maximum bandwidth that can be used/shared per month.

"I see in the node dashboard that we can limit the bandwidth usage to a maximum per time unit — but what about having control on the maximum that can be used per month (or whatever time unit)? could you please add this, set by the user? it would be useful to many I'm sure"

Describe the solution you'd like

Maybe a check box allowing that possibility

"it's mainly about not reaching the bandwidth limit on rented hardware without notice, so that the thing cannot get disconnected totally at some point — keeping some margin for running whatever else process on the given hardware

Additional context Suggestion made by Charly Empereur-mot user on Telegram

Sep
27
3 weeks ago
Activity icon
issue

isaackielma issue comment mysteriumnetwork/node

isaackielma
isaackielma

Your identity is being registered, please be patient...

Planned to create 10 nodes using DigitalOcean VPS, 8 successed and two failed. Both stucked at the message "Your identity is being registered, please be patient..." when I try to open the dashboard. Please help me get out of this status. I am completed new to this project, a step by step operation note/ command line will be appreciated. Thanks.

NodeID1:0x545888592d1a3fe162cc7aacc8e0fbe7fad40937 NodeID2:0xc50c1b94be9a8d1fc3b7dfdbcc03db5144bb095f

Environment :

  • Node version: 0.65.0
  • OS: Ubuntu 20.04(LTS) x64 under DigitalOcean VPS
isaackielma
isaackielma

Node ID: 0xbc7e66c8b0597981a99ef1d880d4eaa919d0568e

Also experiencing this same issue for over 12 hours "Your identity is being registered, please be patient"

Activity icon
issue

isaackielma issue comment mysteriumnetwork/node

isaackielma
isaackielma

Mobile app disconnected due to insufficient balance error message

Describe the bug ID: 0x9ec7aef942e0d7d6aff222e8a31e545bb3d4679b

"I'll get disconnected at seemingly random times due to insufficient balance. even though I have about 20 myst in the account, the account displays 0 myst after disconnection then after an hour or so the right amount of myst is displayed again.

I have slow internet, and I'm using a Nord plus n200 5g with android 11. I'm using the latest version of mysterium. hope this helps"

To Reproduce Steps to reproduce the behavior:

  1. Go to 'mobile app'
  2. Click connect to 'any node'
  3. See error

Expected behavior Session should start and keep going until funds actually run out.

Environment (please complete the following information):

  • OS: Android

Additional context

Same issue: https://github.com/mysteriumnetwork/node-user-reports/issues/3726

logs:

filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":0,"ServiceType":"wireguard"} 2021-09-21T00:40:55.000 DBG app/market/mysterium/mysterium_api.go:66 > Total proposals: 2255 supported: 2255 2021-09-21T00:40:55.000 INF app/core/discovery/repository.go:93 > Returning 2255 unique proposals 2021-09-21T00:41:00.000 DBG app/eventbus/event_bus.go:81 > Published topic="NAT-type-detected" event=prcone 2021-09-21T00:41:00.000 DBG app/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":0,"ServiceType":"wireguard"} 2021-09-21T00:41:03.000 DBG app/market/mysterium/mysterium_api.go:66 > Total proposals: 2255 supported: 2255 2021-09-21T00:41:03.000 INF app/core/discovery/repository.go:93 > Returning 2255 unique proposals 2021-09-21T00:41:43.000 DBG app/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"","PresetID":0,"ProviderID":"","QualityMin":0,"ServiceType":"wireguard"} 2021-09-21T00:41:43.000 DBG app/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"","PresetID":0,"ProviderID":"","QualityMin":0,"ServiceType":"wireguard"} 2021-09-21T00:41:49.000 DBG app/market/mysterium/mysterium_api.go:66 > Total proposals: 2256 supported: 2256 2021-09-21T00:41:49.000 INF app/core/discovery/repository.go:93 > Returning 2256 unique proposals 2021-09-21T00:41:49.000 INF app/session/pingpong/pricing.go:160 > pricing info loaded 2021-09-21T00:41:49.000 DBG app/market/mysterium/mysterium_api.go:66 > Total proposals: 2256 supported: 2256 2021-09-21T00:41:50.000 INF app/core/discovery/repository.go:93 > Returning 2256 unique proposals 2021-09-21T00:41:53.000 DBG app/eventbus/event_bus.go:81 > Published topic="NAT-type-detected" event=prcone 2021-09-21T00:41:53.000 DBG app/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":0,"ServiceType":"wireguard"} 2021-09-21T00:42:02.000 DBG app/market/mysterium/mysterium_api.go:66 > Total proposals: 2256 supported: 2256 2021-09-21T00:42:02.000 INF app/core/discovery/repository.go:93 > Returning 2256 unique proposals 2021-09-21T00:42:14.000 DBG app/eventbus/event_bus.go:81 > Published topic="NAT-type-detected" event=prcone 2021-09-21T00:42:14.000 DBG app/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":0,"ServiceType":"wireguard"} 2021-09-21T00:42:18.000 DBG app/market/mysterium/mysterium_api.go:66 > Total proposals: 2256 supported: 2256 2021-09-21T00:42:18.000 INF app/core/discovery/repository.go:93 > Returning 2256 unique proposals 2021-09-21T00:42:20.000 DBG app/eventbus/event_bus.go:81 > Published topic="NAT-type-detected" event=prcone 2021-09-21T00:42:20.000 DBG app/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":0,"ServiceType":"wireguard"} 2021-09-21T00:42:20.000 DBG app/eventbus/event_bus.go:81 > Published topic="NAT-type-detected" event=prcone 2021-09-21T00:42:20.000 DBG app/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":0,"ServiceType":"wireguard"}

Activity icon
issue

isaackielma issue comment mysteriumnetwork/node

isaackielma
isaackielma

Top up fail. Not reflecting balance in app

Describe the bug

ID: 0x5ee2596e6e017c3f8cb5e4be194875a780196e5b

"History: I decided to try Mysteriun just a couple of days ago after tip from a user at youtube. I found this open source decentralized vpn interesting, and I like it from my first impression. I then decided to make a top-up with ETH from my wallet at Bitkub.com (Thailand) for further testing. This was my first crypto payment ever. Everything went fine, except from the ETH fee charges and the MYSTT fee witch I found way too expensive to stay connected online all the time.

But I still decided to make another top-up from the same wallet. This time I got a limit warning during the top-up process witch made me change the amount to proceed. So far so good, I got an email from my wallet for confirming purposes in witch I responded to. Then I got a new email confirming the payment. All well so far.

From my first top-up I remembered immediate result, and the top-up was confirmed right away. This was not the case this second time. No top-up was registered.

This is where we are now. The details from the top-ups are as following: Top-up nr. 1: Done 27.08.2021 at 16:12:18 with the amount 0.00706500 ETH and a fee at 0.0035000 witch is about 50%!!! Crazy fee, and I can not say this help to make further top-ups.

Top-up nr. 2: Done 30.08.2021 at 21:17:24 with the amount of 0.00700ETH. Fe again 50% 0.003500ETH!! The fee is a showstopper, so we need to find another top-up method for the future. Hope you have any suggestions.

So, a couple of hours after my second top-up, and no new balance, I decided to write you an email with my concerns.

From the transaction details in my wallet, I can take out Txid and Address, but I prefer to only send info highly needed for you to fix my balance as soon as possible.

Thank you in advance."

To Reproduce Steps to reproduce the behavior:

  1. Go to 'Client App'
  2. See balance

Expected behavior Amount deposited should reflect in balance soon after top up was executed.

Additional context

Same issue: https://github.com/mysteriumnetwork/node-user-reports/issues/3654

2021-09-14T11:32:58.575 INF source/core/discovery/repository.go:93 > Returning 2073 unique proposals 2021-09-14T11:33:27.301 DBG source/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":1,"ServiceType":"wireguard"} 2021-09-14T11:33:28.704 DBG source/market/mysterium/mysterium_api.go:66 > Total proposals: 2073 supported: 2073 2021-09-14T11:33:28.706 INF source/core/discovery/repository.go:93 > Returning 2073 unique proposals 2021-09-14T11:33:57.298 DBG source/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":1,"ServiceType":"wireguard"} 2021-09-14T11:33:58.506 DBG source/market/mysterium/mysterium_api.go:66 > Total proposals: 2072 supported: 2072 2021-09-14T11:33:58.513 INF source/core/discovery/repository.go:93 > Returning 2072 unique proposals 2021-09-14T11:34:27.303 DBG source/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":1,"ServiceType":"wireguard"} 2021-09-14T11:34:28.547 DBG source/market/mysterium/mysterium_api.go:66 > Total proposals: 2073 supported: 2073 2021-09-14T11:34:28.549 INF source/core/discovery/repository.go:93 > Returning 2073 unique proposals 2021-09-14T11:34:57.299 DBG source/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":1,"ServiceType":"wireguard"}

Sep
24
1 month ago
Activity icon
issue

isaackielma issue mysteriumnetwork/node

isaackielma
isaackielma

Top up fail. Not reflecting balance in app

Describe the bug

ID: 0x5ee2596e6e017c3f8cb5e4be194875a780196e5b

"History: I decided to try Mysteriun just a couple of days ago after tip from a user at youtube. I found this open source decentralized vpn interesting, and I like it from my first impression. I then decided to make a top-up with ETH from my wallet at Bitkub.com (Thailand) for further testing. This was my first crypto payment ever. Everything went fine, except from the ETH fee charges and the MYSTT fee witch I found way too expensive to stay connected online all the time.

But I still decided to make another top-up from the same wallet. This time I got a limit warning during the top-up process witch made me change the amount to proceed. So far so good, I got an email from my wallet for confirming purposes in witch I responded to. Then I got a new email confirming the payment. All well so far.

From my first top-up I remembered immediate result, and the top-up was confirmed right away. This was not the case this second time. No top-up was registered.

This is where we are now. The details from the top-ups are as following: Top-up nr. 1: Done 27.08.2021 at 16:12:18 with the amount 0.00706500 ETH and a fee at 0.0035000 witch is about 50%!!! Crazy fee, and I can not say this help to make further top-ups.

Top-up nr. 2: Done 30.08.2021 at 21:17:24 with the amount of 0.00700ETH. Fe again 50% 0.003500ETH!! The fee is a showstopper, so we need to find another top-up method for the future. Hope you have any suggestions.

So, a couple of hours after my second top-up, and no new balance, I decided to write you an email with my concerns.

From the transaction details in my wallet, I can take out Txid and Address, but I prefer to only send info highly needed for you to fix my balance as soon as possible.

Thank you in advance."

To Reproduce Steps to reproduce the behavior:

  1. Go to 'Client App'
  2. See balance

Expected behavior Amount deposited should reflect in balance soon after top up was executed.

Additional context

Same issue: https://github.com/mysteriumnetwork/node-user-reports/issues/3654

2021-09-14T11:32:58.575 INF source/core/discovery/repository.go:93 > Returning 2073 unique proposals 2021-09-14T11:33:27.301 DBG source/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":1,"ServiceType":"wireguard"} 2021-09-14T11:33:28.704 DBG source/market/mysterium/mysterium_api.go:66 > Total proposals: 2073 supported: 2073 2021-09-14T11:33:28.706 INF source/core/discovery/repository.go:93 > Returning 2073 unique proposals 2021-09-14T11:33:57.298 DBG source/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":1,"ServiceType":"wireguard"} 2021-09-14T11:33:58.506 DBG source/market/mysterium/mysterium_api.go:66 > Total proposals: 2072 supported: 2072 2021-09-14T11:33:58.513 INF source/core/discovery/repository.go:93 > Returning 2072 unique proposals 2021-09-14T11:34:27.303 DBG source/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":1,"ServiceType":"wireguard"} 2021-09-14T11:34:28.547 DBG source/market/mysterium/mysterium_api.go:66 > Total proposals: 2073 supported: 2073 2021-09-14T11:34:28.549 INF source/core/discovery/repository.go:93 > Returning 2073 unique proposals 2021-09-14T11:34:57.299 DBG source/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":1,"ServiceType":"wireguard"}

Activity icon
issue

isaackielma issue mysteriumnetwork/node

isaackielma
isaackielma

Mobile app disconnected due to insufficient balance error message

Describe the bug

"I'll get disconnected at seemingly random times due to insufficient balance. even though I have about 20 myst in the account, the account displays 0 myst after disconnection then after an hour or so the right amount of myst is displayed again.

I have slow internet, and I'm using a Nord plus n200 5g with android 11. I'm using the latest version of mysterium. hope this helps"

To Reproduce Steps to reproduce the behavior:

  1. Go to 'mobile app'
  2. Click connect to 'any node'
  3. See error

Expected behavior Session should start and keep going until funds actually run out.

Environment (please complete the following information):

  • OS: Android

Additional context

Same issue: https://github.com/mysteriumnetwork/node-user-reports/issues/3726

logs:

filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":0,"ServiceType":"wireguard"} 2021-09-21T00:40:55.000 DBG app/market/mysterium/mysterium_api.go:66 > Total proposals: 2255 supported: 2255 2021-09-21T00:40:55.000 INF app/core/discovery/repository.go:93 > Returning 2255 unique proposals 2021-09-21T00:41:00.000 DBG app/eventbus/event_bus.go:81 > Published topic="NAT-type-detected" event=prcone 2021-09-21T00:41:00.000 DBG app/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":0,"ServiceType":"wireguard"} 2021-09-21T00:41:03.000 DBG app/market/mysterium/mysterium_api.go:66 > Total proposals: 2255 supported: 2255 2021-09-21T00:41:03.000 INF app/core/discovery/repository.go:93 > Returning 2255 unique proposals 2021-09-21T00:41:43.000 DBG app/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"","PresetID":0,"ProviderID":"","QualityMin":0,"ServiceType":"wireguard"} 2021-09-21T00:41:43.000 DBG app/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"","PresetID":0,"ProviderID":"","QualityMin":0,"ServiceType":"wireguard"} 2021-09-21T00:41:49.000 DBG app/market/mysterium/mysterium_api.go:66 > Total proposals: 2256 supported: 2256 2021-09-21T00:41:49.000 INF app/core/discovery/repository.go:93 > Returning 2256 unique proposals 2021-09-21T00:41:49.000 INF app/session/pingpong/pricing.go:160 > pricing info loaded 2021-09-21T00:41:49.000 DBG app/market/mysterium/mysterium_api.go:66 > Total proposals: 2256 supported: 2256 2021-09-21T00:41:50.000 INF app/core/discovery/repository.go:93 > Returning 2256 unique proposals 2021-09-21T00:41:53.000 DBG app/eventbus/event_bus.go:81 > Published topic="NAT-type-detected" event=prcone 2021-09-21T00:41:53.000 DBG app/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":0,"ServiceType":"wireguard"} 2021-09-21T00:42:02.000 DBG app/market/mysterium/mysterium_api.go:66 > Total proposals: 2256 supported: 2256 2021-09-21T00:42:02.000 INF app/core/discovery/repository.go:93 > Returning 2256 unique proposals 2021-09-21T00:42:14.000 DBG app/eventbus/event_bus.go:81 > Published topic="NAT-type-detected" event=prcone 2021-09-21T00:42:14.000 DBG app/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":0,"ServiceType":"wireguard"} 2021-09-21T00:42:18.000 DBG app/market/mysterium/mysterium_api.go:66 > Total proposals: 2256 supported: 2256 2021-09-21T00:42:18.000 INF app/core/discovery/repository.go:93 > Returning 2256 unique proposals 2021-09-21T00:42:20.000 DBG app/eventbus/event_bus.go:81 > Published topic="NAT-type-detected" event=prcone 2021-09-21T00:42:20.000 DBG app/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":0,"ServiceType":"wireguard"} 2021-09-21T00:42:20.000 DBG app/eventbus/event_bus.go:81 > Published topic="NAT-type-detected" event=prcone 2021-09-21T00:42:20.000 DBG app/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":0,"ServiceType":"wireguard"}

Activity icon
issue

isaackielma issue comment mysteriumnetwork/node

isaackielma
isaackielma

Balance unchanged after top up

Describe the bug "I topup my account using LN. Unfortunatelly I still have 0 MYST on my account. My CoinGate Order ID is #9477224 from 13.09.2021. could you please help?"

ID: 0x5906ddb139c9a3e6d247521db8e375c766d8948f

Expected behavior Account balance should change after Top up.

Additional Context Also found here: https://github.com/mysteriumnetwork/node-user-reports/issues/3748

isaackielma
isaackielma

filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":0,"ServiceType":"wireguard"} 2021-09-22T13:36:19.000 DBG app/market/mysterium/mysterium_api.go:66 > Total proposals: 2320 supported: 2320 2021-09-22T13:36:19.000 INF app/core/discovery/repository.go:93 > Returning 2320 unique proposals 2021-09-22T13:36:20.000 DBG app/market/mysterium/mysterium_api.go:66 > Total proposals: 2320 supported: 2320 2021-09-22T13:36:20.000 INF app/core/discovery/repository.go:93 > Returning 2320 unique proposals 2021-09-22T13:36:27.000 DBG app/eventbus/event_bus.go:81 > Published topic="NAT-type-detected" event=prcone 2021-09-22T13:36:27.000 DBG app/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":0,"ServiceType":"wireguard"} 2021-09-22T13:36:28.000 DBG app/market/mysterium/mysterium_api.go:66 > Total proposals: 2320 supported: 2320 2021-09-22T13:36:28.000 INF app/core/discovery/repository.go:93 > Returning 2320 unique proposals 2021-09-22T13:36:28.000 INF app/session/pingpong/pricing.go:160 > pricing info loaded 2021-09-22T13:36:41.000 DBG app/eventbus/event_bus.go:81 > Published topic="NAT-type-detected" event=prcone 2021-09-22T13:36:41.000 DBG app/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":0,"ServiceType":"wireguard"} 2021-09-22T13:36:42.000 DBG app/market/mysterium/mysterium_api.go:66 > Total proposals: 2320 supported: 2320 2021-09-22T13:36:42.000 INF app/core/discovery/repository.go:93 > Returning 2320 unique proposals 2021-09-22T13:37:18.000 DBG app/eventbus/event_bus.go:81 > Published topic="NAT-type-detected" event=prcone 2021-09-22T13:37:18.000 DBG app/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":0,"ServiceType":"wireguard"} 2021-09-22T13:37:18.000 DBG app/eventbus/event_bus.go:81 > Published topic="NAT-type-detected" event=prcone 2021-09-22T13:37:18.000 DBG app/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":0,"ServiceType":"wireguard"} 2021-09-22T13:37:19.000 DBG app/market/mysterium/mysterium_api.go:66 > Total proposals: 2320 supported: 2320 2021-09-22T13:37:19.000 INF app/core/discovery/repository.go:93 > Returning 2320 unique proposals 2021-09-22T13:37:20.000 DBG app/market/mysterium/mysterium_api.go:66 > Total proposals: 2320 supported: 2320 2021-09-22T13:37:20.000 INF app/core/discovery/repository.go:93 > Returning 2320 unique proposals 2021-09-22T13:37:27.000 DBG app/eventbus/event_bus.go:81 > Published topic="NAT-type-detected" event=prcone 2021-09-22T13:37:27.000 DBG app/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":0,"ServiceType":"wireguard"} 2021-09-22T13:37:28.000 DBG app/market/mysterium/mysterium_api.go:66 > Total proposals: 2320 supported: 2320 2021-09-22T13:37:28.000 INF app/core/discovery/repository.go:93 > Returning 2320 unique proposals 2021-09-22T13:37:42.000 DBG app/eventbus/event_bus.go:81 > Published topic="NAT-type-detected" event=prcone 2021-09-22T13:37:42.000 DBG app/core/discovery/repository.go:63 > Retrieving proposals from 1 repositories filter={"AccessPolicy":"","AccessPolicySource":"","CompatibilityMax":0,"CompatibilityMin":0,"ExcludeUnsupported":true,"IPType":"","IncludeMonitoringFailed":false,"LocationCountry":"","NATCompatibility":"prcone","PresetID":0,"ProviderID":"","QualityMin":0,"ServiceType":"wireguard"} 2021-09-22T13:37:43.000 DBG app/market/mysterium/mysterium_api.go:66 > Total proposals: 2320 supported: 2320 2021-09-22T13:37:43.000 INF app/core/discovery/repository.go:93 > Returning 2320 unique proposals

Activity icon
issue

isaackielma issue mysteriumnetwork/node

isaackielma
isaackielma

Balance unchanged after top up

Describe the bug "I topup my account using LN. Unfortunatelly I still have 0 MYST on my account. My CoinGate Order ID is #9477224 from 13.09.2021. could you please help?"

ID: 0x5906ddb139c9a3e6d247521db8e375c766d8948f

Expected behavior Account balance should change after Top up.

Additional Context Also found here: https://github.com/mysteriumnetwork/node-user-reports/issues/3748

Activity icon
issue

isaackielma issue mysteriumnetwork/node

isaackielma
isaackielma

"Restart" button somewhere in the WebUI dashboard

Is your feature request related to a problem? Please describe. When an error like test failed happen or any other small issues, some non tech savvy users may have trouble with restarting the node.

Describe the solution you'd like These complications would be solved by a "restart" button somewhere in the WebUI dashboard!

Describe alternatives you've considered Maybe a simple button that would reboot node with a simple quick would help many of the user experiencing frequent test failed warnings or other similar issues.

Additional context Feature requested by a provider through Intercom. node ID: 0xd24823c6ef9a33a9f9b20a57ac958d2ce907e47a

Sep
21
1 month ago
Activity icon
issue

isaackielma issue mysteriumnetwork/node

isaackielma
isaackielma

Testnet nodes to join mainnet

Is your feature request related to a problem? Please describe.

"Considering how many nodes the myst network can end up having and also factorting how that would impact earnings for the node runners."

Describe the solution you'd like A clear and concise description of what you want to happen.

"I was thinking if it would be ideal to allow unlimited nodes to join the testnet. All the testnet nodes can join mainnet. However, once mainnet is launched, any new nodes would come at a cost where the node runner must purchase a license to run that node."

Describe alternatives you've considered

"For example, If a testnet node is offline for an extended period of time then it loses its spot. the fee for new nodes are then distributed i guess to the company, the existing node runners, etc...

After each 10 nodes that are purchased, the price of the next 10 nodes is incremented by 1000 Myst tokens

or something of that nature

1 - 10 = 1000 MYST 11-20 = 2000 MYST" ...

Additional context

Suggestion from Telegram User and loyal node runner https://t.me/NickYung

Sep
16
1 month ago
Activity icon
issue

isaackielma issue mysteriumnetwork/node

isaackielma
isaackielma

Payment in progress. It should reach you before 2021-09-07. Not reached yet

Describe the bug Node ID: 0x9cccbc4cd4d02e4d060259945e82cc88b0cc243c

Provider should have been paid on the 7th of the month but still has not been processed

To Reproduce Steps to reproduce the behavior:

  1. Go to 'MMN dashboard'
  2. Click on 'Bounty payout history'
  3. Scroll down to 'September'
  4. See error 'Payment in progress. It should reach you before 2021-09-07'

Expected behavior Ideally payment should have been processed before the 7th of the month.

Screenshots Screenshot 2021-09-16 at 17 17 28

Environment (please complete the following information): OS: Ubuntu 20.04.2 LTS Architecture: linux/amd64 Node version: 0.62.1

Additional context Add any other context about the problem here.

Sep
14
1 month ago
Activity icon
issue

isaackielma issue comment mysteriumnetwork/node

isaackielma
isaackielma

Unable to login into NodeUI (Bad Credentials)

Describe the bug

when using sudo myst reset does not reset it to the default password neither does it redirect the node setting to a onboarding page the problem stays

0x1f6f6e197e645c5ad144819678ec658b03aa9fc2

To Reproduce Steps to reproduce the behavior:

  1. Go to 'NodeUI login page'
  2. See error

Expected behavior NodeUI should either accept password or allow for password reset

Screenshots If applicable, add screenshots to help explain your problem.

Environment (please complete the following information): OS:Raspbian GNU/Linux 10 (buster) Architecture:linux/arm Node version:0.63.0

Additional context same issue and logged #3886 It is solved in 0.62.1 https://github.com/mysteriumnetwork/node/releases/tag/0.62.1

Not resolved for this specific node even after updates.

isaackielma
isaackielma

@etherunit

"Thank you for your assistance.

I have tried using the default password ‘mystberry’ after sudo reset, it still gives bad credential error. Also, I have went into my raspi and checked the password file. The encrypted password in the file matches ‘mystberry’ but somehow it gives me bad credential.

Best regards,

Daniel"

Activity icon
issue

isaackielma issue mysteriumnetwork/node

isaackielma
isaackielma

Unable to login into NodeUI (Bad Credentials)

Describe the bug

when using sudo myst reset does not reset it to the default password neither does it redirect the node setting to a onboarding page the problem stays

0x1f6f6e197e645c5ad144819678ec658b03aa9fc2

To Reproduce Steps to reproduce the behavior:

  1. Go to 'NodeUI login page'
  2. See error

Expected behavior NodeUI should either accept password or allow for password reset

Screenshots If applicable, add screenshots to help explain your problem.

Environment (please complete the following information): OS:Raspbian GNU/Linux 10 (buster) Architecture:linux/arm Node version:0.63.0

Additional context same issue and logged #3886 It is solved in 0.62.1 https://github.com/mysteriumnetwork/node/releases/tag/0.62.1

Not resolved for this specific node even after updates.

Sep
10
1 month ago
Activity icon
issue

isaackielma issue comment mysteriumnetwork/node

isaackielma
isaackielma

Nodes are getting earnings differently on Residential Bounty balance and Global Bounty balance

Describe the bug

Nodes are getting earnings differently on Residential Bounty balance and Global Bounty balance

"I’ve been selling much more residential bandwidth than global, but my country isn’t listed so I’m losing money. Please add Greece or tell me when are you planing to do it." 0x9265e89a23591cff7f22be6c531761c26e21d4b9

To Reproduce Steps to reproduce the behavior:

  1. Go to 'MMN'
  2. Scroll down to 'Bounty balances'
  3. See error (error shown in screenshot below)

Expected behavior Normally nodes tend to reflect the same balance on both Global and residential bounties. However, for a few of the nodes the balances are completely different between the two bounties. Is there a criteria or a reason behind this?

The issue arrises when these providers are not eligible for residential bounty and are eligible for the Global Bounty. However, all of their earnings go to residential bounty balance and since they are not eligible all of their earnings stay there and are never payed.

Screenshots Screenshot 2021-09-10 at 11 28 11

Environment (please complete the following information): OS:Raspbian GNU/Linux 10 (buster) Architecture: linux/arm Node version: 0.62.1

Additional context

Similar balance discrepancies can be seen on the comment section of the issue right below. Screenshot displays about 7 nodes with different balances from Residential and global bounty.

https://github.com/mysteriumnetwork/node/issues/3926

isaackielma
isaackielma

@eugenegoncharuk Is there a way to ensure that provide is only earning global bounty instead. Since Greece isn't in the residential bounty anyways, provider would not get paid for shared bandwidth?

Activity icon
issue

isaackielma issue mysteriumnetwork/node

isaackielma
isaackielma

Avado node provider is stuck on older version. Node cannot update it in order to receive bounty payments

Describe the bug One of our node providers is running a node on Avado box and for some odd reason his node isn't auto updating like the rest of the other Avado nodes in the Network. As seen in the screenshot below provider is still on version 0.41.4, but has no way to update manually unless Avado updates for him.

To Reproduce Steps to reproduce the behavior:

  1. Go to 'MMN'
  2. See node version
  3. Click on 'Bounty Payout History'
  4. See error message 'Leaderboard positions were ineligible for payments'

Expected behavior Normally Avado nodes are expected to auto update whenever our updates become available for the Avado team to update them all.

Screenshots Screenshot 2021-09-10 at 11 36 02

Environment (please complete the following information): OS: Alpine Linux v3.12 Architecture: linux/amd64 Node version: 0.41.4

Additional context This issue was reported last month and was not fully resolved. What happened last month is that we manually payed node provider the amount he deserved, because we agreed that it was not his fault since he could not update the node.

Activity icon
issue

isaackielma issue mysteriumnetwork/node

isaackielma
isaackielma

Nodes are getting earnings differently on Residential Bounty balance and Global Bounty balance

Describe the bug

Nodes are getting earnings differently on Residential Bounty balance and Global Bounty balance

"I’ve been selling much more residential bandwidth than global, but my country isn’t listed so I’m losing money. Please add Greece or tell me when are you planing to do it." 0x9265e89a23591cff7f22be6c531761c26e21d4b9

To Reproduce Steps to reproduce the behavior:

  1. Go to 'MMN'
  2. Scroll down to 'Bounty balances'
  3. See error (error shown in screenshot below)

Expected behavior Normally nodes tend to reflect the same balance on both Global and residential bounties. However, for a few of the nodes the balances are completely different between the two bounties. Is there a criteria or a reason behind this?

The issue arrises when these providers are not eligible for residential bounty and are eligible for the Global Bounty. However, all of their earnings go to residential bounty balance and since they are not eligible all of their earnings stay there and are never payed.

Screenshots Screenshot 2021-09-10 at 11 28 11

Environment (please complete the following information): OS:Raspbian GNU/Linux 10 (buster) Architecture: linux/arm Node version: 0.62.1

Additional context

Similar balance discrepancies can be seen on the comment section of this issue. Screenshot displays about 7 nodes with different balances from Residential and global bounty.

https://github.com/mysteriumnetwork/node/issues/3926

Sep
9
1 month ago
Activity icon
issue

isaackielma issue mysteriumnetwork/node

isaackielma
isaackielma

MMN and NodeUI not reflecting earnings nor data transferred

Describe the bug MMN and NodeUI not reflecting earnings nor data transferred as it previously was before. No update or changes were done to the node

To Reproduce Steps to reproduce the behavior:

  1. Go to 'MMN or Node UI'
  2. See error

Expected behavior Normally dashboards should either keep their previous information or accumulate MYST and data transferred.

Screenshots Screenshot 2021-09-09 at 07 55 32 Screenshot 2021-09-09 at 07 55 21

Environment (please complete the following information): OS: Ubuntu 20.04.3 LTS Architecture: linux/amd64 Node version: 0.62.1

Sep
3
1 month ago
Activity icon
issue

isaackielma issue mysteriumnetwork/node

isaackielma
isaackielma

Node UI not reflecting earnings and sessions

Describe the bug Node UI not reflecting earnings and sessions MMN dashboard is updated and reflecting earnings and sessions correctly. However, node ui is not at all

0xeeb7f1ade35da77b096c47430452a18d53c9f14d after node updated to latest version

To Reproduce Steps to reproduce the behavior:

  1. Go to 'NodeUI Dashboard'
  2. See error

Expected behavior NodeUI should be reflecting same information as MMN is.

Screenshots

Screenshot 2021-09-03 at 14 58 03 Screenshot 2021-09-03 at 15 14 27 Screenshot 2021-09-03 at 15 14 40 Screenshot 2021-09-03 at 15 14 53 Screenshot 2021-09-03 at 15 15 04 Screenshot 2021-09-03 at 15 15 16

Environment (please complete the following information): OS: Ubuntu 20.04.3 LTS Architecture: linux/amd64 Node version: 0.62.1

Additional context Add any other context about the problem here.

Activity icon
issue

isaackielma issue mysteriumnetwork/node

isaackielma
isaackielma

Stuck on node version 0.46.2-rc0 in my.mysterium.network despite updating both nodes

Describe the bug 0x8db0575a165f780ebee4eb23976ad23f49f6e69f 0x28e13d5d3c47e93da4bdeb0f2ac94f256bd6ab03

Nodes are being unsuccessfully updated. tried and still showing on my.myst.network as being on the old node on both raspberry pis.

To Reproduce Steps to reproduce the behavior:

Heres the results of that command: [email protected]:~ $ sudo -E bash -c "$(curl -s https://raw.githubusercontent.com/mysteriumnetwork/node/master/install.sh)"

Detecting platform

System info: OS: linux Distribution: raspbian Version codename: buster

Detecting platform - done

Installing myst & dependencies

Executing: /tmp/apt-key-gpghome.WESaXZFBwF/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys 04EE7237B7D453EC gpg: key E0B11894F66AEC98: "Debian Archive Automatic Signing Key (9/stretch) [email protected]" not changed gpg: Total number processed: 1 gpg: unchanged: 1 Executing: /tmp/apt-key-gpghome.hl0sMAyoXp/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys 648ACFD622F3D138 gpg: key DC30D7C23CBBABEE: "Debian Archive Automatic Signing Key (10/buster) [email protected]" not changed gpg: Total number processed: 1 gpg: unchanged: 1 Get:1 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB] Get:2 http://deb.debian.org/debian buster-backports InRelease [46.7 kB] Get:3 http://archive.raspberrypi.org/debian buster InRelease [32.6 kB] Get:4 http://deb.debian.org/debian unstable InRelease [165 kB] Hit:5 http://ppa.launchpad.net/mysteriumnetwork/node/ubuntu focal InRelease Get:6 http://deb.debian.org/debian buster-backports/main armhf Packages [476 kB] Get:7 http://archive.raspberrypi.org/debian buster/main armhf Packages [378 kB] Get:8 http://deb.debian.org/debian unstable/main armhf Packages [8,428 kB] Get:9 http://deb.debian.org/debian unstable/main Translation-en [6,519 kB] Fetched 16.1 MB in 25s (632 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: raspberrypi-kernel-headers 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 27.7 MB of archives. After this operation, 180 MB of additional disk space will be used. Get:1 http://archive.raspberrypi.org/debian buster/main armhf raspberrypi-kernel-headers armhf 1:1.20210805-1 [27.7 MB] Fetched 27.7 MB in 3s (8,515 kB/s) Selecting previously unselected package raspberrypi-kernel-headers. (Reading database ... 40800 files and directories currently installed.) Preparing to unpack .../raspberrypi-kernel-headers_1%3a1.20210805-1_armhf.deb ... Unpacking raspberrypi-kernel-headers (1:1.20210805-1) ... Setting up raspberrypi-kernel-headers (1:1.20210805-1) ... Executing: /tmp/apt-key-gpghome.fwEdYcRqBb/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys ECCB6A56B22C536D gpg: key ECCB6A56B22C536D: "Launchpad PPA for Mysterium Network" not changed gpg: Total number processed: 1 gpg: unchanged: 1 Hit:1 http://ppa.launchpad.net/mysteriumnetwork/node/ubuntu focal InRelease Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease Hit:3 http://deb.debian.org/debian buster-backports InRelease Hit:4 http://deb.debian.org/debian unstable InRelease Hit:5 http://archive.raspberrypi.org/debian buster InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. Reading package lists... Done Building dependency tree Reading state information... Done myst is already the newest version (0.53.2+build348501509+focal). wireguard is already the newest version (1.0.20200827-1~bpo10+1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Installing myst & dependencies - done

Installation complete!

Expected behavior Node would update normally after running commands

Screenshots

Screenshot 2021-09-03 at 11 34 51

Environment (please complete the following information): System info: Device: Pi 3b OS: linux Distribution: raspbian Version codename: buster

Additional context Provider's comment "ive got over 100 myst tokens I cannot collect though no fault of my own"

Sep
1
1 month ago
Activity icon
issue

isaackielma issue mysteriumnetwork/mysterium-vpn-desktop

isaackielma
isaackielma

Unable to update bug reports in app

Describe the bug When going under help tab to submit an error in the logs app will not succeed with sending the report via app. Report has to be sent manually then.

To Reproduce Steps to reproduce the behavior:

  1. Go to 'help'
  2. Submit bug report
  3. Click on 'send'
  4. See error

Expected behavior Upon trying to submit logs via app. Error apppears

Logs Attach logs (app, node, supervisor) to the issue. Where to find the logs: https://github.com/mysteriumnetwork/mysterium-vpn-desktop#logs

Screenshots Screenshot 2021-08-29 at 08 50 48

Desktop (please complete the following information):

  • OS: MAC
  • App Version 6.0.0

Files:

main.log

renderer.log

Aug
21
2 months ago
Activity icon
issue

isaackielma issue comment mysteriumnetwork/node

isaackielma
isaackielma

Nodes not displaying specific countries on MMN. Location Unknown

Describe the bug Nodes not displaying specific countries on MMN dashboard. Location Unknown is being displayed.

Paramba- 0xe974018de1605a366f9de33c74d32599009d7701 ——> USA ABCMine- 0x65ee793880ca381ae3c7d00f09abfcaf2e954a5b ——> Russia Sonu Adhikari- 0x3baabcea9723f7db82a9be1f1ce53021568d8ac4 ——> India

To Reproduce Steps to reproduce the behavior:

  1. Go to 'MMN'
  2. See on dashboard
  3. See error

Expected behavior Dashboard should be displaying respective countries.

Screenshots Visual Example:

2021-08-04 17 05 43

Environment (please complete the following information): OS: Ubuntu 20.04.2 LTS Architecture: linux/amd64 Node version: 0.52.0

OS: Alpine Linux v3.12(docker) Architecture: linux(docker)/amd64 Node version: 0.53.1

Possibly other environments as well (will request other users with same issue to include their respective environments).

isaackielma
isaackielma

0x7de3cab9b70a3308de07cddd22c383538bb4d09b - USA

Aug
19
2 months ago
Activity icon
issue

isaackielma issue comment mysteriumnetwork/node

isaackielma
isaackielma

Nodes not displaying specific countries on MMN. Location Unknown

Describe the bug Nodes not displaying specific countries on MMN dashboard. Location Unknown is being displayed.

Paramba- 0xe974018de1605a366f9de33c74d32599009d7701 ——> USA ABCMine- 0x65ee793880ca381ae3c7d00f09abfcaf2e954a5b ——> Russia Sonu Adhikari- 0x3baabcea9723f7db82a9be1f1ce53021568d8ac4 ——> India

To Reproduce Steps to reproduce the behavior:

  1. Go to 'MMN'
  2. See on dashboard
  3. See error

Expected behavior Dashboard should be displaying respective countries.

Screenshots Visual Example:

2021-08-04 17 05 43

Environment (please complete the following information): OS: Ubuntu 20.04.2 LTS Architecture: linux/amd64 Node version: 0.52.0

OS: Alpine Linux v3.12(docker) Architecture: linux(docker)/amd64 Node version: 0.53.1

Possibly other environments as well (will request other users with same issue to include their respective environments).

isaackielma
isaackielma

0x7de3cab9b70a3308de07cddd22c383538bb4d09b - USA

Previous