kombify.me troubleshooting - kombify

Open the name in a browser and note what you see. The answer tells you which check below to start with. If you have not made an address yet, begin with Get your first kombify.me address.

What the browser shows

What you see	Most likely reason
404, “service subdomain not exposed”	The app is switched off. Switch it on.
503, “subdomain inactive”	The address is paused. Set it back to active.
503, “try again” on a private address	The home helper is not connected.
502, “Bad Gateway”	kombify.me could not reach your app. Check that it runs and is public.
410, “publication expired”	A temporary sharing period ended.

The name shows an error or does not open

Check	What it means
The service route is exposed	An unexposed service name stays unpublished. Exposure defaults to off.
The name has the right shape	First-party kit services use `{base}-{service}.kombify.me`. Reserved apex names such as `auth.kombify.me` stay unused.
The origin is public (public address)	The public path rejects private, loopback and link-local targets.
The node agent is connected (private target)	If the agent is disconnected, the public name stays unavailable and asks the client to retry.
The same owner reconnects	Reconnecting the same owner restores forwarding. Another owner’s agent cannot serve the route.

Steps to work through

Open the name again after about a minute. kombify.me keeps a routing cache of about 60 seconds, so a change may not show immediately.
Check the answer in the table above and follow its row in the checks below.
Check that the app itself works: for a public address open its public address directly, and for a private address open it from inside your home network.
If registering a new name fails with a limit error, remove one you no longer use. See Get your first kombify.me address for the limits.

To change, pause or remove an address, see Change, pause or remove an address. For the difference between public and private, see Public, private or redirect. For kit apps, see Use an address with a StackKits server.

I only need the service at home

Use the local name instead. Local names stay on the resolver that StackKits installs. kombify.me does not publish *.lan.kombify.me names.

Still stuck

kombify.me is Alpha software, so names and error shapes can still change. Write to info@kombify.io with the name you used and the time of the attempt. Never send a password or API key.