Downloading QSOs from eQSL fails

6 posts / 0 new
Last post
K5TTF
K5TTF's picture
Downloading QSOs from eQSL fails

Uploading QSOs to eQSL.cc works fine, but downloading from them gets this:

Size: 2400
eQSL page was probably changed, cannot find the link to ADIF file
Server returned this:

I need someone to help me with what this error means & hopefully give me a clue as to what I can do about it.

Thanks,
Bill - K5TTF

oh1kh
EQSL

Hi Bill!
Just tested to download from eQsl and did not have any problems:

Size: 6088
File will be downloaded from:
http://www.eqsl.cc/qslcard/downloadedfiles/LF1PH654.adi
Size: 157479
File downloaded successfully
File:
/home/saku/.config/cqrlog/eQSL/2017-10-20_20-04-02.adi
Preparing import ....
Import complete ...

New QSOs confirmed by eQSL:
2017-01-01 OF8TA 80M JT65
2017-08-22 YO5BYV 30M FT8
2017-09-07 DL4MFF 6M FT8

........etc..

-----------------------------
Total: 58 new QSOs

Please check your Eqsl logon (preferences/loTW/eQSLsettings) and correct nicname for qth (that you have set in eqsl station information )

K5TTF
K5TTF's picture
I am sure this is something I am doing wrong...

I'm still having this problem. I can both download & upload to LOTW, no problem. I can upload to eqsl, no problem. I just cannot download from eqsl. Is it necessary that the QTH Profile, entered on eqsl.cc, be the same as the QTH Profile entered in the Preferences->QTH Profiles tab in CQRLOG? I would assume not, since there is a box to enter QTH Profile in both the "Upload to eqsl" & the "Download from eqsl" dialog boxes. However, I note that the program will not let one download with the QTH Profile box empty, while it will let one upload with an empty QTH Profile box.
Nevertheless, in my case the QTH Profiles throughout the various locations are identical. And I still cannot download from eqsl.

oh1kh
EQSL

You assume right. I do not have profiles in preferences, but eqsl dialog should have the same nicname than you have set at eqsl web page.
Preferences callsign and password should also match to qth nicname.

Download starts with url := 'http://www.eqsl.cc/qslcard/DownloadInBox.cfm'+ '?UserName='+user+ '&Password='+EncodeURL(pass)+ '&QTHNickname='+EncodeURL(edtQTH.Text)+ '&RcvdSince='+StringReplace(edtDateFrom.Text,'-','',[rfReplaceAll, rfIgnoreCase]);

So it could be tested with browser putting this url (click the link, then change call.passwd.nicname as yours @ browser):
http://www.eqsl.cc/qslcard/DownloadInBox.cfm?UserName=mycall&Password=my...

And it really gives a page with 2 links then:

Your ADIF log file has been built
There were 848 records
The last one was uploaded on 24-Oct-2017 at 04:31Z
Click one of the following to download it to your computer:
.ADI file
.TXT file

And if you look link "ADI" it really points to similar path you can see after "download data from eqsl- - window/File will be downloaded from:" line.

So test the link with your call, password, nicname and download from date. If you get response page from eqsl, then test that ADI link can you download file from it.
If it works, then downloading via cqrlog should work too. If you just have right call/passwd/nicname/date set @ cqrlog

--
Saku
OH1KH

File: 

K5TTF
K5TTF's picture
Well, here I am with egg on my face again.

This condition was caused by some problem in my eqsl.cc Inbox. I had about 40 QSLs in my Inbox when the contacts would initially not download. I did not manually download them because I thought I would find my mistake & then be able to get them automatically. Eventually there were so many contacts in my Inbox that I did manually add them to CQRLOG & then archive them all. The next day I tried to download from eqsl & it worked perfectly. And it has continued for several days now. So, I apologize for wasting everyones time.
73,
Bill - K5TTF

oh1kh
No problem

Hi Bill
Nice to hear that all is ok now.

These things are not waisted time. All entered messages may be valuable for someone other with similar problems.

If peope just would learn to use forum search with words that fits to their problem many things might be solved by just reading old messages.
--
Saku
OH1KH