mednote.zeabur.app generated subdomain stale reservation, unable to rebind to new GCP App

Back

Waiting for author response

AAnderDEVELOPER1d ago

Hello Zeabur Support,

I need assistance in manually releasing or rebinding a stuck Zeabur generated subdomain.

Domain: mednote.zeabur.app

Issue: Currently, this domain returns a Zeabur 404, but it cannot be rebound to my new GCP app service.

When I attempt to bind it via Dashboard / CLI / API, addDomain returns:

DOMAIN_UNAVAILABLE / Domain is not available

However, this domain does not appear in any visible service domain list.

Target Service:

Project: MedNote-GCP-standby
Project ID: 6a25b920f1be9943f1f9d98e
Environment ID: 6a25b92095b39806d284adc0
Service: tungim-gemini
Service ID: 6a25b923f1be9943f1f9d98f
Port: web / 3000 HTTP

Currently working test domain: https://mednote-gcp.zeabur.app

This test domain is already bound to the target GCP app service and returns HTTP 200.

Current production domain status: https://mednote.zeabur.app

This domain currently returns a Zeabur 404.

Troubleshooting completed:

mednote.zeabur.app is not in the domain list of the target GCP app service.
mednote.zeabur.app is not in the domain list of the old AWS app service.
Executed removeDomain on the target GCP app, returned domain not found.
Executed removeDomain on the old AWS app, returned domain not found.
Scanned all visible projects / services; no service domain list shows mednote.zeabur.app.
Retrying addDomain still returns DOMAIN_UNAVAILABLE.
Zeabur AI confirmed this appears to be a backend domain registry stale reservation, and current tools cannot manually release or force-bind it.

Request: Please assist in manually releasing this stale registry reservation:

mednote.zeabur.app

Or bind it directly to:

Service ID: 6a25b923f1be9943f1f9d98f Environment ID: 6a25b92095b39806d284adc0 Port: web / 3000 HTTP

Important Note: Please do not delete or recreate PostgreSQL, MinIO, app services, or any volumes.

Migration status: The GCP migration itself is complete; only the production domain is stuck.

Completed items:

GCP app is running normally.
GCP PostgreSQL data has been restored and verified.
GCP MinIO data has been restored and verified.
GCP MinIO HTTPS domain is working normally: https://minio-mednote-gcp.zeabur.app
GCP app temporary test domain is working normally: https://mednote-gcp.zeabur.app
Asset URLs in the GCP database have been updated to the new GCP MinIO HTTPS endpoint.
Temporary public TCP endpoints used for migration have been closed.

The only remaining blocker is:

The stale reservation of mednote.zeabur.app cannot be released, preventing the production domain from being rebound.

Thank you.

2 Replies

AAnderDEVELOPER1d ago

how to do this

Confirm Upgrade

You will be billed $80/mo for the Team Plan. For this billing cycle, you'll only be charged the prorated difference between the two plans.

team plans must use teamSubscribePlan

CCanEMPLOYEE22h ago

Hello,

After checking our backend logs, mednote.zeabur.app currently has no stale reservation — it was fully released during a domain removal operation on 6/8 at 04:06 (UTC). (The operation was performed by domain name, which removed the bindings from both the old AWS and the new GCP, which is why it is not visible in the domain lists on either side.) The name is currently completely available.

The reason you received DOMAIN_UNAVAILABLE when rebinding is: for domains ending in zeabur.app, you cannot use the "Bind Custom Domain" method to enter the full domain mednote.zeabur.app (zeabur.app is a reserved suffix and will be flagged as "Domain name already reserved"). Please use the "Bind Zeabur Subdomain" method instead and enter only the prefix:

Console Operation: Go to the tungim-gemini service page → switch to the "Networking" tab → in the "Public Networking" section, click "Bind Zeabur Subdomain" → enter mednote → select the web (3000) port → "Confirm Binding".
Via API: When calling addDomain, please include isGenerated: true and domain: "mednote" (excluding the .zeabur.app suffix).

This will allow you to bind it directly back to your new GCP service without our manual intervention, and it will not affect your PostgreSQL / MinIO / volumes.

Regarding the Team Plan upgrade confirmation window: Simply click confirm in the confirmation dialog in the console. You will only be charged the prorated difference between the two plans for this billing cycle.

If you still encounter issues after following the steps above, please let us know and we will assist you further.

Add a Reply

Forum

2 Replies

Confirm Upgrade