Hello,
I have confirmed that the New API database currently connected to web3xxxx.com is not the original production database, but a newly initialized Postgres instance from 2026-06-02.
Evidence:
- The current online database has only 3 users and 1 channel.
- Previous channel data, user data, and customer recharge balances/quotas are all missing.
- The current database shows redemptions=0, and the business log count is extremely low, clearly indicating it is not the original production database.
- The New API startup log at 2026-06-02 13:34:21 clearly shows: system is not initialized and no root user exists
Please assist urgently with the following:
- Locate the original production Postgres data volume/backup used by the New API service for web3xxxx.com prior to 2026-06-02 13:34 (Asia/Shanghai).
- Restore the old production database or remount the current service to the original production Postgres volume.
- If automatic backups exist, please prioritize restoring the most recent backup prior to 2026-06-02 13:34.
- Please do not just restore the site page; I need to recover:
- Channel data
- User data
- Customer recharge balances/quotas
- Historical business data
Additional Information:
- Current public domain: web3xxxx.com
- The New API service previously used the Zeabur domain: hu-newapi.zeabur.app
- I have confirmed that New API uses Postgres, not SQLite.
- This is a data recovery issue, not a frontend display issue.
Please handle this as soon as possible and inform me of the specific backup timestamp used for the restoration.