If you invoke TQSL's sign and upload ADIF or Cabrillo File function and are informed that "CURL returned Peer certificate cannot be authenticated with given CA certificates (SSL certificate problem: self signed certificate in certificate chain)", direct your anti-virus application to consider TQSL to be safe. If you are using Kaspersky AntiVirus, disable its Scan encrypted connections option. If you invoke TQSL's sign and upload ADIF or Cabrillo File function and are informed that TQSL cannot communicate with LoTW, check here to determine whether LoTW is unavailable (in which case you should wait until it returns to service), or whether your computer is unable to access LoTW via the internet if the latter, check to see if your computer can access any web site on the internet.
![hrd 6 uploads to lotw not showing on server hrd 6 uploads to lotw not showing on server](https://user-images.githubusercontent.com/13950650/92001538-18062580-ed3f-11ea-8c49-8380e0fab06b.png)
If the Callsign Certificate is invalid, request a replacement. If the Callsign Certificate was deleted, recover the deleted Callsign Certificate from a backup file (.tbk) or load it from a saved Callsign Certificate container file (.p12). If the Callsign Certificate has expired, renew it. If the Station Location you select to digitally sign your QSOs specifies a Callsign Certificate that is expired, has been deleted, or is invalid, TQSL will not proceed.
HRD 6 UPLOADS TO LOTW NOT SHOWING ON SERVER WINDOWS
![hrd 6 uploads to lotw not showing on server hrd 6 uploads to lotw not showing on server](https://demo.fdocuments.in/img/766x1032/reader019/reader/2020042923/5c8eb59f09d3f20b4a8d1487/r-2.jpg)
Determining Why a QSO Isn't Yet Confirmed