Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

100% time Offline, 100% time Idle reported in UI #6000

Open
PaJaSoft opened this issue Mar 3, 2024 · 3 comments
Open

100% time Offline, 100% time Idle reported in UI #6000

PaJaSoft opened this issue Mar 3, 2024 · 3 comments
Labels

Comments

@PaJaSoft
Copy link

PaJaSoft commented Mar 3, 2024

Using Node version: 1.29.8 and Node UI version: 2.15.0 (Windows Native installation), but probably it isn't only in this release.

UI reports in Statistics (Last 24 hours) 100% Ofline and 100% Idle although connections have been flowing without any issue and there was no service or network outage on that node and 500Mbps network for over one week.

In contrary Dashboard reports 'Online -> green point', ' Quality -> green point' but Myst cli:

  • healthcheck -> fine
  • nat -> Monitoring Status: "success"
  • status -> "Status:NotConnected"

all of the time...:-(

@PaJaSoft PaJaSoft added the bug label Mar 3, 2024
@ZygintasBudrys
Copy link

Severity: low
Priority: low

@nightcrawlerbr
Copy link

nightcrawlerbr commented Mar 9, 2024

I have the same issue. Node works fine, connections flow, but UI reports 100% offline and 100% iddle. Last 3 versions. Node 1.29.9. UI 2.15.1. The same happens for last 3 versions of Node (didn't check UI, watchtower upgraded automatically). Running on Docker (Alpine host). No outages and still every report is 100% offline and iddle.

PS: Now it says -270138% Idle and 270238% connected.

@ZygintasBudrys
Copy link

Will be solved with another ticket:
https://github.com/mysteriumnetwork/mystnodes/issues/176/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants