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:
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.