Wallet Connection
Troubleshoot Web3 wallet connection problems. --- If MetaMask is installed but not detected: 1. Check MetaMask extension is enabled 2. Refresh the page 3. Try...
Wallet Connection Issues
Troubleshoot Web3 wallet connection problems.
MetaMask Connection
"Please Install MetaMask"
If MetaMask is installed but not detected:
- Check MetaMask extension is enabled
- Refresh the page
- Try clicking MetaMask extension icon first
- Restart browser
"Connection Rejected"
User rejected connection:
- Click "Connect Wallet" again
- When MetaMask popup appears, click "Connect"
- Select accounts to connect
"Already Processing"
MetaMask request pending:
- Click MetaMask extension icon
- Approve or reject pending request
- Try connecting again
WalletConnect Issues
QR Code Not Scanning
- Ensure good lighting
- Clean camera lens
- Try zooming on QR code
- Use "Copy to clipboard" option instead
"Connection Timeout"
WalletConnect session expired:
- Refresh page
- Click "Connect Wallet" again
- Scan new QR code
Mobile Wallet Not Opening
- Ensure wallet app is installed
- Try "Open in App" link
- Manually open wallet and scan QR
Signature Request Failed
"User Rejected Signing"
For SIWE (Sign-In with Ethereum):
- Click "Connect Wallet"
- Approve connection
- When signature request appears, click "Sign"
"Invalid Signature"
Possible causes:
- Wrong account selected
- Transaction modified
- Network issue
Try:
- Disconnect wallet
- Reconnect with correct account
- Sign again
Wrong Network
"Please Switch Network"
BlockSecOps works with any EVM network for auth.
If prompted to switch:
- Open MetaMask
- Click network selector
- Switch to requested network
- Or dismiss and continue
Account Selection
Wrong Account Connected
To change connected account:
- Open wallet extension
- Click account icon
- Switch to correct account
- Refresh BlockSecOps page
Multiple Accounts
If you have multiple accounts:
- Decide which to use for BlockSecOps
- Select only that account when connecting
- Consistent account = consistent profile
Wallet Locked
"Please Unlock Wallet"
- Click wallet extension icon
- Enter your password
- Return to BlockSecOps
- Try connecting again
Auto-Lock Settings
To prevent frequent unlocking:
- Open wallet settings
- Adjust auto-lock timer
- Consider longer timeout for active sessions
Browser Compatibility
Supported Browsers
Web3 wallets work best in:
- Chrome (recommended)
- Firefox
- Brave
- Edge
Mobile Browsers
For mobile:
- Use in-app browser from wallet app
- Or use WalletConnect with separate browser
Safari Limitations
Safari may have issues with:
- Extension detection
- Popup handling
- WalletConnect deep links
Try Chrome or Firefox for best experience.
Extension Conflicts
Multiple Wallet Extensions
Having multiple wallets installed can cause conflicts:
- MetaMask
- Coinbase Wallet
- Phantom
- Rabby
Try:
- Disable other wallet extensions
- Keep only one enabled
- Refresh page
Ad Blockers
Some ad blockers interfere with wallet connections:
- Disable ad blocker for blocksecops.com
- Add to allowlist
- Try incognito without extensions
Hardware Wallets
Ledger/Trezor via MetaMask
- Connect hardware wallet to computer
- Open MetaMask
- Select hardware wallet account
- Approve connection on device
- Approve signature on device
"Device Not Found"
- Ensure device is connected and unlocked
- Open Ethereum app on device
- Enable "blind signing" if needed
- Try different USB port
Mobile Wallet Apps
Not Redirecting to App
If clicking "Open in App" doesn't work:
- Ensure wallet app is installed
- Try copying the WalletConnect URI
- Paste in wallet app manually
Session Disconnected
Mobile sessions may disconnect:
- Return to BlockSecOps page
- Click "Connect Wallet" again
- Scan new QR or deep link
Clearing Wallet Connection
Disconnect in BlockSecOps
- Click your profile icon
- Click "Disconnect Wallet"
- Confirm disconnection
Disconnect in Wallet
- Open MetaMask
- Click connected sites
- Find BlockSecOps
- Click "Disconnect"
Fresh Connection
For a completely fresh start:
- Disconnect in both places
- Clear browser cache
- Reconnect
Security Best Practices
Verify Connection Requests
Always check:
- URL is blocksecops.com
- Request is for signing, not transaction
- No unexpected permissions requested
Signing Messages
BlockSecOps only requests message signing (SIWE):
- No transaction approval needed
- No token approvals
- No gas fees
If asked for anything else, do not approve.
Solana Wallet Issues
Phantom Connection
"Phantom Not Detected"
- Check Phantom extension is installed
- Ensure Phantom is enabled in browser
- Refresh the page
- Click Phantom icon to ensure it's unlocked
"Connection Rejected"
- Click "Connect Solana" again
- When Phantom popup appears, click "Connect"
- Select the account you want to use
Solflare Connection
"Solflare Not Found"
- Verify Solflare extension is installed
- Try clicking Solflare icon first
- Refresh BlockSecOps page
Backpack Connection
"Backpack Connection Failed"
- Check Backpack extension is enabled
- Ensure Backpack is unlocked
- Try reconnecting
Solana Signature Issues
"Signature Verification Failed"
- Ensure you signed the message (didn't reject)
- Try disconnecting and reconnecting
- Check your Solana wallet is on mainnet
"Invalid Solana Address"
- Make sure wallet is connected
- Verify the address is a valid Solana address (base58)
- Try with a different wallet
Still Having Issues?
Provide to support:
- Wallet type (MetaMask, WalletConnect, Phantom, Solflare, etc.)
- Browser and version
- Device (desktop/mobile)
- Blockchain (Ethereum or Solana)
- Exact error message
- Steps tried
See Contact Support.