Skip to content

← All integrations

Firewall and VPN

Renews the OPNsense Web GUI certificate through SSH with locked configuration changes.

The appliance runs the integration and drives the OPNsense command line over SSH on port 22. No service agent is installed on the device.

What happens

  1. The appliance connects to the OPNsense command line over SSH, port 22.
  2. The integration uses pinned SSH and a fixed PHP routine to add certificate and CA objects under a configuration lock. No HTTP API access is required.
  3. Only the Web GUI binding changes and the GUI restarts. The binding and new TLS leaf are checked; a listener unreachable both before and after is reported separately.

Technical details

Connection
The integration runs on the appliance, which connects over SSH, port 22. No service agent is installed.
Service ports
22, 443
What you need
Enable SSH with root login under System > Settings > Administration > Secure Shell. Enter root's password or unencrypted SSH private key here. Read and confirm the SSH host key first.
Platform
OPNsense 24.1+
Actions
Discovery, Installation, Verification, Rollback
Integrations
opnsense-api 2.0.0
Note
  • Automatic restoration and rollback use previous_state to restore the individual binding and preserve later choices. Certificate and CA objects are not deleted. Native ACME continues with its own object and restart actions. ACME is the protocol a CA uses to issue certificates automatically.

Next steps