Here are common network ports SolarNode devices rely on, which can be used to configure firewalls if necessary.

For normal operations, SolarNode does not need any inbound connections from the public internet. You might want to configure a firewall/router to forward some ports to SolarNode if you want to be able to remotely manage the node. You can also remotely manage the node without requiring any inbound connections by deploying SolarSSH.

Ports	Protocol	Description
22	TCP	SSH administration
80, 8080	TCP	SolarNode web admin GUI

The following table shows the common network connections made by SolarNode to the public internet. Not all connections are required for normal operations. For example, the HTTP package connections are only required to perform OS package updates, and the MQTT connections are only necessary if SolarNode is configured to post data via MQTT.

Ports	Protocol	Destination	Description
80	TCP	archive.raspberrypi.org	HTTP packages (Raspberry Pi based nodes)
80	TCP	raspbian.raspberrypi.org	HTTP packages (Raspberry Pi based nodes)
80, 443	TCP	debian.repo.solarnetwork.org.nz	HTTP packages (Debian based nodes)
123	UDP	0.debian.pool.ntp.org, 1.debian.pool.ntp.org, 2.debian.pool.ntp.org, 3.debian.pool.ntp.org	NTP time synchronisation (Debian based nodes)
443	TCP	in.solarnetwork.net	HTTP posting of data
8022	TCP	ssh.solarnetwork.net	SSH node management
8883	TCP	queue.solarnetwork.net	MQTT posting of data
8884	TCP	influx.solarnetwork.net	MQTT posting of data