Data Recovery Request

Resolved

PPpeter peiDEVELOPER5/16/2026

Technical Information

Project Information:

Project ID: 69ff349fe6a21fff4d95e40c
Project Name: new-api
Service ID: 69ff3520e6a21fff4d95e423
Service Name: new-api
Environment ID: 69ff349fe5ed304c1d845771

Database Information:

Database Type: SQLite
Database Path: /data/newapi-reset-20260509.db
Current Database Size: 556KB (Initialized state)
Database Filename Pattern: newapi-reset-{DATE}.db (Indicates reset)

Deployment History:

Data Loss Timeline:

First Data Loss: 2026-05-09 (Deployment ID: 69ff38cf78d6bbbd5c6acdd5)
Second Data Loss: 2026-05-16 (Deployment ID: 6a08602cbbc71468fc736987)

Environment Variable Configuration:

PORT=${WEB_PORT}
SQLITE_PATH=/data/newapi-reset-20260509.db?_busy_timeout=30000
SESSION_SECRET=newapi-reset-20260509-session

GitHub Repository:

Repository: QuantumNous/new-api
Repository ID: 717197250

🆘 Request Content

Check Backups - Please check if there are any database backups prior to 2026-05-09.
Restore Data - If backups exist, please help restore to the last known good state.
Root Cause Analysis - Why was the database reset? Is it related to the persistent storage configuration?

⚠️ Additional Information

Current Service Status: RUNNING
Service Domains:
new-api-k9xm.zeabur.app
api.gantriq.com
The database does not have persistent storage (Disk) configured.
This is a production service, and the data loss has a severe impact.

📞 Submission Steps

Visit https://zeabur.com/forum
Click "New Topic" or "Ask a Question"
Select Category: Support or Bug Report
Title: [Urgent] SQLite Database Reset - Data Recovery Request
Paste the information above into the issue description
Submit

🔐 Actions Taken Simultaneously

Minified React error #185; visit https://react.dev/errors/185 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

2 Replies

BCBohan ChenEMPLOYEE5/18/2026

Hello,

I have checked your service status:

Persistent storage is configured — The /data directory of your new-api service has a Persistent Volume Claim (PVC) mounted, and the SQLite database is currently running normally. Therefore, the assessment that "persistent storage is not configured" is inaccurate.

Reason for data loss: Your persistent volume was recreated on May 16th, and the previous volume no longer exists. This means the old volume was deleted and recreated during an operation, and the data inside was cleared as well. Common triggers include removing and re-adding a Volume in the Dashboard, or recreating the service.

Unable to recover old data — Zeabur does not automatically back up data in persistent volumes, and there are no remnants of the old volume on the disk. If you have important production data, it is recommended to regularly back up your database files to external storage yourself.

AAnonymous5/22/2026

This post has been inactive for a while. We will be closing it in 2 days if there is no new activity.

This issue has been marked as resolved