Files
flvx/plans/005-forward-invalid-bindip-fallback-default.md
sagitchu 1c596fae4b feat: auto-fallback to default bind IP when invalid bind address detected
When a forward service is updated with a bind IP that doesn't exist on the
host network interfaces, the system now automatically falls back to the
default bind address (listening on all interfaces) instead of failing.

- Added syncForwardServicesWithWarnings to collect fallback warnings
- Implemented fallbackForwardPortToDefaultBind for graceful degradation
- Added UpdateForwardPortBindIP repository method to persist fallback
- Enhanced error detection for 'cannot assign requested address' errors
- Frontend displays warning toasts when fallback occurs
- Added comprehensive unit tests for new error detection functions
2026-03-03 21:34:12 +08:00

656 B

005 Forward Invalid BindIP Fallback Default

Checklist

  • Split forward service bind failures into address-in-use and cannot-assign classes.
  • Keep self-occupy release/rebind only for address-in-use conflicts.
  • Add fallback path for cannot-assign: switch to default listener bind and retry service creation.
  • Persist fallback result to DB by clearing forward_port.in_ip for affected node+port.
  • Return non-blocking warning in forward update response when fallback occurs.
  • Show warning toast in forward edit UI while still treating operation as success.
  • Run focused backend tests for touched handler/repo packages.