Troubleshooting
Use the HTTP response, job status, and source behavior to choose the next step.
Could not reach MediaFilez
This browser message means fetch could not expose a response. It can result from a connection failure, timeout, or CORS. It is not proof that your internet connection is down.
Check the browser Network panel for the OPTIONS request and the failing method. Website writes need credentialed CORS and a trusted origin. A backend caller using an API key does not rely on browser CORS.
The hosted API fix in v0.2.2 permits PATCH and DELETE preflights for configured website origins. Self-hosted deployments should check their own method list and reverse proxy. Do not use mode: 'no-cors'; it makes the response unreadable.
Accepted, but no file
202 is an acceptance response. Poll /jobs/:id and check status, phase, and error. A successful HTTP poll can return a failed job. Stop on terminal states instead of polling forever.
401 or 404
For 401, check the exact header Authorization: ApiKey YOUR_API_KEY, key expiry, and revocation. Do not send Bearer with a partner key.
For 404, check the ID and account that created the job or file. Private ownership failures also return 404. Reusing the source URL from another account does not grant access to its stored result.
429 and retries
Wait before retrying. Accounts share capacity across all keys and sessions. Slow down polling and wait for running work to finish. Preserve the idempotency key when retrying the same submission after a network error.
An album has one result
Inspect job.result.files. Reading only result.fileId intentionally retrieves the first file. If a source no longer exposes the full album, check the job error rather than returning partial success.
Download URL expired
Request /files/:id again with the owning account. Fetch the returned URL unchanged and without your API authorization header. In Discord, put the URL inside a Markdown link so surrounding punctuation stays outside it.
Source rejected the request
A source can require authentication, remove media, rate-limit a server, or change extraction behavior. Retry only when the failure is temporary. Do not send site cookies, passwords, or source-platform tokens to the hosted API.
Desktop users can review site sign-in and troubleshooting. Worker operators can inspect execution and cancellation.
Ask for help
Send [email protected] the endpoint, HTTP status, error code, approximate time, and requestId when provided. Remove API keys, cookies, OAuth codes, and signed download URLs before sharing logs. Report vulnerabilities privately to [email protected].