Loading ...
Sorry, an error occurred while loading the content.

New TQSL, operator error

Expand Messages
  • Mark Lunday
    I upgraded without any issues, but now that I try to sign and send an ADIF file using TQSL, I get the message as follows: CURL SSL error. If I just sign the
    Message 1 of 10 , Jun 16, 2013
    • 0 Attachment
      New TQSL, operator error

      I upgraded without any issues, but now that I try to sign and send an ADIF file using TQSL, I get the message as follows:

      CURL SSL error.

      If I just sign the ADIF and upload it via the ARRL LOTW interface, it works fine.

      So what am I doing wrong?

      Mark Lunday, WD4ELG

      Greensboro, NC  FM06be

      wd4elg@...

      http://wd4elg.blogspot.com

    • Dave AA6YQ
      ... From: ARRL-LOTW@yahoogroups.com [mailto:ARRL-LOTW@yahoogroups.com] On Behalf Of Mark Lunday Sent: Sunday, June 16, 2013 8:16 PM To:
      Message 2 of 10 , Jun 16, 2013
      • 0 Attachment

        >>>AA6YQ comments below

         

        From: ARRL-LOTW@yahoogroups.com [mailto:ARRL-LOTW@yahoogroups.com] On Behalf Of Mark Lunday
        Sent: Sunday, June 16, 2013 8:16 PM
        To: ARRL-LOTW@yahoogroups.com
        Subject: [ARRL-LOTW] New TQSL, operator error

        I upgraded without any issues, but now that I try to sign and send an ADIF file using TQSL, I get the message as follows:

        CURL SSL error.

        If I just sign the ADIF and upload it via the ARRL LOTW interface, it works fine.

        So what am I doing wrong?

        >>>Two possibilities:

        1.       You are running on Windows XP, and its root certificate has expired.

        2.       Your firewall or anti-malware application(s) are preventing TQSL 1.14 from accessing the internet (an ability that TQSL 1.13 did not require)

        >>>If you’re running on Windows XP, direct Internet Explorer (not Firefox or any other browser) to navigate to

        https://lotw.arrl.org|https://lotw.arrl.org

        >>>If instead of displaying the ARRL’s LotW web page, you see a complaint about a certificate being invalid, follow this procedure to update XP’s root certificate:

        <http://www.microsoft.com/en-us/download/details.aspx?id=38918>

        >>>To prevent this from happening again, enable Windows Updates.

        >>>If you’re not running on Windows XP, or if IE is able to display the ARRL’s LotW web page, then check your Firewall and anti-malware settings.

                       73,

                                     Dave, AA6YQ

         

         

      • Rick Murphy/K1MU
        ... If you can provide the complete cURL message, we can help you to diagnose. Dave has already suggested a few possibilities. The simple answer is that your
        Message 3 of 10 , Jun 16, 2013
        • 0 Attachment
          At 08:15 PM 6/16/2013, Mark Lunday wrote:
          >
          >
          >I upgraded without any issues, but now that I try to sign and send an
          >ADIF file using TQSL, I get the message as follows:
          >
          >CURL SSL error.
          >
          >If I just sign the ADIF and upload it via the ARRL LOTW interface, it
          >works fine.
          >
          >So what am I doing wrong?

          If you can provide the complete cURL message, we can help you to
          diagnose. Dave has already suggested a few possibilities.

          The simple answer is that your computer isn't able to make a secure
          connection to the LoTW upload site, most likely due to an out of date
          certificate store.
          73,
          -Rick
        • Mark Lunday
          The CURL message is CURL returned SSL connect error (schannel: failed to setup extended errors) Mark Lunday, WD4ELG Greensboro, NC FM06be wd4elg@arrl.net
          Message 4 of 10 , Jun 20, 2013
          • 0 Attachment
            Re: New TQSL, operator error

            The CURL message is

            CURL returned SSL connect error (schannel: failed to setup extended errors)

            Mark Lunday, WD4ELG

            Greensboro, NC  FM06be

            wd4elg@...

            http://wd4elg.blogspot.com

          • Dave AA6YQ
            That’s not the result of operator error, Mark. cURL is a component the TQSL uses to upload signed logs to LotW. It is required to employ a secure protocol
            Message 5 of 10 , Jun 20, 2013
            • 0 Attachment

              That’s not the result of operator error, Mark.

               

              cURL is a component the TQSL uses to upload signed logs to LotW. It is required to employ a secure protocol for this upload, but is being overly insistent on verifying the credentials of the ARRL’s web service, which can cause trouble in some circumstances.

               

              I’ve sent a file that configures cURL to be less insistent. Please let me know how it goes.

               

                    73,

               

                            Dave, AA6YQ

               

               

              From: ARRL-LOTW@yahoogroups.com [mailto:ARRL-LOTW@yahoogroups.com] On Behalf Of Mark Lunday
              Sent: Thursday, June 20, 2013 10:42 PM
              To: ARRL-LOTW@yahoogroups.com
              Subject: [ARRL-LOTW] Re: New TQSL, operator error

               

               

              The CURL message is

              CURL returned SSL connect error (schannel: failed to setup extended errors)

              Mark Lunday, WD4ELG

              Greensboro, NC  FM06be

              wd4elg@...

              http://wd4elg.blogspot.com


              No virus found in this message.
              Checked by AVG - www.avg.com
              Version: 10.0.1432 / Virus Database: 3199/5927 - Release Date: 06/20/13

            • madcapt
              Hi Dave, I get the same error message and have not been able to upload any logs since installing ver1.14.1. LoTW techs simply replied that they are
              Message 6 of 10 , Jun 21, 2013
              • 0 Attachment
                Hi Dave,
                I get the same error message and have not been able to upload any logs since installing ver1.14.1. LoTW techs simply replied that they are researching this problem. Any ideas? How about re-installing 1.13, as I had no problems with that version?

                Mark W1MAD

                --- In ARRL-LOTW@yahoogroups.com, "Dave AA6YQ" <aa6yq@...> wrote:
                >
                > That's not the result of operator error, Mark.
                >
                > cURL is a component the TQSL uses to upload signed logs to LotW. It is required to employ a secure protocol for this upload, but is
                > being overly insistent on verifying the credentials of the ARRL's web service, which can cause trouble in some circumstances.
                >
                > I've sent a file that configures cURL to be less insistent. Please let me know how it goes.
                >
                > 73,
                >
                > Dave, AA6YQ
                >
                >
                > From: ARRL-LOTW@yahoogroups.com [mailto:ARRL-LOTW@yahoogroups.com] On Behalf Of Mark Lunday
                > Sent: Thursday, June 20, 2013 10:42 PM
                > To: ARRL-LOTW@yahoogroups.com
                > Subject: [ARRL-LOTW] Re: New TQSL, operator error
                >
                >
                > The CURL message is
                > CURL returned SSL connect error (schannel: failed to setup extended errors)
                > Mark Lunday, WD4ELG
                > Greensboro, NC FM06be
                > wd4elg@...
                > http://wd4elg.blogspot.com
                >
                > _____
                >
                > No virus found in this message.
                > Checked by AVG - www.avg.com
                > Version: 10.0.1432 / Virus Database: 3199/5927 - Release Date: 06/20/13
                >
              • Dave AA6YQ
                I have sent you the file that changes the cURL configuration, Mark. Please let me know how it goes. 73, Dave, AA6YQ From: ARRL-LOTW@yahoogroups.com
                Message 7 of 10 , Jun 21, 2013
                • 0 Attachment

                  I have sent you the file that changes the cURL configuration, Mark. Please let me know how it goes.

                   

                       73,

                   

                             Dave, AA6YQ

                   

                  From: ARRL-LOTW@yahoogroups.com [mailto:ARRL-LOTW@yahoogroups.com] On Behalf Of madcapt
                  Sent: Friday, June 21, 2013 8:44 AM
                  To: ARRL-LOTW@yahoogroups.com
                  Subject: [ARRL-LOTW] Re: New TQSL, operator error

                   

                   

                  Hi Dave,
                  I get the same error message and have not been able to upload any logs since installing ver1.14.1. LoTW techs simply replied that they are researching this problem. Any ideas? How about re-installing 1.13, as I had no problems with that version?

                  Mark W1MAD

                  --- In ARRL-LOTW@yahoogroups.com, "Dave AA6YQ" <aa6yq@...> wrote:
                  >
                  > That's not the result of operator error, Mark.
                  >
                  > cURL is a component the TQSL uses to upload signed logs to LotW. It is required to employ a secure protocol for this upload, but is
                  > being overly insistent on verifying the credentials of the ARRL's web service, which can cause trouble in some circumstances.
                  >
                  > I've sent a file that configures cURL to be less insistent. Please let me know how it goes.
                  >
                  > 73,
                  >
                  > Dave, AA6YQ
                  >
                  >
                  > From: ARRL-LOTW@yahoogroups.com [mailto:ARRL-LOTW@yahoogroups.com] On Behalf Of Mark Lunday
                  > Sent: Thursday, June 20, 2013 10:42 PM
                  > To: ARRL-LOTW@yahoogroups.com
                  > Subject: [ARRL-LOTW] Re: New TQSL, operator error
                  >
                  >
                  > The CURL message is
                  > CURL returned SSL connect error (schannel: failed to setup extended errors)
                  > Mark Lunday, WD4ELG
                  > Greensboro, NC FM06be
                  > wd4elg@...
                  > http://wd4elg.blogspot.com
                  >
                  > _____
                  >
                  > No virus found in this message.
                  > Checked by AVG - www.avg.com
                  > Version: 10.0.1432 / Virus Database: 3199/5927 - Release Date: 06/20/13
                  >


                  No virus found in this message.
                  Checked by AVG - www.avg.com
                  Version: 10.0.1432 / Virus Database: 3199/5927 - Release Date: 06/20/13

                • Bill Kasper
                  Following one wierd display, sent trouble ticket WB2SXY KR4RO 2013-06-27 00:34:00 15M JT65 21.076000 UNITED STATES OF AMERICA North Carolina: 15M;
                  Message 8 of 10 , Jun 29, 2013
                  • 1 Attachment
                  • 288 KB
                  Following one wierd display, sent trouble ticket

                  WB2SXY KR4RO 2013-06-27 00:34:00 15M JT65 21.076000 UNITED STATES
                  OF AMERICA North Carolina: 15M; JT65; 15M JT65; 15M Digital; 6M AMTOR;
                  6M CLOVER; 6M CONTESTI; 6M DOMINO; 6M FSK31; 6M FSK441; 6M GTOR; 6M
                  HELL; 6M HFSK; 6M ISCAT; 6M JT4; 6M JT65; 6M JT6M; 6M JT9; 6M MFSK16; 6M
                  MFSK8; 6M MINIRTTY; 6M MT63; 6M OLIVIA; 6M OPERA; 6M PACKET; 6M PACTOR;
                  6M PAX; 6M PSK10; 6M PSK125; 6M PSK2K; 6M PSK31; 6M PSK63; 6M PSK63F; 6M
                  PSKAM; 6M PSKFEC31; 6M Q15; 6M RTTY; 6M RTTYM; 6M THOR; 6M THROB; 6M
                  VOI; 6M WINMOR; 6M WSPR; 2M AMTOR; 2M CLOVER; 2M CONTESTI; 2M DOMINO; 2M
                  FSK31; 2M FSK441; 2M GTOR; 2M HELL; 2M HFSK; 2M ISCAT; 2M JT4; 2M JT65;
                  2M JT6M; 2M JT9; 2M MFSK16; 2M MFSK8; 2M MINIRTTY; 2M MT63; 2M OLIVIA;
                  2M OPERA; 2M PACKET; 2M PACTOR; 2M PAX; 2M PSK10; 2M PSK125; 2M PSK2K;
                  2M PSK31; 2M PSK63; 2M PSK63F; 2M PSKAM; 2M PSKFEC31; 2M Q15; 2M RTTY;
                  2M RTTYM; 2M THOR; 2M THROB; 2M VOI; 2M WINMOR; 2M WSPR

                  Bill WB2SXY
                • KQ8M
                  WOW, one QSO and all those band modes. Yea, I think something is amiss. 73, Tim Herrick, KQ8M Charter Member North Coast Contesters kq8m@kq8m.com AR-Cluster V6
                  Message 9 of 10 , Jun 29, 2013
                  • 0 Attachment

                    WOW, one QSO and all those band modes. Yea, I think something is amiss.

                     

                    73,

                    Tim Herrick, KQ8M

                    Charter Member North Coast Contesters

                    kq8m@...

                     

                    AR-Cluster V6 kq8m.no-ip.org

                    User Ports: 23, 7373  with local skimmer, 7374 without local skimmer

                    Server Ports: V6 3607, V4 Active 3605, V4 Passive 3606

                     

                    From: ARRL-LOTW@yahoogroups.com [mailto:ARRL-LOTW@yahoogroups.com] On Behalf Of Bill Kasper
                    Sent: Saturday, June 29, 2013 10:20 AM
                    To: ARRL-LOTW@yahoogroups.com
                    Subject: [ARRL-LOTW] wierd LoTW WAS Display [1 Attachment]

                     

                     

                    [Attachment(s) from Bill Kasper included below]

                    Following one wierd display, sent trouble ticket

                    WB2SXY KR4RO 2013-06-27 00:34:00 15M JT65 21.076000 UNITED STATES
                    OF AMERICA North Carolina: 15M; JT65; 15M JT65; 15M Digital; 6M AMTOR;
                    6M CLOVER; 6M CONTESTI; 6M DOMINO; 6M FSK31; 6M FSK441; 6M GTOR; 6M
                    HELL; 6M HFSK; 6M ISCAT; 6M JT4; 6M JT65; 6M JT6M; 6M JT9; 6M MFSK16; 6M
                    MFSK8; 6M MINIRTTY; 6M MT63; 6M OLIVIA; 6M OPERA; 6M PACKET; 6M PACTOR;
                    6M PAX; 6M PSK10; 6M PSK125; 6M PSK2K; 6M PSK31; 6M PSK63; 6M PSK63F; 6M
                    PSKAM; 6M PSKFEC31; 6M Q15; 6M RTTY; 6M RTTYM; 6M THOR; 6M THROB; 6M
                    VOI; 6M WINMOR; 6M WSPR; 2M AMTOR; 2M CLOVER; 2M CONTESTI; 2M DOMINO; 2M
                    FSK31; 2M FSK441; 2M GTOR; 2M HELL; 2M HFSK; 2M ISCAT; 2M JT4; 2M JT65;
                    2M JT6M; 2M JT9; 2M MFSK16; 2M MFSK8; 2M MINIRTTY; 2M MT63; 2M OLIVIA;
                    2M OPERA; 2M PACKET; 2M PACTOR; 2M PAX; 2M PSK10; 2M PSK125; 2M PSK2K;
                    2M PSK31; 2M PSK63; 2M PSK63F; 2M PSKAM; 2M PSKFEC31; 2M Q15; 2M RTTY;
                    2M RTTYM; 2M THOR; 2M THROB; 2M VOI; 2M WINMOR; 2M WSPR

                    Bill WB2SXY

                  • Joe Subich, W4TV
                    Similar display occurs for any unselected digital confirmation with a US station. I suspect K1MK is working on some of the issues with WAS digital awards -
                    Message 10 of 10 , Jun 29, 2013
                    • 0 Attachment
                      Similar display occurs for any unselected digital confirmation with
                      a US station. I suspect K1MK is working on some of the issues with
                      WAS digital awards - the generic digital, plus the individual mode
                      endorsements. We've had a log discussion with MVP about it.

                      73,
                      ... Joe, W4TV


                      On 6/29/2013 10:20 AM, Bill Kasper wrote:
                      > Following one wierd display, sent trouble ticket
                      >
                      > WB2SXY KR4RO 2013-06-27 00:34:00 15M JT65 21.076000 UNITED STATES
                      > OF AMERICA North Carolina: 15M; JT65; 15M JT65; 15M Digital; 6M AMTOR;
                      > 6M CLOVER; 6M CONTESTI; 6M DOMINO; 6M FSK31; 6M FSK441; 6M GTOR; 6M
                      > HELL; 6M HFSK; 6M ISCAT; 6M JT4; 6M JT65; 6M JT6M; 6M JT9; 6M MFSK16; 6M
                      > MFSK8; 6M MINIRTTY; 6M MT63; 6M OLIVIA; 6M OPERA; 6M PACKET; 6M PACTOR;
                      > 6M PAX; 6M PSK10; 6M PSK125; 6M PSK2K; 6M PSK31; 6M PSK63; 6M PSK63F; 6M
                      > PSKAM; 6M PSKFEC31; 6M Q15; 6M RTTY; 6M RTTYM; 6M THOR; 6M THROB; 6M
                      > VOI; 6M WINMOR; 6M WSPR; 2M AMTOR; 2M CLOVER; 2M CONTESTI; 2M DOMINO; 2M
                      > FSK31; 2M FSK441; 2M GTOR; 2M HELL; 2M HFSK; 2M ISCAT; 2M JT4; 2M JT65;
                      > 2M JT6M; 2M JT9; 2M MFSK16; 2M MFSK8; 2M MINIRTTY; 2M MT63; 2M OLIVIA;
                      > 2M OPERA; 2M PACKET; 2M PACTOR; 2M PAX; 2M PSK10; 2M PSK125; 2M PSK2K;
                      > 2M PSK31; 2M PSK63; 2M PSK63F; 2M PSKAM; 2M PSKFEC31; 2M Q15; 2M RTTY;
                      > 2M RTTYM; 2M THOR; 2M THROB; 2M VOI; 2M WINMOR; 2M WSPR
                      >
                      > Bill WB2SXY
                      >
                      >
                      >
                      > ------------------------------------
                      >
                      > Yahoo! Groups Links
                      >
                      >
                      >
                      >
                      >
                      > -----
                      > No virus found in this message.
                      > Checked by AVG - www.avg.com
                      > Version: 2013.0.3345 / Virus Database: 3199/6433 - Release Date: 06/23/13
                      >
                    Your message has been successfully submitted and would be delivered to recipients shortly.