EZSCALE/virtfusion-whmcs-module
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 10 Wiki Activity

Fix firewall API endpoints to use correct {interface} path parameter

Browse Source 
- Firewall endpoints now use /firewall/{interface}/ where interface is
  "primary" or "secondary" (was missing the interface segment)
- Add applyFirewallRulesets() method for applying predefined rulesets by ID
- Add firewallApplyRulesets client endpoint (comma-separated ruleset IDs)
- Add sanitizeFirewallInterface() helper for input validation
- All firewall methods now accept optional interface parameter (default: primary)
- Document that VirtFusion uses ruleset-based firewall (no individual rule CRUD)
- Update README with correct API paths and ruleset documentation

https://claude.ai/code/session_01TCsJ4WZCGuEX3zqh1tQ2zx
This commit is contained in:
Claude
2026-02-07 12:51:36 +00:00
parent cad1af18c1
commit cfb1ddb4e5
3 changed files with 151 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
README.md
View File

@@ -288,10 +288,11 @@ Four power control buttons:
- **Force Off** - Immediate power cut (use with caution)
### Firewall Management
- View firewall status (enabled/disabled)
- Enable or disable the server firewall
- Apply/synchronize firewall rules
- For advanced rule management, use the VirtFusion control panel
- View firewall status (enabled/disabled) with status badge
- Enable or disable the server firewall on primary/secondary interfaces
- Apply firewall rulesets by ID (rulesets are predefined in VirtFusion admin)
- Re-apply/synchronize currently assigned rulesets
- **Note**: VirtFusion uses a ruleset-based firewall system. Individual rules cannot be created or deleted via the API. Create rulesets in the VirtFusion admin panel, then apply them to servers through this module or the control panel
### Network Management
- View all IPv4 addresses and IPv6 subnets assigned to the server
@@ -404,10 +405,12 @@ WHMCS automatically loads theme-specific templates when they exist. Copy the ori
| Method | Endpoint | Purpose |
|---|---|---|
| `GET` | `/servers/{id}/firewall` | Firewall status |
| `POST` | `/servers/{id}/firewall/enable` | Enable firewall |
| `POST` | `/servers/{id}/firewall/disable` | Disable firewall |
| `POST` | `/servers/{id}/firewall/rules/apply` | Apply firewall rules |
| `GET` | `/servers/{id}/firewall/{interface}` | Firewall status and rules |
| `POST` | `/servers/{id}/firewall/{interface}/enable` | Enable firewall |
| `POST` | `/servers/{id}/firewall/{interface}/disable` | Disable firewall |
| `POST` | `/servers/{id}/firewall/{interface}/rules` | Apply rulesets (body: `{"rulesets": [1,2]}`) |
`{interface}` is `primary` or `secondary`. Individual firewall rules cannot be managed via the API - use rulesets created in the VirtFusion admin panel.
### Network