Troubleshooting
Symptom first — what the wizard and the scaffolded app do when something is wrong, what causes each one, and the page that owns the fix.
Two things break in different ways here: the wizard, which runs once on your machine, and the app it writes, which runs on a host. The symptoms below are grouped that way. Every one of them links to the page that owns the detail.
Check /chatfuel/healthz, then the startup log
The app's server answers /chatfuel/healthz with one field, uncached:
{ "ok": true }200 and true means the proxy came up with a configuration it can serve; 503 and false means
it is running and something is missing. That is the whole of it. The route is open to anyone who
can reach the deployment, so it says nothing about the auth gate — an unauthenticated caller has no
business learning whether the gate is off before trying a request.
The mode is on the startup line instead, and that line is the first thing to read when a deployment misbehaves: it names the gate, the fences, the routes that are mounted and the admin panel. Your own server shows the line and what each shape of it means.
The path is the same on the bundled Node server, the Vite dev server and the Vercel function. It
sits inside the proxy's prefix because on Vercel everything outside /chatfuel/* goes to
index.html: a bare /healthz there is the SPA answering 200 with HTML. A page back instead
of JSON means you asked the wrong path.
A build/runtime mismatch never announces itself. VITE_* values are compiled into the browser
bundle when you build; everything else is read by the server when it starts. Nothing fails at the
moment the two disagree — it fails later, at the gate, and reads as an auth bug.
The wizard
The app
Not on this page
Limits that are not bugs
Behaviour that looks broken, is not, and will not change — because the Chatfuel API cannot answer the question underneath it.
Getting help
Where to ask, what to include, and what to redact before you paste it anywhere.
Errors
Every error code the stack can produce, code by code, with what causes it.
This site as text
An index at /docs/llms.txt, everything in one file at /docs/llms-full.txt, a Markdown twin at every documentation address, and /SKILL.md — with no MCP server behind any of it.
Limits that are not bugs
Behaviour that looks broken, is not, and will not be fixed — because the Chatfuel API cannot answer the question underneath it.