> For the complete documentation index, see [llms.txt](https://archer-bot.gitbook.io/archer.bot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://archer-bot.gitbook.io/archer.bot/troubleshooting/common-issues.md).

# Common Issues

## Sign-in fails, or wallet screens will not load (403 errors)

Symptoms: signing in hangs or fails, signature prompts never appear, and the browser console shows `403` responses from `privy.archerprotocol.com` (script chunks, `/api/v1/sessions`, or `/api/v1/passkeys/...`), often alongside a "blocked by CORS policy" message.

Cause: the browser is holding stale data for the wallet service on that domain. Two kinds of stale state produce this: a cached page that references an old release of the wallet service, and an expired anti-bot cookie that the service's edge network then rejects. The service itself is up; only the affected browser is blocked, and the CORS message is a side effect of the blocked response rather than the real problem.

Fix, in the affected browser:

1. Close the Archer app tabs.
2. Clear site data for **both** `app.archerprotocol.com` and `privy.archerprotocol.com`. In Chrome: open DevTools on each site → Application tab → Storage → "Clear site data". Use DevTools rather than the address-bar padlock menu; the padlock option leaves the service worker in place.
3. If you are on a VPN, turn it off for the sign-in.
4. Sign in again.

## "The wallet paying for this request is not available in this session"

Right after a fresh sign-in, the embedded wallet can take a few seconds to load into the session. If you see this message on a payment card, reload the page, send your request again, and pay from the new card.

## Errors shown by external apps connected over WalletConnect

When you connect your Archer wallet to an external app over WalletConnect, that app runs its own interface and error handling. Sometimes the app shows an error that does not reflect what Archer actually does. If you approve a request in the Archer modal, Archer signs and submits it on-chain regardless of what the app's screen says. Check the receipt link Archer shows after signing to confirm the result.

### Aave

Aave's app may display "There was some error. Please try changing the parameters" on its own modal when you start a supply, borrow, or repay, even though the request reached Archer and can be approved normally. This is usually Aave's own wallet-client handling, and it is more likely when several browser wallet extensions (for example MetaMask, Rabby, or HashPack) are installed at once and compete for the page's wallet provider.

What to do:

1. Approve the request in the Archer modal as usual. Archer signs and submits it.
2. Check the receipt link Archer shows after signing to confirm it went through.
3. If Aave keeps erroring, try a browser profile with other wallet extensions disabled.