For the Atera site, I only have "app.atera.com" in the URL field.
Thinking something might be wrong with my Chrome installation, I uninstalled Chrome this morning, deleted all the Chrome folders under my profile folder, and did a fresh installation but it's still not working.
I started thinking maybe there's something in my Chrome profile or one of the other extensions I'm using that's interfering so I went to another machine that's never had Chrome installed, installed it but did not log in to my Google account, installed and activated the Passwordstate plugin. When I browsed to those sites, the same symptoms occurred.
As yet another test, I RDP'd to a terminal server with Chrome installed but is not logged in to my Google account, installed and activated the PWS plugin and the same symptoms occurred again.
The only common thing between all these computers is they're referencing the same Passwordstate server. Could there possibly be something with the server that's causing the issue? It didn't seem likely to me since the plugin was recognizing the sites and seeing there were credentials available but like I said, that's the only common link between all these computers.
What's so strange is the plugin had been working for all of these sites prior to the update to the latest build. I was so pleased with it that I had deleted all of my saved credentials from Chrome and had just been using Passwordstate and the plugin but now... :-(