Dennis,
Please see attached error message with a new QSO. This time it said http://localhost:10004/session/6b30cafbca...
I am monitoring k7ar.net:7300 via telnet. I will change to another cluster just to see if that makes a difference.
The Log -- Main gets filled out with all information, including the callsign of the station worked. All information also shows up in the browser window EXCEPT the callsign. Then there is a delay (probably the 60 seconds noted in the error message) before the error message shows up. After I click on ignore, the callsign shows up in the browser window. During the delay, I get the error message: "This action cannot be completed..." if I click anywhere in the program.
Note: this does not happen with every QSO. Sometimes there is about a 2-5 second delay which is also not something I have seen before. It appears that anytime there is a callsign that has not been previously entered into the log, I get the delay and error message.
I am using QRZ Subscription which is up to date.
I closed the Telnet window with no change.
I closed the Spotlog with no change.
I am using Google Chrome Version 108.0.5359.125 (Official Build) (64-bit). Chromedriver108.exe is installed.
As mentioned before, this started BEFORE I installed the latest LOGic update and have installed it twice, which also resulted in rebooting the computer each time.
Most of the time I do not see these errors using WSJT-X, only when manually entering a new QSO. However, I have noticed that a new QRZ page is being opened (and stays open) every time I log a QSO which says "Chrome is being controlled by automated test software". This window opens on top of my LOGic screen sometimes.
Update: After all that testing and typing, I may have solved the problem, but it was something I never had to do before: I had to log in to the QRZ.com window that I mentioned above which says "Chrome is being controlled by automated test software". After doing that I no longer get the error messages, however there is still a bit of a delay before the browser window is updated...which may be attributable to the slow d/l speeds I am currently getting with my super old POS (that is Point of Sale) computer...
73, Allen N5XZ