StreamR Node Invisible in the operators dashboard, while the node is running

[sxiii]

Node is running and with debug logging I'm seeing a lot of different activity. However, in the dashboard, I don't see it. (5000 DATA is staked and 20 MATIC is available). Firewall is open, port forwarding on the router is added (some other crypto nodes work without any issues). Docker port forwarding should also be OK.

sudo docker logs streamr | grep error
...
TRACE [2024-06-10T05:43:22.092] (RecursiveOperationRpcRemo): Next hop responded with error 1
TRACE [2024-06-10T05:43:23.441] (DhtNodeRpcRemote         ): getClosestPeers error layer1::0xd683f37ca8807d352e8d6241be1ee211452e2766/operator/coordination#0 
TRACE [2024-06-10T05:43:23.442] (DhtNodeRpcRemote         ): getClosestPeers error layer1::0xd683f37ca8807d352e8d6241be1ee211452e2766/operator/coordination#0 
TRACE [2024-06-10T05:43:25.834] (RecursiveOperationRpcRemo): Next hop responded with error 1
TRACE [2024-06-10T05:43:25.978] (RecursiveOperationRpcRemo): Next hop responded with error 1
...
TRACE [2024-06-10T05:43:43.698] (AbstractWebsocketClientCo): WebSocket Client error: WebSocket was closed before the connection was established 
    error: {}
TRACE [2024-06-10T05:43:56.241] (RecursiveOperationRpcRemo): Next hop responded with error 1
...
TRACE [2024-06-10T05:44:44.711] (RecursiveOperationRpcRemo): Next hop responded with error 0
TRACE [2024-06-10T05:44:44.767] (RecursiveOperationRpcRemo): Next hop responded with error 0
TRACE [2024-06-10T05:44:45.371] (RecursiveOperationRpcRemo): Next hop responded with error 1
TRACE [2024-06-10T05:44:45.485] (RecursiveOperationRpcRemo): Next hop responded with error 1
TRACE [2024-06-10T05:44:54.457] (AbstractWebsocketClientCo): WebSocket Client error: WebSocket was closed before the connection was established 
    error: {}
TRACE [2024-06-10T05:45:00.313] (AbstractWebsocketClientCo): WebSocket Client error: connect EHOSTUNREACH 84.189.44.192:32200 
    error: {
TRACE [2024-06-10T05:45:06.483] (RecursiveOperationRpcRemo): Next hop responded with error 1
TRACE [2024-06-10T05:45:10.654] (RecursiveOperationRpcRemo): Next hop responded with error 1
TRACE [2024-06-10T05:45:10.866] (AbstractWebsocketClientCo): WebSocket Client error: connect EHOSTUNREACH 84.189.44.192:32200 
    error: {
TRACE [2024-06-10T05:45:11.918] (RecursiveOperationRpcRemo): Next hop responded with error 1
...

I'm randomly guessing that either 84.189.44.192:32200 is another node or maybe it's the parser node that checks status and I can't talk to it for some reason? Btw, it's pingable.

But I'm not sure if these errors have something to do with node invisibility or not.

Please help!
Thanks.
Den