If you find a problem with the Lite Node on your system, please report the relevant console output, the results of diode-node.info, the results of snap get diode-node, and the logs from snap logs diode-node
ulimit problem → in v1.5.16 and earlier, the node always sets ulimit to 120,000 TCP connections. If your system has ulimit set to a small maximum connections, the node will not start. in v1.15.17 and later, the node sets ulimit tcp max to the system max instead. Be aware that your node’s performance may suffer if you restrict TCP connections too much.
rpc connection problem → in v1.15.16 and earlier, there would sometimes be an RPC connection error that was a result of the system hostname being changed without a reboot. In v.1.15.17 and later, the node detects a changed hostname and uses the updated name even without a reboot.
port conflicts → you can set the ports your node uses in case you are running it on a box/vm that already uses the default ports.
checkout snap get diode-node - this shows how to change all ports
that said these are very important ports you shouldn’t remove:
- 8545 - is used for network uptime monitoring. so if your node doesn’t respond it’s considered dead
- 41046 - this is the primary device port, all devices will check this one first. not having this port will still allow devices to connect but the likelihood is very much reduced.
IP address or port not externally accessible → very often, if your node’s dashboard shows an error / connection problem it is because your node is not actually externally accessible. This is not a Diode issue per se, it is more of a system/network configuration issue. Whereas a “virtual machine” in a data center will nearly always work (as long as your firewall rules are open), a box in your house will ALWAYS require router configuration. And, even if you correctly configure your router, your ISP still may not allow inbound connections. So, you may be stuck. Read on to get some tips.
If your ISP does allow inbound connections, then it will just be a process of port forwarding through your router. Here is an example of someone who sorted that out in Brazil with a ZTE router. Also, if you are running the node in a virtual environment (e.g. docker, wsl, etc…) on your box, then you may also have to make sure that virtual environment is allowing communications in.
Here are some tips for how to test if your machine is accessible to the open world:
-
go to your node’s dashboard - e.g. Diode™ Network
-
find the Primary Edge Address box - that is where other nodes will try to find your node and route data to it. It looks like:
-
Copy the IP address and port there
-
In a terminal window on Mac or Linux (or Windows if you have the right tools), type:
curl -v telnet://147.160.139.55:41046
You should get back something like:
-
Do this for any port that the dashboard is warning you that it can’t connect to
NOTE: You can also use tools like ping, nc (netcat), or nmap to try to connect. e.g.:
Use ping to see if the server is alive (however, sometimes servers or ISPs block pings):
> ping 147.160.139.55
PING 147.160.139.55 (147.160.139.55): 56 data bytes
64 bytes from 147.160.139.55: icmp_seq=0 ttl=52 time=68.893 ms
Use netcat to test a particular port:
> nc -zv -w 5 147.160.139.55 41046
Connection to 147.160.139.55 port 41046 [tcp/*] succeeded!
Use nmap to scan a range of ports:
> nmap 147.160.139.55 -p 1-1000
Starting Nmap 7.95 ( https://nmap.org ) at 2025-04-18 11:02 PDT
Nmap scan report for 147.160.139.55
Host is up (0.061s latency).
Not shown: 990 closed tcp ports (conn-refused)
PORT STATE SERVICE
22/tcp open ssh
25/tcp filtered smtp
135/tcp filtered msrpc
136/tcp filtered profile
137/tcp filtered netbios-ns
138/tcp filtered netbios-dgm
139/tcp filtered netbios-ssn
443/tcp open https
445/tcp filtered microsoft-ds
993/tcp open imaps
Node is not getting any traffic → Sometimes, in higher node density areas, the network will not route traffic to your node because there are other nodes already with good enough performance around you. So, if you’ve verified the node is usable (e.g. forced a connection to it using somethinng like diode -diodeaddrs={ip}:41046), but your node is still not getting any traffic, you can try publishing a small webpage via the node and then accessing the web page via the Web2 gateway. Sometimes, after the network has connected clients via your node, it will start routing other public traffic to your node.
- run a web server
npm install -g http-server
cd myprojectfolder
echo "hello world" > index.html
http-server
diode -diodeaddrs={ip}:41046 publish -public 80:80
- access the web page
In the previous step, look for “INFO HTTP Gateway Enabled” → the link after the : is where you can view your site from a web browser.