Why the Confirm button is greyed out
Seen a greyed-out confirm button while trying to sign a transaction? You're not alone. In my experience this shows up for three broad reasons: the wallet needs a missing step (unlock or hardware confirmation), the transaction payload requires contract-data permissions, or the client is still estimating gas/nonce or waiting for an RPC response. Short pause. Then action.
Users searching for "confirm button greyed out MetaMask Ledger" often find that the device or MetaMask is waiting for the other side to be ready. But there are other, less obvious causes too: custom RPC timeouts, EIP-1559 parameter mismatches, or a dApp expecting a different signing flow (WalletConnect vs injected provider).
If you want to confirm this transaction in your wallet MetaMask, start with the simple checks below.
Quick checklist: immediate fixes
- Unlock MetaMask and make sure the correct account is selected. Simple, but often missed.
- If using Ledger, open the correct app on the device (for EVM transactions: the Ethereum app). (Yes, hardware must be awake.)
- Wait for MetaMask’s gas estimation to finish. If it spins for >30s, try switching networks or retrying.
- Disable any interfering extension (privacy blockers or tab-sandbox add-ons) and refresh the page.
- Try a different connection method (USB vs WebHID) or use the mobile app.
And yes, restart your browser if nothing else works.
How to confirm the transaction in MetaMask wallet — step by step
Below I describe the common flows I use daily. These are practical actions you can take now.
Browser extension (desktop)
- Click the dApp action that triggers a MetaMask popup.
- Check the popup: verify the destination address, token amounts, and gas settings.
- If the confirm button is greyed out, watch the status line: is MetaMask "Estimating gas" or "Waiting for Ledger"?
- If estimation is ongoing, wait 15–30 seconds. If it stalls, switch your RPC (see custom-rpc-network-settings).
- Once ready, click Confirm. If the transaction needs external signing, follow prompts on your hardware device.
Mobile app (iOS / Android)
- Tap the action in the dApp browser or follow the deep link from the website.
- Mobile shows a full-screen transaction review — check the gas (EIP-1559 fields if shown). If the Confirm button is greyed out, confirm the network at the top.
- Use WalletConnect if the dApp requires it; follow the QR/connect steps from the walletconnect-guide.
Hardware wallet (Ledger) specifics
When MetaMask asks you to "confirm the transaction in MetaMask wallet," the hardware path adds a second step: confirm on the Ledger device. Typical sequence:
- Connect Ledger via USB (or Bluetooth where supported) and unlock it.
- Open the Ethereum app on the device.
- Approve the transaction details on the device screen; the device will show a summary.
If the MetaMask confirm button remains disabled even though the Ledger is unlocked, jump to the Ledger section below or see ledger-with-metamask-guide.
Ledger-specific failures: "failed to sign with ledger device MetaMask"
Common symptom: MetaMask shows a prompt but returns an error like failed to sign with ledger device MetaMask (or the confirm button greyed out MetaMask Ledger). Here are tested fixes I use:
- Update Ledger firmware and update the Ethereum app on the device.
- In the Ethereum app settings on the Ledger device, enable contract data / allow contract data if you are interacting with a smart contract (tokens, DeFi). This is necessary for contract interactions that include data payloads.
- Try the alternate transport method: switch between WebHID and U2F (browser-dependent) or connect through the Ledger Live bridge if supported.
- Close and reopen MetaMask; reconnect the hardware account via hardware-wallets-with-metamask.
If none of these resolve the error, see ledger-errors-and-troubleshooting for deeper logs and known bug workarounds.
Advanced causes: RPC, nonce, EIP-1559 and gas estimation
Sometimes the problem is not the UI but the underlying transaction parameters.
- RPC node timeout: a slow or overloaded RPC provider will stall gas estimation and leave Confirm disabled.
- Incorrect nonce (manual nonces or duplicated pending transactions) prevents the transaction builder from enabling Confirm.
- EIP-1559 fields: if you manually set a priority fee that is invalid on the selected network, MetaMask can block confirmation.
Fixes: switch RPC or network, reset nonce by clearing pending transactions (see pending-transaction-troubleshooting), or use the "Advanced" gas options and revert changes.
When dApps or WalletConnect block confirmation
Some dApps expect a particular signing flow. For example, a dApp might open a WalletConnect session instead of using the injected provider. That mismatch can show a confirm button that's disabled because MetaMask is not the active signer.
Try these steps:
- Reconnect the dApp and explicitly choose the correct connection method.
- In MetaMask, disconnect the site and reconnect (see disconnect-connected-sites).
- If the dApp requires contract approvals, confirm the approval first (or revoke and retry—see token-allowances-and-revoke).
Safety checklist before you hit Confirm
- Verify destination address visually. Do not paste and trust a copy-only check. Phishing dApps can swap addresses.
- Check the method being called (transfer vs approve vs swap). Approve operations can grant unlimited token allowance.
- For hardware wallets: confirm the transaction summary on the device screen (amount, recipient, and any contract data).
But remember: convenience trades off with security. A hot wallet is convenient. Consider a hardware device for large holdings.
Troubleshooting table: symptoms → likely cause → fix
| Symptom |
Likely cause |
Quick fix |
| Confirm button greyed out (desktop) |
Gas estimation pending / RPC timeout |
Switch RPC, reload page, retry |
| Confirm requires device confirmation but device shows nothing |
Ledger app not open, or no browser support enabled |
Open Ethereum app, enable contract data, reconnect |
| MetaMask shows error "failed to sign" |
Transport mismatch or outdated firmware |
Update firmware, try WebHID or Ledger Live bridge |
| Confirm disabled only on a specific dApp |
dApp expects WalletConnect or different provider |
Reconnect using correct method (see walletconnect-guide) |
(Placeholder image: screenshot-placeholder-confirm-button-greyed-out)
FAQ
Q: Is it safe to keep crypto in a hot wallet?
A: Hot wallets are designed for daily use. They are convenient for DeFi swaps and staking but less secure than hardware or offline storage for long-term holdings. See security-checklist for mitigations.
Q: How do I recover if the confirm button remains disabled after troubleshooting?
A: Export transaction details (hash, nonce) and follow the steps in transaction-errors-and-fixes or reset MetaMask after backing up your seed phrase (seed-phrase-backup-recovery).
Q: What happens if I lose my phone while using MetaMask Mobile?
A: Use your seed phrase to restore the wallet on a new device. Keep your seed offline and never share it.
Conclusion and next steps
Greyed-out confirm buttons and signing failures are annoying but usually resolvable with a short checklist: confirm the account and network, update and open the Ledger app (if using hardware), switch RPCs, and verify gas/nonce settings. I’ve run into these several times, and the diagnosis usually comes down to one missing step. Try the quick checklist first; if the error persists, follow the Ledger troubleshooting steps or the pending transaction guide.
If you want deeper guides, check: ledger-with-metamask-guide, pending-transaction-troubleshooting, and reset-delete-and-reinstall.
Need step-by-step help for a specific error message? I can walk through the exact screen you see and suggest the next action. Click through the relevant internal guides above and keep your seed phrase secure.
