- Shipped
- August 27, 2026 at 8:33 AM UTC
- Author
- Kamo
- Commit
- 90f99a7
Adding a KamoPBX phone server failed with a raw Kubernetes DNS error — 'I/O error on PUT ... **************** — shown to an organization admin who can neither read nor act on it. Two causes, both fixed: - The provisioner attempted the call with no platform configuration at all. It now checks first and refuses with an actionable message naming the settings page, instead of failing open into a DNS error. - Settings were @Value-only, so there was no way to configure KamoPBX without a redeploy. They now come from the SYSTEM_CONFIGURATION singleton, which the platform settings UI writes; the @Value defaults remain a fallback so the service still boots before the migration has run.