Network Requirements

Smart Panel relies on local network communication to discover and control your devices. This page explains what your network needs to support for everything to work properly.

Required Ports

Port	Protocol	Service	Required?
3000	TCP	Backend HTTP server & Admin UI	Yes
5353	UDP	mDNS (`.local` hostname resolution)	Recommended
Various	TCP	WebSocket connections to devices	Yes

Port 3000 is the default. You can change it via the FB_BACKEND_PORT environment variable or in your docker-compose.yml configuration.

mDNS (Multicast DNS)

Smart Panel uses mDNS for three purposes:

Hostname resolution — so you can access http://smart-panel.local:3000 from your browser
Device discovery — plugins like Shelly use mDNS to automatically find devices on the network
Display → server discovery — in multi-display setups, panel displays use mDNS to automatically find Smart Panel servers on the network (no manual URL entry needed)

Requirements for mDNS

Devices must be on the same subnet (same VLAN / broadcast domain)
Your router must allow multicast traffic on UDP port 5353
On Windows, you may need Bonjour installed

Common mDNS issues

Problem	Cause	Solution
`.local` domain doesn’t resolve	mDNS not supported on client	Use the IP address directly instead
Shelly devices not discovered	Devices on different VLAN	Move devices to the same subnet as Smart Panel
Intermittent discovery	Router blocking multicast	Enable IGMP snooping or allow multicast on the network

Many home networks with IoT VLANs or guest network isolation will block mDNS traffic between segments. If you use network segmentation, ensure Smart Panel and your IoT devices share the same broadcast domain, or configure an mDNS reflector/repeater.

Firewall Configuration

If you run a firewall on the Raspberry Pi (e.g., UFW), allow the required ports:


sudo ufw allow 3000/tcp comment "Smart Panel"
sudo ufw allow 5353/udp comment "mDNS"

Device Communication

Each integration plugin has its own network requirements (mDNS, WebSocket, HTTP, MQTT, etc.). See the Extensions section for details on specific integrations.

Reverse Proxy

If you run Smart Panel behind a reverse proxy (nginx, Caddy, etc.), you must forward WebSocket connections:


location / {
    proxy_pass http://localhost:3000;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_set_header Host $host;
}

Without WebSocket forwarding, the panel display will not receive real-time updates from the backend.

What’s Next?

Continue to Installation to set up Smart Panel
See the Troubleshooting guide if you’re having connectivity issues