LastPass Won’t Launch Site | Quick Fix Guide

Seeing the Launch button do nothing can stall your workflow. The good news: it’s almost always a small mismatch—blocked pop-ups, a malformed URL, or a default browser handoff that’s off. This guide gives you fast checks first, then deeper fixes that work on Chrome, Firefox, Edge, and Safari. You’ll also find two compact tables so you can skim and act right away.

Site Not Opening From LastPass Vault: Fast Checks

Start with the handful of triggers that cause the Launch action to fail most often. Knock these out in order, then try again.

Why The Launch Button Fails

The Launch feature opens the site stored in a vault entry and passes control to your browser. If any link in that chain breaks—pop-up rules, URL matching, or browser defaults—the click appears to do nothing. Here’s what tends to block it.

Blocked Pop-Ups Or Redirects

Browsers block unwanted windows by default. The vault opens the target page in a new tab or window, so a strict rule can stop it. Allow pop-ups for the target domain and, if needed, for the vault’s domain as well. You can grant a site-level exception in minutes. If you use strict tracking protection or a hardening extension, add the same allowlist there too.

Malformed Or Partial URLs In The Entry

A stored address like example.com/login without a scheme can fail to launch. Use the full form—https://example.com/login. Also check if your account signs in at accounts.example.com or another subdomain. The address in the entry should match the page that actually loads the sign-in fields.

Subdomain Drift And Equivalent Domains

Some brands spread sign-in over multiple hosts—think shop.example.com, login.example.com, and a regional domain. If the vault entry points to one host and the site shifts you to another, Launch can appear unresponsive or open the wrong place. Use equivalent domains so related hosts match cleanly, or create a separate entry for each login host.

“Never URL” And Fill Preferences

If a site got added to a Never list by mistake, Launch and autofill feel disabled. Remove it. Also ensure autofill is enabled and that warnings on insecure forms aren’t stopping the action on mixed-content pages.

Iframe Login Screens

Some services tuck the login inside an embedded frame. When the visible page isn’t the same origin as the actual login host, Launch and matching behave strangely. Open the real sign-in URL in a tab, save that address to the entry, and try again.

Default Browser Handoff

Launch hands the address to your system default browser. If the OS points to an uninstalled or outdated app—or a profile with strict pop-up blocking—the handoff stalls. Set your daily driver as the default and test again.

Extension State Or Cache

After long sessions, the add-on can hold stale state. Logging out and back in, refreshing the vault, or reinstalling the extension often clears the block. A full browser update helps too.

Step-By-Step Fix That Works

Walk through these steps once. In most cases, Launch comes back before you finish the list.

1) Update The Site Record

1. Open the vault entry.
2. Copy the login page URL directly from a fresh browser tab where you can see the username and password fields.
3. Paste it into the entry’s URL field. Keep the scheme (https://) and the right host.
4. Save and try Launch.

2) Allow Pop-Ups Where Needed

Grant a site exception for the target domain. If Launch still doesn’t open a tab, give an exception to the vault site as well. Many users only need one of the two.

Chrome users can follow the steps under block or allow pop-ups. The same idea applies in other browsers—site-level allowlists work best.

3) Fix Subdomain And Domain Matching

• If your brand has multiple login hosts, store the exact one that shows the form.
• Use equivalent domains to reconcile related hosts. This keeps matching tidy when services switch between regional or brand domains.
• If switching hosts is part of the login flow, create a second entry dedicated to the redirected host and Launch that one.

4) Remove “Never” Rules And Re-enable Fill

Open advanced options and remove any Never rules for the domain. Turn autofill back on. If you’re warned about mixed content or insecure fields, switch to the secure login page and save that URL.

5) Reset The Extension State

1. Log out of the add-on.
2. Close the browser, wait a few seconds, and open it again.
3. Log back in and refresh the vault.
4. If Launch still fails, remove and reinstall the extension, then test once more.

6) Align The Default Browser

Set the browser you actually use as the OS default. This avoids a handoff to an unused app or a profile with stricter pop-up rules. On Windows, adjust Default apps; on a Mac, pick your browser in System Settings → Desktop & Dock (or General on older versions).

7) Watch For Iframes And Mixed Content

If the sign-in lives inside an embedded frame, grab the address of the page inside the frame and save that as the entry. Launch now targets the right origin.

Deep Dives: Matching Rules That Matter

Matching isn’t guesswork. The vault compares your saved address with the page you’re on, with options that fine-tune the result.

URL Rules

URL Rules let you refine how entries match. If you keep multiple logins under one domain—say, separate accounts for app.example.com and admin.example.com—rules prevent cross-suggestions and smooth the Launch action. A tidy set of rules also reduces noisy prompts during redirects.

Equivalent Domains

Use equivalent domains when a brand owns several top-level domains or regional sites. Pair them so Launch follows across example.com, example.co.uk, and example.de without confusion. Business users may see admin-set pairs that cannot be edited.

Never URLs And Fill Warnings

Never rules are handy on portals that you don’t want to launch or fill. If you change your mind, remove them, then test. Also check any preference that blocks filling on insecure forms, since that can make Launch feel unresponsive on mixed pages.

Troubleshooting Paths For Each Browser

Use this table to adjust the two settings that trip Launch most: pop-ups and default browser behavior.

When Launch Still Won’t Open A Tab

If the problem survives the steps above, the page flow may be unusual. Try these workarounds, then update your entry so it works one-click next time.

Open The Login Page Manually, Then Resave

Type the login address directly in a tab and sign in with the vault. Once confirmed, overwrite the entry’s URL with the exact page you used.

Split One Entry Into Two

Some services push you through a branded gateway before sending you to an identity provider. Save both addresses as separate entries—Gateway and Identity—and Launch the one you need for each session.

Strip Tracking Parameters

If the saved address contains a long string of parameters, trim to a clean login URL. Many trackers expire and break Launch later.

Test In A Fresh Profile

Create a new browser profile with no extra extensions. Install only the password manager add-on and test Launch. If it works there, you’ve isolated a conflict in the original profile.

Security And Reliability Tips

• Keep the extension updated. New releases fix behavior on modern sites and browsers.
• Prefer the secure login host. Save the https:// address that actually shows the form.
• Use equivalent domains sparingly. Only pair hosts that truly belong together to prevent mismatches.
• Review Never rules twice a year. Remove entries you no longer need.
• When a site redesigns sign-in, resave the URL from a clean tab and test Launch that same day.

Trusted References

Need the official word on the core fixes? See the product’s guide on sites not launching and Google’s steps for allowing pop-ups. Both pages stay current and mirror the steps in this article.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback