shardeum / bug-reporting

59 stars 35 forks source link

Dashboard error and staking unsuccessfully/error #929

Open ScapeXYZ opened 15 hours ago

ScapeXYZ commented 15 hours ago
What is the issue? I had run my node previously and get my dashboard with my staking SHM and reward increases suddenly I'm unable to login my dashboard getting "timeout" error. and stop me logging.

I tried back to run the node and got the dashboard back but no more reward, staking SHM from previously dashboard and my node continue stopping anytime after an hours

:red_circle: Describe the error in simple terms. : Staking unsuccessfully/error. No validator syncing

What impact does the issue have?

The bug leads to failures in critical features, causing error messages or unexpected behaviors.

Examples include crashes, data loss, failure to load components, or incorrect output that prevents users from achieving their objectives.

Often requires immediate attention and resolution to restore normal operation.

:red_circle: Describe if the bug is a visual warning or if it breaks functionality causing a system to fail. :red_circle: This kind bug will prevent many user to complete the task or using the system

How to reproduce the issue?

IMG-20241021-WA0033 20241001_225343

:red_circle: Explain in as much detail as possible to help reproduce the bug:

    -where the error is seen? I'm my dashboard 
    -how the error was potentially caused if possible (mention previous steps taken to see the error if relevant). I tried to restart my docker and even the node
    -share code and explain how the code was run

:red_circle:

What other resources can you share regarding this issue? I've shared my previously and healthy of my dashboard before it's crash and the new dashboard I got .

:red_circle: Photos and links related to the error. :red_circle:

Julietnacy commented 12 hours ago

@ScapeXYZ It seems like you're facing several issues with your node and staking dashboard. Ensure that your internet connection is stable. An unstable connection can cause "timeout" errors.