Illusory upload and download LOTW

[iu0dhv]

Feature Description

A few days ago I observed the following:
QLog was apparently performing both the upload and download from LOTW. After some time however I started to be a bit puzzled as of why no confirmations had been downloaded for quite a few days and that seemed strange. I went on LOTW webpage and realized that there had also been no uploads as well. After controlling in TQLS I notice that the installation of the new certificates did not go through. After installing them properly upload and download started working again nicely.
It would be nice if QLog could give a warning or an error message if, in case of expired or not properly installed certificates, there is no actual download from or upload on LOTW?

[foldynl]

As you already mentioned, QLog uses LoTW's official TQSL application for uploading to LoTW in order to guarantee maximum protocol compatibility when uploading QSOs. QLog checks for TQSL error status when uploading. Unfortunately, if this application does not report an error in the state you describe, I am not able to pass this on to the user.

However, it is not a function of QLog to check for an expired certificate of another service if this service does not report this as an upload error.

Unfortunately, I am not sure that I can test this, because I have no expired LoTW certificate now.

[foldynl]

Tested with TrustedQSL v 2.7.2 with my old certificate and QLog reported an error of TQSL. Unfortunately, I don't know what circumstances arose in your case that TQSL didn't report any errors.

[iu0dhv]

Dear I don't know either, I Just wanted to report what I observed. In your test where do you see the error? Does a pop up message appear in Qlog or did you see it in Tqsl? I did not open Tqsl until I started to realise that something could have been wrong there. I could reload the expire certificate to try again and see..but I suspect that I was somewhere in between a full upload of the certificates. So maybe this is why no error was displayed (as should be the case with expired certificates) Il ven 25 lug 2025, 12:27 Ladislav ***@***.***> ha scritto:

…

*foldynl* left a comment (foldynl/QLog#713) <#713 (comment)> Tested with TrustedQSL v 2.7.2 with my old certificate and QLog reported an error of TQSL. Unfortunately, I don't know what circumstances arose in your case that TQSL didn't report any errors. — Reply to this email directly, view it on GitHub <#713 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BPHTUE67Y3H364OA7Z4PH5T3KIA7PAVCNFSM6AAAAACCIAS5BWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMJXGIZDMOJRGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>