Skip to main content

​
Publish troubleshooting

When a publish fails, the dialog tells you why and usually gives you two buttons: Fix with AI (the agent reads the build output or the app’s logs and fixes the project) and Try again. (A taken link name suggests other names instead, and running out of credits offers Buy credits or Claim offer — Pro at 30% off.) The sections below match the messages you can see.

​
“Publish was interrupted”

The publish stopped part way (for example during an update on our side). Nothing is wrong with your app — Try again.

​
“Email not verified”

Verify your email, then retry publish. See Email verification.

​
Slug already taken

The publish says “That link name is taken”. Choose another slug — slugs are unique across Mythex. This, and “This link name can’t be used for publishing”, are the only messages that mean the name is the problem — change it and publish again. For any other publish error, keep the same name.

​
“Publishing couldn’t finish because of a problem on our side”

Nothing is wrong with your app or its name. Publish again in a few minutes with the same slug. If it keeps failing, contact support with the project ID and slug.

​
“Publishing is busy for a moment”

The hosting side asked us to slow down. Nothing is wrong with your app — publish again in a few minutes.

​
“This file is too big” / too many files

Each published file has a size limit (about 25–30 MB, depending on the kind of site), and a site can have up to 20,000 files; the message lists the files over the limit. Move large files out of the folder that gets published (for example into Storage, and link to them) or make them smaller, then publish again.

​
“Your app stopped right after it started”

The app published but exits shortly after starting — usually a missing setting (an env var or secret), a crash on the first request, or an error in the start command. Use Fix with AI: the agent reads the app’s logs and fixes it. Then publish again.

​
“Your app didn’t start after publishing”

The app was published but never began accepting connections. Most often it listens on a different port, or only on localhost: a published app must listen on 0.0.0.0 and the port in $PORT. Use Fix with AI, then publish again.

​
“Your app keeps crashing” / “isn’t accepting connections” (after it went live)

A publish can succeed and the app fail a few minutes later — it keeps crashing, or it runs but stops accepting connections. Mythex checks published apps regularly; when that happens the publish is marked failed, you get an email, and the project shows the message with Fix with AI. Fix it, then publish again.

​
“The build failed”

Use Fix with AI — the agent reads the build output and fixes it. Or, by hand:
  1. Confirm the app runs in Preview
  2. Ask the agent to fix the build/start command errors shown in logs
  3. For Dockerfile backends, confirm the image builds locally in the sandbox before retrying publish
  4. Retry publish

​
Published URL is blank or errors

  • Wait a minute and hard-refresh (CDN can lag briefly)
  • Confirm env vars / database were attached before publish
  • Check hosting allowance was not exhausted (Hosting limits)
  • Unpublish/republish after a clean Preview

​
App crashed or “ran out of memory” email

The app used all the memory its machine has. Ask the agent: “my app ran out of memory, give it more and publish again.” Each plan has a maximum (App size); at the maximum, ask the agent to find what uses the memory and reduce it.

​
Hit deployment limit

Free allows up to 3 published apps at once (live, or paused for credits). Unpublish one, or upgrade to a paid plan to publish as many as you like. An app that’s already published can always be republished. Publishes also need positive Cloud credits.

​
Out of credits

When a project’s monthly Cloud credits run out, the published app pauses (its database, files and URL are kept) until Cloud credits reset on the 1st (Free) or more credits are available (Pro, Business and Enterprise, from monthly credits, top-ups or auto-reload). Free cannot top up. We email you before it happens. See Credits and Hosting limits.

​
“Only admins can publish” or “Ask an admin to publish”

Your Enterprise workspace has a publishing rule. Ask an admin to publish, or to approve your request. See Who can publish and open apps.

​
Update didn’t show on the live URL

Publish again after Preview looks right, then hard-refresh. Live sites are a snapshot until you republish — chatting in the workspace does not auto-push to the public URL.

​
Still stuck

Email support@mythex.ai with project ID, slug, and screenshots of the publish error.