LoTW Troubleshooting

Please review this document before submitting a support request.

1. QRZ Logbook can't Upload to LoTW or says my certificate is invalid.
2. How do I check my TrustedQSL certificate's validity?
3. Why would my certificate no longer be valid?
4. I sent records to LoTW via QRZ Logbook, but they have not appeared in my LoTW Account.
5. Where can I get more help with LoTW or TrustedQSL?
6. I submitted contacts that were confirmed in QRZ Logbook, but they are not showing as confirmed in LoTW.
7. Information appears to be missing from contacts imported from LoTW.
8. I still need help. What do I do?

QRZ Logbook can't Upload to LoTW or says my certificate is invalid.  What do I do?

Occasionally your certificate will become invalid. This can happen when it expires, or a replacement certificate is issued. 

If you have recently requested a renewal or replacement certificate, after you receive the new callsign.TQ6 file, you will need to install the TQ6 file into TQSL.  In TQSL, you will be able to create the requisite callsign.P12 file that will be uploaded to QRZ Logbook to continue using our LoTW integration.

Otherwise, check the status of the certificate we have on file.  A certificate can be valid, expired, or revoked. 

Obviously, the status must be valid. 

If the status is expired or revoked, you will need to return to TQSL and request a new callsign.TQ6 certificate.  When you receive it from LoTW, install it in your TQSL software.  Then, create a new callsign.P12 file in TQSL and then upload it to your QRZ Logbook.

*Note: you will not ever upload your callsign.TQ6 certificate to QRZ.

Confirm that you are using the correct passwords. When exporting to LoTW, we will ask for your certificate password. This is an optional password that was set when you exported your certificate from TrustedQSL. This password cannot be recovered or changed.  If you have forgotten it, you will need to re-export your certificate from TrustedQSL by following our setup guide.

When importing from LoTW, you need to enter the password you would use to log in at https://lotw.arrl.org. Your QRZ password is not used at any point in the process.

How do I check my TrustedQSL certificate's validity?

You can verify the status of your certificate by visiting our Logbook of The World Access Settings page. (this is the same page where you set up LoTW integration)

You should see something like this:

Why would my certificate no longer be valid?

Only one certificate can be valid for a callsign at a given time. If you request a replacement, all previously issued certificates become invalid and cannot be used.

Unrevoked - This means the certificate should be in good standing.
Revoked - This status usually occurs when a replacement certificate has been issued.
Superseded - This status usually occurs when a renewal certificate has been issued.
Expired - This status occurs when a certificate has expired.

If your status is anything other than "Unrevoked," you will need to upload the most recently issued certificate. If your certificate is expired and you have not requested a renewal, you will need to do so.

I sent records to LoTW via QRZ Logbook, but they have not appeared in my LoTW Account.

Records submitted to LoTW are placed in a processing queue, and QRZ does not receive feedback from LOTW about records after they are sent.  We drop them off like a hot potato, and LoTW never tells us what happened afterward.  It's up to you to gather the status from LoTW.

You can find information about the individual batches of QSOs we sent to LoTW on your behalf by visiting the Your Activity page in the LoTW Console.

The current status of the LoTW Processing Queue is published on the ARRL website here.

Where can I get more help with LoTW or TrustedQSL?

Additional information about Logbook of The World and TrustedQSL is available here.

I submitted contacts that were confirmed in QRZ Logbook, but they are not showing as confirmed in LoTW

QRZ provides reciprocal credit for all electronic confirmations received from LoTW through our LoTW Integration. Logbook of the World, however, does not recognize QRZ's or anyone else's confirmations.

Information appears to be missing from contacts imported from LoTW.

Logbook of The World does not store the entire contact record that you (or we on your behalf) send them. Only the following ADI fields are returned when an LoTW export is performed:

• APP_LoTW_OWNCALL
• STATION_CALLSIGN
• MY_DXCC
• MY_COUNTRY
• APP_LoTW_MY_DXCC_ENTITY_STATUS
• MY_GRIDSQUARE
• MY_CQ_ZONE
• MY_ITU_ZONE
• CALL
• BAND
• FREQ
• MODE
• APP_LoTW_MODEGROUP
• QSO_DATE
• APP_LoTW_RXQSO
• TIME_ON
• APP_LoTW_QSO_TIMESTAMP
• QSL_RCVD
• QSLRDATE
• APP_LoTW_RXQSL
• DXCC
• COUNTRY
• APP_LoTW_DXCC_ENTITY_STATUS
• PFX
• APP_LoTW_2xQSL
• GRIDSQUARE
• STATE
• CNTY
• CQZ
• ITUZ

If you need more information about a specific field, please check the ADIF Specifications published at https://adif.org/. Note fields starting with "APP_LoTW_" are application-specific fields that do not conform to the standard.

When we receive this information from LoTW, it is merged with anything that already exists in your logbook. To ensure that your QRZ Logbook records are as complete as possible, make sure that you import your data both through ADI files and through the LoTW integration (this will make sure that you get credit for LoTW confirmations)

I still need help. What do I do?

Unfortunately, due to the cryptographic nature of Logbook of The World, there is little we can do to assist with these issues. From our perspective, they either work, or they don't.  If you have already requested a replacement certificate from LoTW, uploaded it using our guide, and are still having problems, you may submit a support ticket, and we will try to assist you further. In your report, be sure to mention what troubleshooting steps you have already tried.