The photo clients publish the endpoint they declare (hq issue 227) #263

2026-10-04T10:25:57Z

mesh-admin commented

2026-10-04 10:25:57 +00:00

Three one-line changes. photos is the one failing on the control node right now; photos-eef and photos-filip are the same fault waiting for a machine that runs a reverse proxy.

Each declares a web endpoint — 4001, 4012, 4013 — that its route grant points at, and each published a bare 80. The mesh assigns a machine port only for a port the module declares, so 80 got no assignment, publishedOn fell back to the number as written, and the container asked the machine for the port the proxy holds.

Written the long way (4001:80), the software's 80 is published at the port the module declares, and the mesh rewrites the outer half to whatever it assigned.

mesh-controller #263 adds the catalogue-wide test that makes this a rule rather than three repairs. It fails against this branch's parent, naming all three.

Three one-line changes. `photos` is the one failing on the control node right now; `photos-eef` and `photos-filip` are the same fault waiting for a machine that runs a reverse proxy. Each declares a web endpoint — 4001, 4012, 4013 — that its route grant points at, and each published a bare `80`. The mesh assigns a machine port only for a port the module *declares*, so 80 got no assignment, `publishedOn` fell back to the number as written, and the container asked the machine for the port the proxy holds. Written the long way (`4001:80`), the software's 80 is published at the port the module declares, and the mesh rewrites the outer half to whatever it assigned. mesh-controller #263 adds the catalogue-wide test that makes this a rule rather than three repairs. It fails against this branch's parent, naming all three.

mesh-admin added 1 commit 2026-10-04 10:25:58 +00:00

The photo clients publish the endpoint they declare (hq issue 227) 1bc6daf31b

Each declares a web endpoint — 4001, 4012, 4013 — and published a bare 80,
which the mesh has nothing to assign for, so 80 reached the machine and
collided with the reverse proxy. Written the long way, the software's 80 is
published at the port the module declares and the mesh rewrites the outer
half to whatever it assigned.

photos is the one that failed on the control node; the other two are the same
fault waiting for a machine that runs a proxy.

mesh-admin merged commit 19a4055bb5 into main

2026-10-04 10:27:23 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#263