Question

1password not working well with subdomains

Forum|Forum|13 days ago
September 18, 2026
5 replies
8 views

Hi

I have a VPS with a number of services, each on a separate subdomain.

The issue is that 1password keeps showing me the wrong login.

Example

Passwords saved on: n8n.vps.com, blog.vps.com, coolify.vps.com

When I open n8n.vps.com for example, it shows me the login for blog.vps.com

In the example below, it’s showing me the login for designer.vps.com instead of the n8n login.

And it becomes annoying when

Is this a known issue?

I think the priority should be fixed. When a login matches the subdomain exactly, it should have priority over other logins from the same domain.

I hope you can fix this soon

PS: Interestingly, the “Open And Fill” feature seems to pick up the right subdomain.

Best regards

ChrisC1P

1Password Employee

Hi @unlocomqx thanks for reaching out!

You can configure the autofill behaviour of your different login items to only fill on specific domains: Change where a login is suggested and filled | 1Password Support

Does the behaviour improve after setting your login items to Only fill on this exact host?

Let me know if you have any questions.

U

unlocomqxAuthor

Hi @ChrisC1P, thank you for your reply.

Tbh, It’s not convenient to go through my logins and change their settings.

The extension just has to prioritize the login that matches the current subdomain exactly.

Currently, I think it picks the first login that matches the current domain. (the first alphabetically)

Example with explanation

I hope you can improve the logic. Please tell me if something is not clear.

Thank you

ChrisC1P

1Password Employee

Hi @unlocomqx thanks for sharing those screenshots and for providing that extra context.

I agree that an exact match should normally take priority over broader matches for your subdomains. Our developers are working to improve the accuracy of suggestions when logging into subdomains and I’ve submitted your feedback internally.

As a temporary workaround, the exact-host setting remains available for the most sensitive or frequently used items, but I understand why that doesn’t scale for your setup. Thanks for taking the time to report this in such a detailed manner. Let me know if you have any questions.

Sign up

1Password employees: Sign in with SSO

Login to the community

1Password employees: Sign in with SSO