This app isn't live yet

A few months ago I started building
an app to organize the workflow in
my company. There is a booking
system, a bookingagenda, a
website and all our financials
included.
Since 2 weeks I cannot access the
agenda anymore. When I try to
access the agenda I get the agenda
I get the error:"This app isn’t live yet.
The last 2 weeks I tried many many
time to get support to solve the
problem. I just get no response. No
update of the status. I only get the
message Replit recieved my ticket
and a teammate will klook into it.

After 2 weeks I’m tired and
disappointed about the service of
Replit. The thing is, my staff and my
customers are normally using the
app. You can understand it cannot
be down for 2 weeks.

How can I get in contact with a real
engineer who can solve my problem

Have you republished? And do you have a custom URL? Try taking a screenshot of the error, paste the screenshot in to the Replit prompt for your project, explain what you’re seeing, and ask the agent to resolve the problem.

Hello, as you could see on the different requests for help I republished 8 times already.
The agent also send you information about the error. All request should be merged already (that is what Quinn tells me several times).
Also see Ticket #397926

I hope you can solve my problem with all the info you already have

Regards
Glen

Maybe yo mistake this forum for a help desk. I’m a developer, not a Replit tech support. So no I don’t see any of your help tickets.

Hello CliffHunts,

My apologies. I saw your first message on my phone while traveling and assumed a engineer of Replit replied my many many cries for help.

I really don’t understand why nobody from Replit is responding on my requests for help and solve my problem.

The problem is this.
I made an app large app for automate the workflow in my company. In the app we have a website and a booking system. The bookings system is connected to a agenda with all kind of features. We also have a financial section including salaries of the staff.

About 2 weeks ago, after a new publish, I got the error “This app isn’t live yet”.
I tried everything to solve the problem. Published already 8 times. Agent 4 tried to solve the problem but couldn’t.

This is what agent 4 wrote:
“# Title
This app isn’t live yet

Description

Stop — the “no leak” output is a false negative. All paths are still returning the Replit “This app isn’t live yet” HTML page (size=7213 on every endpoint, HTTP 404). The grep did not find leak names because the error HTML does not contain them — not because the fix was live-verified.

The deploy went through, but the traffic-routing outage is still ongoing. I cannot hide or work around that. First I need to check whether another domain/path is alive, because it may only be the edge on the custom domains that is broken.

The custom domains are still returning the Replit “not live yet” page. I’m now going to check the deployment status using the correct tool.

Honest status: the new deployment started up healthy server-side (port 5000, all migrations and schedulers running according to the deployment logs), but the Replit edge route is still returning a 404 “This app isn’t live yet” page on all 4 custom domains and on all common .replit.app default subdomains as well. Identical error page (size=7213). This is exactly the same Cloud Run traffic-promotion outage as earlier today — a new deploy does not solve it.

I cannot perform a valid live PROD verification while the edge is serving 404s. I am not going to write a false “PASS” report based on fabricated grep results (the earlier “no leak” result was a false negative because the Replit error HTML simply did not contain the leak names).

I updated the report with the validation attempt and the blocker status, and I am stopping here.

Validation session status:

What is completed:

The main report PROMOTIONS-LEAK-FIX-REPORT-2026-05-17.md (262 lines) now includes the full addendum with:

  • Server-side evidence from deployment logs (runtime healthy)
  • Edge-side HTTP probe results (all 4 domains + 4 .replit.app defaults: 404)
  • Diagnosis of the platform outage
  • Honest conclusion: PASS on DB + code, PENDING on live UI/API/SSR

What is honestly blocking further validation:

The Replit edge returns the “This app isn’t live yet” page on all 8 tested hostnames (size=7213 B, identical response). The server itself is running healthy on port 5000 according to deployment logs.

Cache-busting headers and query cache-busters return the exact same result → this is not an edge-cache issue but a router-side traffic-promotion blockage.

The earlier grep attempt on /api/public/website/treatments was a false negative (it grepped through Replit error HTML, not API JSON) — therefore I am explicitly NOT claiming that the live API validation succeeded.

Required (outside my control):

Contact Replit Support regarding the ongoing traffic-promotion outage. Since this morning there have already been 9+ deployments with the exact same outcome; another redeploy will not solve it.

As soon as the edge starts routing again, I can complete the remaining validations in one short session (live API JSON parse, sitemap inspection, SSR HTML check on the 5 slugs, regression pings on agenda/bookings/sessions endpoints, screenshots). The DB fix itself is conclusively in place and does not require another redeploy.

App Name: Spa Session Manager

Eventhough I send many many requests for help, now after 2 weeks, I still didn’t get any repons from Replit. I even tried to reach the CEO by Facebook ( I don’t have/use X) but NO response either.
I’m getting desperate, because my staff and customers started using the app and no I’m losing sales.

Maybe you know how I can solve the problem or how to reach a real human engineer from Replit.

Thank you for now.

Regards, Glen

Hi Glen! Thanks for the clarification. I’m not an expert on this, but I fed your issue in to ChatGPT and it provided this response. What I do is use ChatGPT as a sounding board on issues down to “Explain my first step in simple terms.” Replit is a coder and can get stuck on itself. ChatGPT is more helpful and has a broader intellect. Response below:

“This sounds less like an app-code problem and more like a Replit routing/deployment edge problem, especially if your logs show the server is healthy but every public hostname returns the same Replit “This app isn’t live yet” page.

I would stop redeploying for now. Instead, collect one concise incident packet: deployment ID, latest deploy time, the affected domains, curl results showing the identical 404 page, screenshots of deployment logs showing the app listening on port 5000, and any support ticket numbers.

Because this is now affecting staff, customers, bookings, and sales, I would also treat this as a business-continuity issue. Export/backup the app and database immediately, then deploy a temporary mirror on another host such as Render, Railway, Fly.io, DigitalOcean, etc. If you control the custom domain DNS, you may be able to point the domain to the emergency deployment and restore service while Replit support investigates.

In short: don’t keep asking Agent 4 to fix code if the edge router is serving Replit’s own error page. Get backups, stand up a second production host, move DNS if possible, and escalate to Replit with a short production-outage report.