You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IF you configure headerscache once WM starts up it reports 'detected pruned node, disabling fast cache', which is wierd because the node behind it is a full-node. This is likely because of the failover method. I would suggest either allowing this via HC with the node as the backend, or allow a specific fast-sync backend to be configured.
The text was updated successfully, but these errors were encountered:
IF you configure headerscache once WM starts up it reports 'detected pruned node, disabling fast cache', which is wierd because the node behind it is a full-node. This is likely because of the failover method. I would suggest either allowing this via HC with the node as the backend, or allow a specific fast-sync backend to be configured.
The text was updated successfully, but these errors were encountered: