Skip to content
LiveStart building for free · CA$100 signup credit, up to CA$300 totalCA$1 verification payment credited back · Ends December 31, 2026
Get started for free →

OPNsense

OPNsense is an open-source firewall and router platform based on FreeBSD. The ZCP marketplace image is a pre-installed OPNsense system, not a live installer, and is intended for firewall, routing, VPN, and network security use cases.

ComponentVersion
OPNsense26.7.1
FreeBSD15.1
ResourceMinimumRecommended
vCPU24
RAM2 GB4 GB
Storage4 GB8 GB

OPNsense is different from most ZCP marketplace images:

  • It does not use cloud-init.
  • It does not provide SSH access by default.
  • It is managed first through the ZCP console.
  • Its web GUI is available only after the LAN interface is configured.

On first boot, OPNsense uses its default LAN address:

192.168.1.1/24

That address may not match the platform-assigned IP. Reconfigure the LAN interface from the console before expecting the web GUI to be reachable.

In the ZCP console, open the VM and select View Console.

InterfaceUsernamePassword
Consolerootopnsense
Web GUIrootopnsense

Change this password immediately after first login.

From the console menu, select:

2) Set interface IP address

Configure the LAN interface with DHCP or a static address that is reachable on your selected network. After the interface is configured, OPNsense restarts the relevant firewall, DNS, and web GUI services.

Open:

https://<lan-or-forwarded-ip>/

Accept the self-signed certificate warning and log in with root / opnsense, then change the password.

If you access the web GUI through a NAT or port-forwarded address, OPNsense may reject login with an HTTP referer error because the browser URL does not match an address the appliance recognizes as its own.

Configure the port-forwarded hostname as an approved alternate hostname in the OPNsense web GUI before using it. This keeps HTTP referer enforcement enabled.

If you must test the connection before configuring an alternate hostname, temporarily disable the check from the console shell, then restore it immediately after testing:

cp /conf/config.xml /conf/config.xml.bak
sed -i '' 's#</webgui>#<nohttpreferercheck>1</nohttpreferercheck></webgui>#' /conf/config.xml
configctl webgui restart
# Restore HTTP referer enforcement after testing
cp /conf/config.xml.bak /conf/config.xml
configctl webgui restart

The temporary setting must be inside the <webgui> section. Do not leave it enabled after testing.

OPNsense is the firewall, so customer configuration determines which services are reachable. Initially, the important service is:

PortProtocolPurpose
443TCPWeb GUI on LAN interface

WAN rules, VPN ports, firewall policy, and port forwards are configured by the customer after first login.

Change the default password immediately. Avoid exposing the management web GUI to the public internet. For production, restrict management access to a private network, VPN, or trusted administrative IP range.

The template does not support SSH-key injection or platform password reset. Log in with the vendor defaults, then change the password manually after first login.

Last updated: