Now that I switched shack computers out, I loaded the latest version of Trusted QSL to my shack laptop. I requested a new callsign certificate from that laptop and it arrived today. I tried uploading the certificate to the Trusted QSL program and I keep getting this error:
The certificate is there - the League just e-mailed it to me! I even went to the LotW Website and manually downloaded my certificates - still nothing, same message box pops up. I even tried deleting Trusted QSL and re-installed it thinking there might have been some kind of error when it loaded - no dice.
Any LotW gurus out there have any idea as to what might be going on?
72 de Larry W2LJ
QRP - When you care to send the very least!
Does Trusted QSL run as administrator? Try giving it those rights. Then open the email client and click on the attachment. It should "run" and activate TQSL which will then do the rest.
ReplyDeleteThe crew at ARRL will help you out if this doesn't work. Give them a call.
Rob, W8MRL
There's the certificate, and then there's the certificate....
ReplyDeleteSounds like you lost the private key certificate. Your (old) computer generates the private key, then uploads the public key counterpart (.t5 file). The ARRL creates a validation key with their own private key and uploads the public key counterpart (.t6 file). When you combine these, you end up with the public private key certificate (.p12 file).
Having the .t6 file isn't enough, you need the .p12 file. Otherwise, you don't have the private key your computer generated.
It's complicated, but it's part of the way LoTW is secure. You're not the only one who has done this.
There is a private key to your certificates (how secure would LotW be if anybody could download your certificate and use it?).
ReplyDeleteHave you migrated that private key from the old computer, or generated a new one by generating a request for a new certificate?
I run TQSL as a normal user, not admin. Once installed you should be able to do so too.
The previous version of LotW ran successfully on this laptop. Instead of going with the immediately previous version that worked, I decided to install the moist current version, as per the ARRL's instructions. Then I requested a new call sign certificate using the new installation. The certificate came, the software won't recognize it.
ReplyDelete