Upgrade StorageStubborn 'Is Zotero Running?' error and timeout
Hello,
I am opening this issue because I am failing to resolve a systematic timeout error on 'http://127.0.0.1:23119/connector', and I cannot solve the error 'Is Zotero Running?'. I tried all suggestions from the documentation, and now I don't know what else to try.
I would appreciate your guidance on how to debug this issue.
Thank you,
Debug ID: D1943442619
What I tested:
- Tested multiple browsers (Edge, Chrome, Firefox)
- Tried with and without the browser extension, tried reinstalling the browser plugin
- Tried rebooting and updating my PC
- Tried removing all Zotero plugins
- Tried with all browser extensions removed, all programs closed except Zotero
- Tried with and without the config 'Allow other applications on this computer to communicate with Zotero.'
- Tried disabling firewall (Windows Firewall) and antivirus software (Windows Defender and Windows security options), tried allowing Zotero on the firewall on all networks.
- Tried resetting my Windows network settings, resetting DNS config, resetting Host file.
- Tried removing and reinstalling Zotero, tried the latest Zotero 7 and Zotero 8 beta.
- Tried Windows 8 compatibility mode on Zotero process
- Tried adding multiple types of content (Wikipedia, YouTube, arXiv, website) in multiple places (my library, subcollection, shared library).
- Tried resetting translators (both in connector and Zotero)
- Tried resetting Zotero data and profile (removed Zotero files in AppData and /user/)
- Made sure I was not using a proxy server, and that 127.0.0.1 was excluded from proxying
- Tried Zotero in debug mode, logging says: 'HTTP server listening on 127.0.0.1:23119' but I still get the error 'Zotero unavailable'
Additional info:
- I am using Zotero 7.0.30 (64-bit), Connector 5.0.193, Windows 11 Pro Version 25H2 Build 26200.7309
- I checked, a socket on TCP port 23119 is indeed opened by Zotero
- The Zotero log does not seem to report any significant error (sometimes 'The connection was refused when attempting to contact wss://stream.zotero.org/', 'WebSocket connection closed: 1006', and 'DOMException: Could not get children of file (C:\Users\myuser\AppData\Roaming\Zotero\Zotero\Crash Reports\events) because it does not exist' in the error console though).
- The browser extension config panel will randomly switch between: "Zotero is currently unavailable", and "Zotero is currently available" if I push the 'update status'
- In all my tests, I never got an answer for 'http://127.0.0.1:23119/connector/ping', it always times out.
- I am getting this issue on my personal laptop only. (With my professional laptop, I do not have this issue).
---
Martin
Edit: fixed typos
I am opening this issue because I am failing to resolve a systematic timeout error on 'http://127.0.0.1:23119/connector', and I cannot solve the error 'Is Zotero Running?'. I tried all suggestions from the documentation, and now I don't know what else to try.
I would appreciate your guidance on how to debug this issue.
Thank you,
Debug ID: D1943442619
What I tested:
- Tested multiple browsers (Edge, Chrome, Firefox)
- Tried with and without the browser extension, tried reinstalling the browser plugin
- Tried rebooting and updating my PC
- Tried removing all Zotero plugins
- Tried with all browser extensions removed, all programs closed except Zotero
- Tried with and without the config 'Allow other applications on this computer to communicate with Zotero.'
- Tried disabling firewall (Windows Firewall) and antivirus software (Windows Defender and Windows security options), tried allowing Zotero on the firewall on all networks.
- Tried resetting my Windows network settings, resetting DNS config, resetting Host file.
- Tried removing and reinstalling Zotero, tried the latest Zotero 7 and Zotero 8 beta.
- Tried Windows 8 compatibility mode on Zotero process
- Tried adding multiple types of content (Wikipedia, YouTube, arXiv, website) in multiple places (my library, subcollection, shared library).
- Tried resetting translators (both in connector and Zotero)
- Tried resetting Zotero data and profile (removed Zotero files in AppData and /user/)
- Made sure I was not using a proxy server, and that 127.0.0.1 was excluded from proxying
- Tried Zotero in debug mode, logging says: 'HTTP server listening on 127.0.0.1:23119' but I still get the error 'Zotero unavailable'
Additional info:
- I am using Zotero 7.0.30 (64-bit), Connector 5.0.193, Windows 11 Pro Version 25H2 Build 26200.7309
- I checked, a socket on TCP port 23119 is indeed opened by Zotero
- The Zotero log does not seem to report any significant error (sometimes 'The connection was refused when attempting to contact wss://stream.zotero.org/', 'WebSocket connection closed: 1006', and 'DOMException: Could not get children of file (C:\Users\myuser\AppData\Roaming\Zotero\Zotero\Crash Reports\events) because it does not exist' in the error console though).
- The browser extension config panel will randomly switch between: "Zotero is currently unavailable", and "Zotero is currently available" if I push the 'update status'
- In all my tests, I never got an answer for 'http://127.0.0.1:23119/connector/ping', it always times out.
- I am getting this issue on my personal laptop only. (With my professional laptop, I do not have this issue).
---
Martin
Edit: fixed typos
I discovered that I had a partially installed version of Portmaster (firewall software). Oddly, the Portmaster process was not visible in Task Manager, Process Explorer, nor in the taskbar, and I thought I had uninstalled this firewall long ago. I did not realize that it was active until I opened Windows Resource Monitor (resmon.exe), looked into the 'Network > TCP Connections,' and saw the activity of portmaster.exe instead of the expected activity of Zotero on the opened 23119 network port.
I uninstalled portmaster and now the connector works without any issues!
I was able to un-install it again simply from Windows setting (the app was still registered in installed apps, thus not completely hidden). And this time it seems it worked. Though I will for sure keep monitoring this!