MyJackfruit

Help
Browse topics · Going live (Publishing)

Going live (Publishing)

← Going live (Publishing)

Publishing failed or found a secret key. What now?

Short answer

When publishing is refused, nothing goes live. Read the line your AI shows, fix what it names, such as a key, then publish again.

Deeper

Also asked:

My AI says my files hold a secret key and will not publish. What now? Nothing was put live. Ask your AI to take the key out of the file the line names and out of your app's code, then publish again. If others may have seen the key, make a new one at the service and end the old one.

When publishing is refused. The connector, the small GilbPlatform program on your computer that publishes, prints one line, mostly a word, a colon and a sentence, and nothing is put live. If your AI ran the command for you, the line it printed is the one to read; ask your AI to show it to you. The answer Why was my publish refused, and what do I do? tells what each line means. The most common:
- A name that is taken or kept back: choose another name; see The name I want is taken, or I chose the wrong name. What now?
- site_limit_reached: you already hold 2 sites. Publishing a site you already hold again works and does not use a new one; for more sites, write to [email protected].
- files_refused: a file of a kind that is not taken, too many files or too many bytes, no index.html at the top, or a secret key, as below.
- not_entitled: Publishing for this account was switched off, so it cannot publish. Write to [email protected].
- the platform could not be reached or the upload timed out: check your internet connection and run it again.

My files hold a secret key. A key is a secret text a service gives you so your app can use it, like a password for a program. Anyone who has it can use the service as you, often at your cost. Before anything is put live, GilbPlatform checks your app's files for text that looks like a key, such as a Stripe key, a GitHub token, a Google API key or a private key block, and refuses: "The file '…' looks like it contains … Nothing was published. Remove the secret from the file and publish again." The line names the file and the kind of key, never the key itself.

What to do. Ask your AI to take the key out of that file and out of your app's code, then publish again. A key does not belong in your app's files at all: an app live at pages.dev has no safe place for one; see Where do I keep the passwords and keys for the services my app uses? Nothing was published, so the key did not go live this time. If it is also in your code's copy on GitHub, or anywhere others may have seen it, make a new one at the service that gave it and end the old one; that service's own pages say how.

If it is not a key. The check finds only text shaped like a key; it does not prove that no key is there, and it can refuse text that only looks like one. There is no way to skip the check. If you are sure the text is not a secret, write to [email protected] with the file's name and the kind of key the line names, never the text itself. A file with an extremely long unbroken run of characters cannot be checked and is refused too: could not be checked for secrets.

I said yes, but my app did not go live. Open https://<name>.pages.dev in your browser, with your site's name in place of <name>: if your site shows, it is live. If it does not, ask your AI what the command printed and read that line as above. If there was no refusal and the site does not open, write to [email protected] with the address and what your AI showed you.

My AI ran out of use in the middle of publishing. Your AI's maker sets usage limits, and one can stop your AI at any point. First open the address: if your site shows, it is live. If it does not show, it may not be live; ask your AI what the command printed, and read that line as above. A name that was reserved for you when a publish began, but was never published, counts as one of your 2 sites until it is let go 24 hours later; publish under the same name and it is yours. The command's publish ticket, the short permission it gets first, lasts 10 minutes, and each run asks for a new one. When your limit resets, or with another AI you have connected, tell your AI in your own words that you want the app live; it then follows the same publishing steps, and still needs your yes. The files your AI wrote on your computer stay there. The answer My AI says I have reached my usage limit. What now? tells more.

This answer is written for a computer screen.

Source: GilbPlatform 0fc5a548 (https://id.gilb.com/version, read 13 November 2026): workers/publish-ingest/src/checks.ts:30-40 (the kinds of key-shaped text: sk- keys, Stripe, AWS, PEM blocks, GitHub, Slack, Google API keys, JSON Web Tokens, Bearer), :153-158 ("looks like it contains … Nothing was published. Remove the secret from the file and publish again."; could not be checked for secrets; the value is never printed); workers/publish-ingest/src/index.ts:100 (files_refused); src/publish/records.ts:134-135 (Publishing for this account was switched off, so it cannot publish.), :246 (an unpublished name is let go after 24 hours), :256 (2 sites), :386-391 (the same person may claim their own name again); src/publish/ticket.ts:19 (a ticket lasts 600 seconds). Connector 0.6.1, served at https://gilb.com/app/gilb-connector.mjs, read 13 November 2026: a refusal printed as one line; the upload timed out after 120 seconds; no option skips the checks. Standards read from GilbPlatform on 13 November 2026: Proc_v_i_c_PublishPagesDev (step 9: read the refusal's code), Standard Rule_Code_deployment (RuleDeployPagesDev), Agent.Coder (AskGoLive: never publish without the person's yes). Live help pages, sentences shared: Why was my publish refused, and what do I do?; Where do I keep the passwords and keys for the services my app uses?; How many sites can I have, and how do I get more?; How do I put my app or website live on the internet?; My AI says I have reached my usage limit. What now?

Checked against GilbApp d529620.