# Lighter Sign Message Popup Not Showing? Fix the Signature Prompt

> The Lighter connect button fires but no sign-message popup appears. The causes in order (hidden wallet window, queued request, locked wallet, two extensions), and how to check each.

Source: https://lighterpedia.com/troubleshooting/lighter-sign-message-popup-not-showing

You click **Connect Wallet** on Lighter, pick your wallet, and then nothing happens. No signature prompt, no error, just a button that looks like it is still thinking. The connection has stalled, and it is almost never a problem with Lighter or with your funds.

The reason it feels alarming is that the failure is silent. The site has handed a request to your wallet and is waiting for an answer. Your wallet has taken the request. What has not happened is the part you can see: the wallet putting a window in front of you. Below are the causes in the order they actually come up, what to check for each, and how to tell the difference between a wallet problem and a page problem.

A missing signature prompt is a **display failure, not a signing failure**. The request usually arrived. Click your wallet's **extension icon in the browser toolbar** first: if a pending request is sitting there, the window simply opened somewhere you could not see it, or queued behind an earlier one. A login signature is a **free, gasless message**, so nothing is at risk while you work through this.

## What is Lighter actually asking for?

Lighter has no email and no password. Your wallet is your login, and the way you prove you control an address is to sign a plain message. That signature is free, produces no on-chain transaction, and moves nothing. Our [connect a wallet and deposit walkthrough](/guides/getting-started/connect-wallet-deposit-lighter) covers the normal flow at **[app.lighter.xyz](https://app.lighter.xyz/?referral=LIGHTERPEDIA)**: choose your wallet, approve the signature request, and the app recognizes the address.

That matters here for one reason. Because it is a message and not a transaction, a failure to sign has no cost and no on-chain trace. There is nothing to reverse and nothing stuck. You are simply not logged in yet.

A login prompt should be a plain message signature. If what appears is a token approval or a transfer request, that is not the Lighter login step. Close it and check the URL in your address bar before approving anything.

## Why does the sign message popup not appear?

These are the usual culprits, roughly in order of how often they come up.

### 1. The wallet window opened behind the browser

Wallet extensions raise their prompt in a separate browser window rather than inside the page. That window can land behind the browser you are looking at, on a second monitor, or on another desktop, and on some setups it does not get raised to the front at all. MetaMask has an open report titled exactly that, [extension window doesn't popup on request](https://github.com/MetaMask/metamask-extension/issues/13590).

**Check it:** click the wallet extension icon in your browser toolbar. If the request arrived, it is there. MetaMask also shows a count badge on the icon when something is pending. Alt-Tab, or a look at your other monitor, finds the stray window.

### 2. An earlier request is still queued

Wallets answer one request at a time. If you left a prompt unanswered ten minutes ago on another tab, the Lighter request goes into the queue behind it and never surfaces on its own. MetaMask's own tracker describes both halves of this: [requests stack up with no way to reject them all](https://github.com/MetaMask/metamask-extension/issues/13201), and [a request sent while the MetaMask screen is already open does not show until you close and reopen it](https://github.com/MetaMask/metamask-extension/issues/4821).

**Check it:** open the extension and clear whatever is waiting, approving or rejecting as appropriate. Then reload Lighter and connect again. The queue drains in order, so the oldest item has to go first.

### 3. The wallet is locked

A locked wallet cannot sign, so it does not raise a signing prompt. Some wallets show the unlock screen instead, some show nothing in the page at all, and if you unlock in a different window the original request may have already been dropped.

**What to do:** open the extension, unlock it, then trigger the connection again from Lighter rather than waiting for the old request to reappear.

### 4. Two wallet extensions are fighting over the same button

If you have more than one wallet extension installed, they can both claim the same injected connection point in the page, and whichever one wins is not necessarily the one you picked. The prompt then arrives in a wallet you are not looking at, or nowhere. This conflict is well enough known that Ethereum standardized a fix for it, [EIP-6963](https://eips.ethereum.org/EIPS/eip-6963), which lets a site discover every installed wallet separately instead of guessing.

**Check it:** open every wallet extension you have installed and look for a pending request in each. As a longer-term fix, disable the wallets you do not use in that browser profile, or keep a profile that has only one.

### 5. The page loaded before the extension did

A tab that was already open when you installed, updated, or re-enabled the extension is running against a page that never saw the wallet. The connect button then does nothing at all, because there is nothing on the other end of it.

**What to do:** close the tab, open a new one, and go to the app again. This also clears a stale page that has been sitting open through a wallet update.

### 6. The wrong browser profile

Extensions are installed per browser profile, not per machine. A guest window, a work profile, or a second browser will not have your wallet even though the same computer does. The symptom is identical to a broken popup.

**Check it:** confirm the wallet icon is visible in the toolbar of the exact window you are using.

### 7. On mobile, the session has dropped

Through WalletConnect or a wallet's in-app browser, the prompt has to travel to a separate app, and that hop is where mobile prompts go missing. MetaMask's mobile tracker records the pattern directly: [the signature popup sometimes does not show, sometimes takes 20 to 30 seconds, and sometimes surfaces minutes late](https://github.com/MetaMask/metamask-mobile/issues/9116).

**What to do:** switch to the wallet app by hand rather than waiting to be switched. If nothing is waiting there, end the WalletConnect session from the wallet side and start a fresh one.

## The order to work through it

## What else could it be?

Two failures get confused with this one, and both have different answers.

- **Funds that do not appear after a transfer.** That is an on-chain question, and the block explorer is the source of truth rather than the app. We cover it in [Lighter deposit not showing](/troubleshooting/lighter-deposit-not-showing).
- **A prompt that appears and asks for something else.** A seed phrase is never requested by any legitimate wallet flow, and a login is never a transfer. Verify the domain before approving anything, and read [whether Lighter is safe, and what verifiable actually means here](/privacy/is-lighter-safe-verifiable) for the wider security picture.

## How do you stop it happening again?

Most of this is browser housekeeping rather than anything to do with Lighter.

- Pin the wallet extension so the pending-request badge is always visible.
- Answer prompts as they arrive instead of leaving them open on background tabs.
- Keep one wallet extension enabled per browser profile.
- Reload after a wallet update before connecting anywhere.
- Bookmark the official app and open it from the bookmark, which also removes a phishing route.

None of this touches your balance. A signature you never gave is a login you never completed, and the [zero-fee trading](/guides/fees/lighter-fees-explained) waiting on the other side of it is unchanged whenever you get there.

If the extension icon shows no pending request at all after several attempts, the request is not reaching the wallet. That points at the browser rather than at the wallet: a blocked or disabled extension, a hardened privacy setting, or an extension conflict. A fresh browser profile with only the wallet installed settles it quickly.

## FAQ

### Why does the Lighter sign message popup not appear?

Almost always because the request reached your wallet but the wallet did not put a window in front of you. The notification window can open behind the browser, it can queue behind an earlier request you never answered, it will not appear at all while the wallet is locked, and it can be swallowed when two wallet extensions are both claiming the connect button. Clicking the wallet extension icon in your browser toolbar shows any request that is waiting, which tells you within a second whether the request arrived.

### Is the Lighter signature request a transaction?

No. Connecting to Lighter asks you to sign a plain message, which is free, gasless, and moves no funds. It proves you control the address. If the prompt you are looking at is a token approval or a transfer rather than a message signature, that is not the login step, and you should stop and re-check the URL you are on before approving it.

### How do I see a signature request that never popped up?

Click your wallet's extension icon in the browser toolbar. MetaMask and Rabby both show pending requests there, and MetaMask shows a count badge on the icon when something is waiting. Answering or rejecting the queued request clears the backlog, and the next request from the site will surface normally.

### Why does the popup work in one browser but not another?

Because the wallet extension is per browser profile, not per machine. A profile where the extension is not installed, is disabled for that site, or was installed after the tab was opened will not raise a prompt. Opening the app in a fresh tab of the profile that has the wallet, then connecting again, separates a wallet problem from a page problem.

### Nothing works. Is my deposit affected?

No. A signature that never appeared means you were not logged in, not that anything moved. It is a separate failure from funds not appearing after a transfer, which is an on-chain question you check on a block explorer rather than in the app.