Build Journey
Three Bugs, One 502: Chasing a Connector That Kept Dropping
August 11: a 502 and three fixes.
The Ford family · Josh, dad and builder of FamilyOrganization.app, writing up his build journey
Published Updated 1 min read
On August 11 the connector's endpoint was returning 502 on every request, with an error that a package couldn't be found.
My first fix was wrong. Netlify was shipping the server's files into a folder with no dependencies, so the site rebuilt and failed exactly the same way. The second fix copied the server code inside the website at build time, so everything bundles together. I tested the bundle on its own: the discovery address returned 200 and an unauthenticated request returned 401, as it should.
The third problem was random disconnects. The server was replying before its database calls had finished. I switched it to the mode that waits for the real answer.
Three fixes for one endpoint. Here's what the connector is for.
Built on August 11, 2026 (commit 52ab86a). Written up on October 2, 2026 from my commit history.