create_haproxy_frontend
Create an HAProxy frontend listener on pfSense. Configure bind addresses, type, backend, and SSL certificates to route incoming traffic.
Instructions
Create an HAProxy frontend listener
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"name": "<name>"
},
"name": "create_haproxy_frontend"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Frontend name | |
| type | No | Frontend type (http, https, tcp, ssl, etc.) | |
| descr | No | Optional description | |
| status | No | Frontend status (active, disabled) | |
| backend | No | Default backend name to forward traffic to | |
| bind_addresses | No | List of bind address dicts. Each dict maps to the pfSense API's `a_extaddr` fields: {"extaddr": "custom", "extaddr_custom": "192.168.1.100", "extaddr_port": "443", "extaddr_ssl": true}. `extaddr` accepts only the API enum — `custom`, `any_ipv4`, `any_ipv6`, `localhost_ipv4`, `localhost_ipv6` (interface names like "wan"/"lan" are GUI-only and are NOT accepted). To bind an interface's address, use extaddr="custom" with extaddr_custom set to that interface's IP or a Virtual IP. | |
| ssloffloadcert | No | The default SSL/TLS certificate refid to use for this frontend when any bind address has extaddr_ssl=true (from search_certificates or search_acme_certificates — use the certificate's `refid`, not its numeric `id`). | |
| ha_certificates | No | Additional SSL/TLS certificate refids for SNI on this frontend | |
| apply_immediately | No | Whether to apply changes immediately |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||