UFW (Uncomplicated Firewall) is a user-friendly frontend for iptables, available by default on most Debian and Ubuntu systems. This guide covers installation, common rules, and DigitalFyre-specific considerations.
Before enabling UFW, always allow SSH first. If you enable UFW without an SSH rule, you will lose access to your server and need to use the VirtFusion console (VPS) or IPMI (Bare Metal) to recover.
# Allow SSH before anything elseufw allow 22/tcp# Set default policiesufw default deny incomingufw default allow outgoing# Enable the firewallufw enable
Confirm with ufw status verbose to verify your rules are active.
# Allow a specific IP to all portsufw allow from 203.0.113.50# Allow a specific IP to a specific portufw allow from 203.0.113.50 to any port 22# Allow a subnetufw allow from 10.0.0.0/8
DigitalFyre VPS servers use cloud-init for initial provisioning and qemu-guest-agent for host communication. These services operate at the hypervisor level and are not affected by UFW rules inside your VPS. You are free to configure your firewall however you need.
If you have a managed service with DigitalFyre, you will need to allow access for DigitalFyre’s management infrastructure:
Jump Server IPs — Required for support team SSH access. Request these IPs from support.
Monitoring Probe IPs — Required for proactive server monitoring. Request these IPs from support.
# Example: allow DigitalFyre jump serverufw allow from <JUMP_SERVER_IP> to any port 22# Example: allow DigitalFyre monitoring probeufw allow from <MONITORING_PROBE_IP>
DigitalFyre uses UptimeRobot for uptime monitoring. If you restrict ICMP or HTTP/HTTPS traffic, you may need to allowlist UptimeRobot’s probe IPs to avoid false downtime alerts.UptimeRobot publishes its probe IP list at: uptimerobot.com/inc/files/ips/IPv4andIPv6.txtAt minimum, allow ICMP (ping) and HTTP/HTTPS (ports 80 and 443) from these addresses.