If you cannot access, retrieve, preview, or download a file in ArDrive Web, the issue may be related to temporary gateway availability, indexing delays, or frontend connectivity.

ArDrive retrieves file data through Arweave gateways. During periods of heavy network activity, gateway maintenance, AR.IO routing issues, or temporary gateway errors, a file may fail to load even if it is still stored permanently on Arweave.

If you are seeing 502, 503, 504, bad gateway, network, resource, AR.IO, GraphQL, gateway, or frontend errors, see Bad Gateway And Network Errors.

The browser console is the best place to confirm whether the file issue is a gateway, network, resource, GraphQL, AR.IO, or frontend error. See Check Browser Console Logs.

Common signs include:

• 502, 503, or 504 errors

• "Bad Gateway" errors

• Failed download, preview, or file retrieval requests

• Network or resource errors in the browser console

• Gateway, AR.IO, GraphQL, or frontend errors while opening a file

What to do

• Refresh ArDrive and try opening or downloading the file again.

• Wait a few minutes and retry if you are seeing 502, 503, 504, or bad gateway errors.

• Try a different browser or private window to rule out cached frontend issues.

• If you have a public preview link or transaction ID, try opening it again later after gateway indexing catches up.

• If the file should be in your drive but does not appear, or its status is stuck red or orange, try manually syncing your drive. See Sync Your Drive.

• Advanced users can try changing the data gateway and GraphQL gateway. See Change Gateway URL For ArDrive.

• If the problem continues, visit our contact page and include the file link or transaction ID if available, plus any browser console errors you saw.