I was just about to report the same issue.. added Zotero as exception in the Firewall, but no clue if this did the trick. On another machine, I did not do it and it works fine.
Hello, using the latest softs, Zotero 6.0.10 and Opera 89.0.4447.71 with Zotero Connector Version 5.0.97, Windows 10 64-Bit.
After starting Zotero and Opera, they were not connecting "Zotero is currently unavailable", however http://127.0.0.1:23119/connector/ping reported "Zotero Connector Server is Available". I refreshed and waited several minutes. Not working. "Private network" FW is On. I added Z as exception. From that moment it connected.
I guess so, ... I'm aware, Opera gets low support. The only thing is, it works on another machine (some software configuration as mentioned above) without the FW-exception. How to understand this interface, does it need Zotero started first, then the browser? Does it include a waiting time, delay for the connection to setup etc.?
FYI. I faced the same issue after update to latest Zotero version using latest Opera. Ping still available. I deinstalled, reinstalled and reauthorized the extension. It works (again).
Upgrade Storage
After starting Zotero and Opera, they were not connecting "Zotero is currently unavailable", however http://127.0.0.1:23119/connector/ping reported "Zotero Connector Server is Available".
I refreshed and waited several minutes. Not working. "Private network" FW is On. I added Z as exception. From that moment it connected.
How to understand this interface, does it need Zotero started first, then the browser? Does it include a waiting time, delay for the connection to setup etc.?
But no, the order doesn't matter, and there's no delay.