Beacon stall?

[Silvercap718]

Anyone else getting this message on the node monitor?

[Jared]

Hello @Silvercap718,

If it is a pNode please follow these instructions:

Official pNode Troubleshooting Guide

It’s finally here! The official pNode troubleshooting guide. No longer do you have to search around the forum for answers to your questions. Use the Node Monitor to check for issues (monitor.incognito.org). When you see an issue come here to fix it. Step 1 - Restart Docker Sometimes the Docker container may get stuck. Restarting it is as easy as sending a URL in a web browser. Please note you will have to change the following "pNode_IP_Address" "pNode_QR_Code" You can find your QR…

If it is a vNode please follow these instructions:

Official vNode Troubleshooting Guide

It’s finally here! The official vNode troubleshooting guide. No longer do you have to search around the forum for answers to your questions. Use the Node Monitor to check for issues (monitor.incognito.org). When you see an issue come here to fix it. This guide assumes you have followed the official installation/setup method for your vNode(s) which can be found here: How to setup your own node in a blink of an eye (Now support multi-nodes per host) If an alternative installation/setup m…

If you have any questions please let me know. I’d be more than happy to assist you.

[sysfu]

Yes, I just noticed this today, I have no idea how long the message has been there. My pNode has been consistently earning three times about month for about three months so I didn’t think it had any issues.

[Jared]

Prior to slashing all nodes earned, even nodes that are offline / not synced.

In order to better secure the network and prepare for expansion, slashing was implemented to ensure only healthy nodes are operating on the network.