POST /api/v2/edge/appliances/edge-01-tyo/survival-config returns a 400 Bad Request. Response body looks like this:
{
"message": "Validation failed",
"errors": [
{
"message": "Local media port range conflicts with existing WAN binding",
"code": "PORT_CONFLICT"
}
]
}
The Edge node is running version 2024.5.0. Bare metal Dell R750 setup. Network uses dual Intel X710 NICs with VLAN 100 for WAN and VLAN 200 for local LAN. The config payload sent via Postman matches exactly what the Edge Admin UI shows under the Survival tab.
Running a GET on /api/v2/edge/appliances/edge-01-tyo/survival-config pulls back the same JSON without issues. The API gateway sits behind an nginx reverse proxy. Logs on the proxy show the request hits the backend, then the backend drops it with the 400. Checked the BIOS settings and firmware on the R750. Everything is at the latest level. The local media port range is set to 50000-50200. WAN binding uses 40000-40100. No overlap exists.
Scripting the deployment for the Osaka site. This validation error blocks the automation. The script is doing jack all right now. The UI accepts the save button click instantly. API rejects it every single time. Firewall rules are wide open for testing. Port 443 and 8443 are passing traffic.
Here is the request payload:
{
"survivalMode": {
"enabled": true,
"localMedia": {
"portRange": {
"start": 50000,
"end": 50200
},
"codecSettings": {
"g711": true,
"g729": false
}
}
}
}
The error code PORT_CONFLICT seems wrong. Maybe the API is checking a cached state or an internal database entry that hasn’t synced with the active config.
Ran the clear command via CLI. edge cache clear executed successfully. API still throws the 400.
Restarting the Edge service is not an option during business hours. Tokyo timezone means the site is live right now. Traffic is flowing. Can’t touch the production node.
Looking at the API docs for edge configuration endpoints. Nothing mentions a hidden validation rule for port ranges. The schema looks standard.