LoTW uploads have stopped working - v2.36.1.0

Post Reply
G0TRT
Novice Class
Posts: 16
Joined: 21 Nov 2024, 05:56

LoTW uploads have stopped working - v2.36.1.0

Post by G0TRT »

Since the upgrade to v2.36.1.0 LoTW uploads have stopped working.

When Log4OM is closed the shutdown hangs (forever) whilst the LoTW upload tried to take place; when I try and push the uploads manually Log4OM just stits there trying to upload through TQSL.

All advice and fault finding suggestions welcome :)
User avatar
G4POP
Log4OM Alpha Team
Posts: 11569
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: LoTW uploads have stopped working - v2.36.1.0

Post by G4POP »

Has your TQSL Cert expired?
73 Terry G4POP
G0TRT
Novice Class
Posts: 16
Joined: 21 Nov 2024, 05:56

Re: LoTW uploads have stopped working - v2.36.1.0

Post by G0TRT »

Thanks Terry,

No, my certificate is in date.

When I try a manual upload of some 417 QSO's the Upload Confirmations window stalls at:

INFO: ADIF File created successfully.
INFO: TQSL Version 2.8.1
No private TQSL Password set
Executing TQSL with upload
MANAGED MODE SET

73, Ciemon
User avatar
G4POP
Log4OM Alpha Team
Posts: 11569
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: LoTW uploads have stopped working - v2.36.1.0

Post by G4POP »

Certainly something wrong with your set up because it works fine for me as confirmed below

INFO: ADIF File created successfully.
INFO: TQSL Version 2.8.1
No private TQSL Password set
Executing TQSL with upload
MANAGED MODE SET
Messages from LOTW:
TQSL Version 2.8.1 [v2.8.1]
Signing using Callsign G4POP, DXCC Entity ENGLAND
Attempting to upload one QSO
D:\Google Drive\G4POP Log4OM NG\config\LOTW\LOTW_UPLOAD_20250613191114.adi: Log uploaded successfully with result:
File queued for processing
After reading this message, you may close this program.
Final Status: Success(0)
success; log signed and uploaded and accepted without incident
INFO: SAVING LOG...
INFO: LOG SAVED
LOTW END

Check the firewall and anti virus are not intervening or perhaps something set wrong in TQSL

When did it stop working - Precicely?
73 Terry G4POP
Post Reply