1Password always redirects to first URL in Firefox on filling (and then sometimes doesn't fill)

manski

1Password on Windows in Firefox always redirects to the first URL stored in a password entry - if the URL has no dot in its server name.

For example, I have two NAS systems running on https://nas1:5001/ and https://nas2:5001/. Both have the same admin credentials so I store both in a single entry in 1Password - with both URLs provided.

Now, when I'm in Firefox, navigate to https://nas2:5001/ and hit the "Fill Login" key combo (or use the 1Password icon in Firefox' toolbar), 1Password always redirects the page to https://nas1:5001/. So, I can't use 1Password to fill the password for the second NAS.

It doesn't happen for URLs that contain a dot (like https://google.com) and it also doesn't happen on macOS & Firefox, or in Chrome on Windows.

However, for some pages it's even redirecting when the URL already is correct - and then for some pages 1Password fails to fill the login altogether, so I have to manually fill it. As you can imagine, this is quite annoying.

I'm currently running Firefox 66.0.5 but I have observed this strange redirect behavior for quite some time (but it didn't occur to me until today that it could be related to URLs without dot).

---

1Password Version: 7.3.684
Extension Version: 4.7.3.90
OS Version: Windows 10 x64
Sync Type: Dropbox

manski

Edit: I just noticed that it redirects every time (and fails to fill the login data) even in Chrome.

bundtkate

Thanks for reaching out with this issue, @manski! Host names are yet supported for filling. If you change those URLs to ip_address:port, they should fill properly without reloading. Let me know if this helps. :chuffed:

manski

@bundtkate Hey. Thanks for the reply. Unfortunately, this doesn't help as I already have a port on the urls (as stated in my original question).

bundtkate

The port isn't the trouble, @manski, it's the host name for your NAS. Instead of nas1:, you'd need to use the IP address for that NAS device. Of course, if you were just using those terms here as more understandable placeholders, definitely let me know. IP addresses should work.

manski

@bundtkate I've changed the names from <hostname> to <hostname>.local (since the devices support mDNS/Bonjour) and now it works.

Am I correct that this is a Windows-only issue? Because on my Mac I can fill the passwords just fine.

Also are there any plans on fixing this problem in the near future?

AGAlumB

I doubt it would be in the near future, as we've got some big projects in the works currently. But we do plan to add support for this so that it works even without an actual valid TLD.