RPC Error, dashboard not loading

Hi,

I’ve been running a few nodes running for a long time and I never had this issue before. Couple of days ago I added a new node but I can’t load the dashboard and the node is not getting any traffic.

Saw an old thread about a similar issue which in theory was fixed long time ago.
Something related to hostname change without a reboot (?)
I did a reboot and my hostname resolve properly.

See error and node. info below:

@Knusperhaus someone told me on Discord you might be able to assist :slight_smile:

2025-12-17T11:32:28Z diode-node.service[661]: 11:32:28.130 [error] Network.Rpc: ErlangError %FunctionClauseError{module: DiodeClient.Base16, function: :decode_int, arity: 1, kind: nil, args: nil, clauses: nil} in {"dio_traffic", [1284]}: [{DiodeClient.Base16, :decode_int, [nil], [file: ~c"lib/diode_client/base16.ex", line: 76]}, {Network.Rpc, :execute_dio, 2, [file: ~c"lib/network/rpc.ex", line: 300]}, {Network.Rpc, :execute, 2, [file: ~c"lib/network/rpc.ex", line: 100]}, {Network.Rpc, :handle_jsonrpc, 2, [file: ~c"lib/network/rpc.ex", line: 53]}, {Network.RpcHttp, :"-do_match/4-fun-3-", 2, [file: ~c"lib/network/rpc_http.ex", line: 37]}, {Network.RpcHttp, :"-dispatch/2-fun-0-", 4, [file: ~c"deps/plug/lib/plug/router.ex", line: 246]}, {:telemetry, :span, 3, [file: ~c"/build/diode-node/parts/diode-node/build/deps/telemetry/src/telemetry.erl", line: 324]}, {Network.RpcHttp, :dispatch, 2, [file: ~c"deps/plug/lib/plug/router.ex", line: 242]}, {Network.RpcHttp, :plug_builder_call, 2, [file: ~c"lib/network/rpc_http.ex", line: 4]}, {Plug.Cowboy.Handler, :init, 2, [file: ~c"lib/plug/cowboy/handler.ex", line: 11]}, {:cowboy_handler, :execute, 2, [file: ~c"/build/diode-node/parts/diode-node/build/deps/cowboy/src/cowboy_handler.erl", line: 37]}, {:cowboy_stream_h, :execute, 3, [file: ~c"/build/diode-node/parts/diode-node/build/deps/cowboy/src/cowboy_stream_h.erl", line: 310]}, {:cowboy_stream_h, :request_process, 3, [file: ~c"/build/diode-node/parts/diode-node/build/deps/cowboy/src/cowboy_stream_h.erl", line: 299]}, {:proc_lib, :init_p_do_apply, 3, [file: ~c"proc_lib.erl", line: 329]}]
andrea@racknrd01:/var/snap/diode-node/437/nodedata_prod$ sudo diode-node.info
[sudo] password for andrea:
== Diode Node 0xc11c5b2ca5e1ca8bab178ce580c336f4821e5ada ==
Name             : forget_just@racknrd01
Version          : 1.7.16
Accountant       : nil
Uptime           : 10375
Connected Devices: 0
Connected Peers  : 171

Current Epoch    : 681
Ticket Score     : 385934336

Previous Epoch   : 680
Ticket Score     : 0

Dashboard        : https://diode.io/network/#/node/0xc11c5b2ca5e1ca8bab178ce580c336f4821e5ada

andrea@racknrd01:/var/snap/diode-node/437/nodedata_prod$ sudo snap get diode-node
Key                Value
data-dir           /var/snap/diode-node/437/nodedata_prod
default-peer-list  diode://0xceca2f8cf1983b4cf0c1ba51fd382c2bc37aba58@us1.prenet.diode.io:51055 diode://0x7e4cd38d266902444dc9c8f7c0aa716a32497d0b@us2.prenet.diode.io:51055 diode://0x68e0bafdda9ef323f692fc080d612718c941d120@as1.prenet.diode.io:51055 diode://0x1350d3b501d6842ed881b59de4b95b27372bfae8@as2.prenet.diode.io:51055 diode://0x937c492a77ae90de971986d003ffbc5f8bb2232c@eu1.prenet.diode.io:51055 diode://0xae699211c62156b8f29ce17be47d2f069a27f2a6@eu2.prenet.diode.io:51055
edge2-port         41046,443,993,1723,10000
host               XX.11.153.147
log-level          debug
peer2-port         51055
private            0
rpc-port           8545
rpcs-port          8443

andrea@racknrd01:/var/snap/diode-node/437/nodedata_prod$ hostname -f
racknrd01

andrea@racknrd01:/var/snap/diode-node/437/nodedata_prod$ ping -c1 racknrd01
PING racknrd01 (127.0.0.1) 56(84) bytes of data.
64 bytes from racknrd01 (127.0.0.1): icmp_seq=1 ttl=64 time=0.044 ms

--- racknrd01 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.044/0.044/0.044/0.000 ms

GM Agarbato! It looks like we had a temporary outage on the dashboard, but it’s back up and running now. Let us know if you have any other issues, happy to help.

Hi @Maliah .

I was referring to node dashboard not points dashboard, it’s a different issue.

Node dashboard still not working:

Thanks

Andrea

Dash is ok now, thanks for info on the potential node issue. Will revert…

Heya @agarbato so, I looked into this, the error is due to a client on the network that is sending a proxy request with null values for its epoch and/or its chain_id_param → it is not actually a functional issue with your node.

Your node is working fine as I can see by doing this with the CLI:

diode -diodeaddrs=72.11.153.147:41046 time

(see How do I know if my new Lite Node is working? ).

That being said, some dashboards (e.g. yours: Diode™ Network ) don’t fully render the connection graph - we are checking on why that is. It is possible the reason that the dashboard doesn’t fully load may also be impacting your ability to organically attract traffic, but it is unlikely the issue is directly with your node.

1 Like

Hi,

Thanks for checking the error.

Node is been up for 3-4 days but didn’t get any traffic at all and it’s very unlikely.

I’m afraid the dashboard error is impacting the node ability to get traffic.

I tried to reinstall the node (just kept wallet* files) as I have 10DIODE but I still get the same error:

2025-12-19T09:43:52Z diode-node.service[403889]: 09:43:52.735 [error] Network.Rpc: ErlangError %FunctionClauseError{module: DiodeClient.Base16, function: :decode_int, arity: 1, kind: nil, args: nil, clauses: nil} in {“dio_traffic”, [1284]}: [{DiodeClient.Base16, :decode_int, [nil], [file: ~c"lib/diode_client/base16.ex", line: 76]}, {Network.Rpc, :execute_dio, 2, [file: ~c"lib/network/rpc.ex", line: 300]}, {Network.Rpc, :execute, 2, [file: ~c"lib/network/rpc.ex", line: 100]}, {Network.Rpc, :handle_jsonrpc, 2, [file: ~c"lib/network/rpc.ex", line: 53]}, {Network.RpcHttp, :“-do_match/4-fun-3-”, 2, [file: ~c"lib/network/rpc_http.ex", line: 37]}, {Network.RpcHttp, :“-dispatch/2-fun-0-”, 4, [file: ~c"deps/plug/lib/plug/router.ex", line: 246]}, {:telemetry, :span, 3, [file: ~c"/build/diode-node/parts/diode-node/build/deps/telemetry/src/telemetry.erl", line: 324]}, {Network.RpcHttp, :dispatch, 2, [file: ~c"deps/plug/lib/plug/router.ex", line: 242]}, {Network.RpcHttp, :plug_builder_call, 2, [file: ~c"lib/network/rpc_http.ex", line: 4]}, {Plug.Cowboy.Handler, :init, 2, [file: ~c"lib/plug/cowboy/handler.ex", line: 11]}, {:cowboy_handler, :execute, 2, [file: ~c"/build/diode-node/parts/diode-node/build/deps/cowboy/src/cowboy_handler.erl", line: 37]}, {:cowboy_stream_h, :execute, 3, [file: ~c"/build/diode-node/parts/diode-node/build/deps/cowboy/src/cowboy_stream_h.erl", line: 310]}, {:cowboy_stream_h, :request_process, 3, [file: ~c"/build/diode-node/parts/diode-node/build/deps/cowboy/src/cowboy_stream_h.erl", line: 299]}, {:proc_lib, :init_p_do_apply, 3, [file: ~c"proc_lib.erl", line: 329]}]

I’ll leave the node running for now,

The node is Toronto Canada and I think it has value for the network so I don’t want to give up just yet :slight_smile:
Let me know if there’s anything I can do to help troubleshooting.

Appreciate the help.

Thanks

Andrea

Thanks for hanging in there - we found the issue. Moonbeam has been sloughing RPC nodes, and your node (and others!) were getting stuck due to caching a validated RPC node that then went tharn/offline. We have a fix coming.

Hi, any update on this? My node been up 24/7 for over a week and nothing changed. Didn’t get a single byte of traffic. I’ll decommission the node on the next epoch and start over unless you have a different suggestion.
Thanks
Andrea

1 Like

Hey Agarbato, Merry Christmas - we have prepared a new edge version 1.7.18 that should address your issue. The core issue is though that your node is not receiving new Moonbeam blocks – this might happen when multiple nodes are sharing the same ip as many of the public rpc providers limit the traffic per ip.

I was having similar issues with getting the RPC error. I had it happen on 2 brand new installs. The machines are completely unrelated, just for info. The only thing “related” would be that they both run flavors of Ubuntu.

What’s happening looks like diode-node is crashing immediately upon launch and gets caught in a loop of attempting to restart. I found out that it seems to be trying to call/access a directory which doesn’t exist, thus causing this loop. I’m guessing on older versions, the snap package created the directory automatically, but this one isn’t.

Once I created the directory manually and then restarted the node, it worked immediately and has been running without issue.

These are the commands I ran to successfully get it to work:

sudo snap stop diode-node
sudo mkdir -p /var/snap/diode-node/461/nodedata_prod
sudo chown -R root:root /var/snap/diode-node/461/
sudo snap start diode-node

The path creation issue on new installs has been fixed in v1.8.5rolling out now via edge.