[FIX] odoo20: bind http_interface 0.0.0.0 + http_port rename

Symptom: fresh Odoo 20 deploy serves 127.0.0.1:8069 only; Traefik and the
swarm VIP get connection refused -> HTTP 502 through the preview domain.

Root cause (odoo/tools/config.py):
  - line 289: --http-interface my_default='127.0.0.1'
  - lines 768-770: empty http_interface is force-reset to 127.0.0.1
  - the legacy xmlrpc_port key no longer exists (renamed http_port), so
    the old conf line was silently ignored (port worked only via default)

Fix: generated odoo.conf now sets http_interface = 0.0.0.0 and
http_port = 8069. Verified end-to-end on the onebspace deployment:
internal 8069 binds 0.0.0.0, preview domain returns 200.
This commit is contained in:
1b-agent committed 2026-11-10 14:30:57 +00:00
1 parent 6e28aba906
commit b2e1d1d3d5
4 files changed
+19 -3

No files matched your search

+7
View File
@@ -17,6 +17,13 @@ blueprint (battle-tested Sep 2026 on Odoo 19) — same architecture, retargeted:
## Deploy (one command + two MCP calls)
> **Odoo 20 delta (2026-11-10):** the generated `odoo.conf` now sets
> `http_interface = 0.0.0.0` and `http_port = 8069`. Odoo 20's
> `odoo/tools/config.py` defaults `http_interface` to `127.0.0.1` (and
> force-resets it when empty), and the legacy `xmlrpc_port` key no longer
> exists — without this fix Odoo binds loopback only and every request from
> Traefik/the swarm VIP dies with `connection refused` → HTTP 502.
```bash
python3 deploy.py prepare # regenerates easypanel.schema.json, inline.Dockerfile, init-odoo.sh, .db_password
```