Chrome Extension Cannot Access a Site? Check This First

If a Chrome extension cannot access one site, check site access on that tab. Open its Extensions menu, select This can read and change site data, and allow the current site. Refresh the page. If it still fails, check the Chrome profile, Incognito setting, and managed-browser policy before reinstalling or widening access.

You can try the MagicLess demo in the same Chrome profile. It simulates the steps without an extension; it cannot test permissions. For diagnosis, test the actual extension on another supported page you are authorized to use.

Site-access diagnosis table and repair checklist

Check access on the affected site

Use the narrowest access that completes your task.

1. Open the exact login page where the extension fails.
2. Select the Extensions icon to the right of the address bar.
3. Find the extension and open its menu.
4. Point to This can read and change site data.
5. Choose On [current site] for ongoing access to that site, or select the extension for temporary access in the open tab.
6. Refresh the page. Start the extension again with its button or shortcut.

The Details page also offers specific-site or all-site access. Do not widen access to fix one domain. User settings cannot add undeclared sites.

Confirm that the extension is enabled under More > Extensions > Manage extensions. If Chrome marks it as corrupted, use Repair. Reinstalling does not remove policy or make an unsupported page compatible.

For a general permission review before installation, see what to check before you install an OTP extension.

Check the Chrome profile and Incognito

Chrome profiles keep extensions and settings separate. Test in the profile where you installed the extension and connected Gmail. Do not switch profiles to evade work policy.

Extensions do not automatically run in Incognito. Under Manage extensions > Details, turn on Allow in incognito only when needed. Then refresh the private page.

Check managed-browser policy

Open chrome://management. If Chrome shows Managed by your organization, an administrator can control extensions and website access. Open chrome://policy to inspect the policies applied to that browser.

Chrome Enterprise documents two relevant controls. blocked_permissions can stop an extension that needs a prohibited permission. runtime_blocked_hosts can prevent interaction with selected sites. An administrator can set an approved runtime_allowed_hosts exception; the user cannot.

Do not remove management software, sideload another build, or move work data to a personal profile. Send IT:

• Extension name, store URL, and extension ID.
• Exact site origin without a private path or token.
• Exact error, timestamp, and redacted screenshot.
• Whether chrome://management reports management.
• Relevant names at chrome://policy.
• Business task and narrow host access requested.

The administrator can allow, limit, or deny the request.

When permission is not the problem

Chrome content scripts run only on declared page patterns. Programmatic injection needs host permission or temporary active-tab access. Permission still does not guarantee support for every custom field or embedded flow.

Check compatibility. If the extension works on another supported page in the same profile, report the difference. Do not keep widening permissions. The simulated demo cannot verify extension or Gmail access.

Keep Gmail authorization separate. Workspace OAuth controls inbox connection. Chrome site access controls interaction with the login page.

Illustrative example

Illustrative example, reviewed October 22, 2026; not a customer case: Ari's Gmail helper works on one approved site but not payroll in the same profile. The menu shows temporary on-select access.

Ari allows that site, refreshes, and starts a lookup. If the control is locked and chrome://management shows management, Ari stops and sends IT the site origin, extension ID, policy details, and business reason.

Where MagicLess fits

MagicLess checks connected Gmail inboxes on supported Chrome login pages. With auto-detection enabled, a recognized login page can trigger a lookup. You can also use its button or shortcut. You choose whether to fill the result. It does not read Outlook or SMS, poll Gmail continuously, bypass policy, or submit forms. See Chrome's separate Android SMS support.

FAQ

Why does an extension work on one site but not another?

Sites can have different permissions, policies, or page structures. Check current-site access and test the actual extension on another supported page in the same profile. The simulated demo does not test extension access.

Does Incognito use my normal extension settings?

Not automatically. Chrome requires you to enable Allow in incognito for each extension that you want there.

How do I know whether Chrome is managed?

Open chrome://management or check the bottom of Chrome's main menu for Managed by your organization. Use chrome://policy to inspect applied policies.

Can I override runtime_blocked_hosts?

No. It is an administrator policy. Ask for a narrow review or approved exception.

Why does the extension have access but still miss the field?

The page may use a custom or embedded login control that the extension does not support. A permission grants access; it does not guarantee compatibility.

Claim ledger

Sources