As of version 1.21.35, the Hivenet Agent no longer uses UPNP (Universal Plug and Play) for automatic port forwarding.
This means the agent no longer requests your router to open ports automatically, which may affect connectivity, especially if you're behind NAT (Network Address Translation).
How does this affect me?
If you updated to 1.21.35, you may notice:
✅ Your agent is still working fine if your network allows outgoing connections.
❌ Your agent fails to connect if your router or firewall previously relied on UPNP to open ports automatically.
❌ Your agent only listens on port 4443, whereas before it used both 4001 and 4443.
How to check if your agent is connected
To check if your agent is running and which ports are open, run:
sudo ss -tulpn | grep hive
This should return an output similar to:
tcp LISTEN 0 4096 0.0.0.0:4443 0.0.0.0:* users:("hive-agent",pid=2046556,fd=54) udp UNCONN 0 0 0.0.0.0:57659 0.0.0.0:* users:("hive-agent",pid=2046556,fd=51)🔍 What this means:
If 4443 is present, your agent is listening for incoming connections on this port.
If 4001 is missing, the agent no longer requires it or it only activates under certain conditions.
Check if the agent is running:
systemctl status hive-agent
Check logs for connection errors:
journalctl -u hive-agent --no-pager | tail -n 50
How to fix connection issues
If your agent isn’t connecting after updating, follow these steps:
1. Open required ports in your firewall
Make sure your system firewall allows the following:
sudo ufw allow 4443/tcp sudo ufw allow 57659/udp
If using iptables, run:
sudo iptables -A INPUT -p tcp --dport 4443 -j ACCEPT sudo iptables -A INPUT -p udp --dport 57659 -j ACCEPT
2. Manually configure port forwarding on your router
If your router does not allow outgoing connections, you may need to set up manual port forwarding:
Go to your router settings (
192.168.x.1in most cases).Locate the port forwarding section.
Add the following rules:
TCP 4443 → Your device’s local IP (e.g., 192.168.1.100)
UDP 57659 → Your device’s local IP
✅ Tip: If your agent previously worked without manual setup, your router may have relied on UPNP. Now, it must be configured manually.
3. Restart your agent & verify connectivity
After updating your settings, restart the agent:
sudo systemctl restart hive-agent
Then check if it’s running:
systemctl status hive-agent
What if my agent still doesn’t work?
If you’ve followed the steps above and still experience connectivity issues:
Check if your ISP blocks certain ports. Some internet providers restrict incoming connections, making it difficult to run an agent behind a NAT.
Try a VPN or relay service. If your ISP blocks connections, using a VPN may help bypass restrictions.
Check for future updates. The Hivenet team is actively improving network configurations in future releases.
For additional help, send us a mail at [email protected].