Fankex

Enter a keyword to search published documentation.

mywebdrive

Troubleshooting

Diagnose sign-in, upload, download, catalogue, metrics, and local runtime issues with safe evidence.

Keep useful, safe evidence

Record the time, page, operation, HTTP status, and a redacted error. Distinguish between no data, no permission, pending processing, and service failure. Never paste codes, cookies, access tokens, grants, complete share links, or user records into Ask Docs.

Sign-in and mail

SymptomCheck and next step
Mail missingCheck the address and spam folder; wait 60 seconds; 202 doesn't mean actual receipt
Six digits rejectedUse the latest challenge, same email, include leading zeros, mind the 10-minute lifetime, and ensure it hasn't been consumed
429Wait for the limit to reset or obtain a new valid challenge; don't keep guessing
Local port 8025 has no inboxfake-email has no public inbox UI; private test reads require a token not present in the default overlay
Signed out after reloadCheck the HTTPS same-origin entry point, cookie, and session validity; sign in again
Old password/invitation flow failsThe active flow uses email codes; archived registration instructions don't apply

Uploads and files

SymptomCheck and next step
Processing after 100%Parts arrived; wait and refresh, then inspect version, size, and downloaded content
Same-name new upload conflictsThere's no automatic overwrite; use the target fileId's replacement-intent API when replacing
Empty file rejectedChoose a nonempty file; sizeBytes must be a positive decimal string
Upload 401uploadGrant lasts at most 300 seconds, not the intent's 15 minutes
Cancellation failed or space stays reservedReread quota and intent/expiry state; avoid multiplying reservations
File exists but can't downloadcurrentVersion may still be null; a name alone doesn't prove finalization
No delete, move, or restore buttonThese operations are absent from the current account page

For stuck processing, operators can inspect storage-worker, Core callbacks, Redis, object storage, and the database. Don't invoke internal completion from the browser or directly alter quota records.

Downloads, shares and publications

Tickets last 60 seconds and are single-use. A stale address or reused grant fails—initiate a new download for a new ticket. Blob-based browser downloads can require considerable memory and are affected by network interruptions.

A share 404 may mean wrong password, expiry, exhausted allowance, revocation, or an unavailable file. Ask the sender. Ticket issuance consumes the share allowance; an interrupted transfer doesn't guarantee a refund. Successful Download metrics use a different completion criterion.

Uploading doesn't automatically list a file on /download; publication with published status is needed. Draft and disabled records stay private. The current catalogue only reads the first page and has no pagination controls; use the paginated API if you need to look further. The admin publication page lists the administrator's own files.

Administrative data

For 401/403, check identity and role; for 503, check dependencies. Empty results differ from loading errors. partial/unavailable or null system-health values aren't healthy zeros. Check freshness, coverage, and the Asia/Shanghai date range for analytics.

Requery notifications after SSE reconnects rather than expecting history replay. Read state doesn't establish that an incident has been resolved.

Local runtime and releases

If Docker can't connect, start your Docker service. Old Compose can't apply !override correctly. Inspect ./manage-services.sh status, logs core-api, and logs storage-worker. reset --confirm deletes local data volumes and isn't a substitute for diagnosis.

A production exit 75 means there's an active release lock—inspect the current release instead of removing the lock. Rollback requires a recorded manifest and doesn't restore backups automatically. See Local development and Deployment.