You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Over the last 24 hours I've seen the following error from CWSL_Digi for my K1RA skimmer spit out numerous times:
ERROR :: Socket connect failed with error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024-06-17 17:10:40.608 ### ERROR :: Error connecting to WSPRNet
Is anyone else who's spotting WSPR from CWSL_Digi not seeing their spots posted at
I'm also running K1RA-PI (DigiSkimmer / RPi + RaspSDR) and K1RA-4 (QRA-Skimmer / RX-888) also from the same QTH/network skimming all modes and those are posting WSPR to WSPRnet just fine.
What is the timeout on the CWSL_Digi socket connection to the WSPRnet server? I see manually polling the WSPRnet database that response times today are up to 60 seconds and its acting very sluggish.
Thanks & 73
andyz - K1RA
The text was updated successfully, but these errors were encountered:
Over the last 24 hours I've seen the following error from CWSL_Digi for my K1RA skimmer spit out numerous times:
ERROR :: Socket connect failed with error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2024-06-17 17:10:40.608 ### ERROR :: Error connecting to WSPRNet
Is anyone else who's spotting WSPR from CWSL_Digi not seeing their spots posted at
https://www.wsprnet.org/drupal/wsprnet/spotquery
I'm also running K1RA-PI (DigiSkimmer / RPi + RaspSDR) and K1RA-4 (QRA-Skimmer / RX-888) also from the same QTH/network skimming all modes and those are posting WSPR to WSPRnet just fine.
What is the timeout on the CWSL_Digi socket connection to the WSPRnet server? I see manually polling the WSPRnet database that response times today are up to 60 seconds and its acting very sluggish.
Thanks & 73
andyz - K1RA
The text was updated successfully, but these errors were encountered: