Browser console logs are often the best way to understand what is happening when ArDrive Web does not load, log in, sync, preview, upload, download, access, or retrieve a file as expected.

Console logs can show whether the issue looks like a password or wallet problem, a frontend issue, a failed network request, a gateway issue, an AR.IO issue, or a 502, 503, 504, or bad gateway error.

How to open the browser console

• In Chrome, Edge, Brave, or Firefox, right-click anywhere on the page and select Inspect, then open the Console tab.

• You can also press F12 or Ctrl+Shift+J on Windows and Linux.

• On Mac, press Cmd+Option+J in Chrome, Edge, or Brave. In Firefox, press Cmd+Option+K.

• In Safari, enable the Develop menu first from Safari settings, then choose Develop > Show JavaScript Console.

What to look for

• 502, 503, 504, or "Bad Gateway" errors

• Failed network requests

• Network or resource errors

• AR.IO, GraphQL, gateway, or frontend errors

• Invalid password, invalid keyfile, wallet, or authentication messages

What to send support

If you contact us, include what you were trying to do and the console errors you saw. A screenshot of the console is helpful.

Do not share your password, seed phrase, private key, or wallet keyfile. If a screenshot includes sensitive information, hide it before sending.