If you are having trouble logging in to ArDrive Web, first check whether the issue looks like a password, keyfile, seed phrase, or wallet problem.

If ArDrive shows an invalid password or invalid keyfile message, double-check that you are using the correct wallet keyfile and password.

If you are using a seed phrase, make sure the phrase belongs to the wallet you expect to access. If you are using ArConnect or another wallet connection, make sure the wallet is unlocked and connected to the correct account.

If you do not see an invalid password or wallet message, and instead see repeated network, resource, 502, 503, 504, bad gateway, AR.IO, GraphQL, or frontend errors, the issue may not be your password or keyfile. See Bad Gateway And Network Errors.

The browser console is the best place to confirm whether the login issue is a password, wallet, gateway, network, or frontend error. See Check Browser Console Logs.

What to do

• Confirm you are using the correct keyfile, seed phrase, wallet, and password.

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

• Refresh ArDrive and try logging in again.

• If the browser console shows 502, 503, 504, bad gateway, network, resource, AR.IO, GraphQL, or frontend errors, see Bad Gateway And Network Errors.

• If the problem continues, visit our contact page and include how you are logging in, whether you saw an invalid password message, and any browser console errors you saw.