LoTW uploads have stopped working - v2.36.1.0

[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

[G4POP]

Has your TQSL Cert expired?

[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

[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?

[G0TRT]

The last QSO marked as sent to LoTW is on the 15th May, after that, none are marked as sent. But LoTW has them, and I just proved that upload is working by checking LoTW.

But Log4OM is just sitting and waiting for something, which I'm not sure how to debug unless there's a verbose log somewhere that I can look at.

I'm going to mark all QSOs as sent and see if that makes a difference.

[G4POP]

You can access the log file from the help menu and change the info depth to trace or debug

Have you checked the box 'TQSL Interactive mode' in Settings/Program config/external serices/LOTW menu?

[G0TRT]

Thanks Terry,

I've upped the logging level. LoTW has worked flawlessly in the past, and I've not had 'TQSL Interactive mode' ticked. So I'll do some more testing with all of that and come back with my findings.

[G0TRT]

Just to cap this off, all is working normally.

It appeared that Log4OM wasn't uploading to LoTW but QSOs had been already uploaded, and this "dupe" state maybe why Log4OM was hanging, no doubt output text from LoTW wasn't what was expected by LoG4OM.

But manually setting "LoTW sent" manually within Log4OM for those QSOs marked as unsent, cleared the issue and all is working normally now.

[KI5IO]

Ciemon,

Are those Q's that appeared to have an upload problem come into Log4OM V2 via a 3rd party APP such as WSJTx, JTAlert, Gridtracker, etc.?

If so you might have a tic box checked in those APPs to upload to LOTW as well. Also, if you are using such APPs check the inbound UDP connections and the parameters for each of those connections. They can also control LOTW uploads, etc..

[G0TRT]

Hey Nolan,

That's a useful point, although not what's been happening here. The only other package I use is N1MM+ and the ADIF outtput from that is really simplistic, so not an issued in this case.