Since 2 days:
Uploading file ...
Size: 1090
After upload, please wait, eQSL will return some information!
Information: Received 629 bytes
Error: No match on eQSL_User/eQSL_Pswd for date 20210101 14:59
Web Login still works with the same combination.
cqrlog beta version
HI !
Have you tried to change your password?
Make an "easy" password with only up and low case letters and number(s). Try with that both web and cqrlog login.
If it works you can try to change you previous password back and see does it work.
--
Saku
OH1KH
Check what you have set for last year/day for your log
in Eqsl preferences...
<p>Jarmo</p>
Thanks.
Created new (sub-)account in eQSL (Website) with home2 Nick and changed in cqrlog Upload.. Works agn.+
Name: Rupert * QTH: Aachen * JO30as * DIG 19 * https://dl3no.de
Same problem but perhaps my preferences are not good ! I cant remember how it was before upgrading to new version (all is ok with it except for eqsl...) I missed something evident but what ?
here are my preferences :
http://www.eqsl.cc/qslcard/DownloadInBox.cfm
http://www.eqsl.cc/downloadedfiles/
https://www.eQSL.cc/qslcard/GeteQSL.cfm
Do I have to modify one of these lines ? Not sure ! Can you help !
Thanks a lot
You should post screenprints, because your links show the values of the person using them, i.e. mine :-)
Name: Rupert * QTH: Aachen * JO30as * DIG 19 * https://dl3no.de
that s all
File:
Go to EQSL web site, open Myprofile and look
Callsign/QTH End. Just change year, let's say 2030
so you have lots of years ahesd to upload your logs..
<p>Jarmo</p>
Hi !
There is normally no need to touch eQSL lines in preferences. They should be ok by default.
When eQSL changed addresses, and there was no confirm that new addresses stayed valid then user definitions were added for possible changes.
Normally DO NOT TOUCH DEFAULTS !
Just check what Jarmo OH1MMR says:
Log into eQSL web site and check that your account's ending date is in future.
All eQSL accounts created in past did took expire date at 2020-12-31.
You can easily edit that in you eQSl web site to expire at 2030-12-31 and after that all works again for next 10 years!
--
Saku
OH1KH
Date was OK but I change it to 2035 ! Same problem I can download the qsl info received but uploading doesn t work.
here the msg received :
"Please wait, exporting QSO for eQSL ...
Filename: /home/eric/.config/cqrlog/eQSL/2021-01-18_18-00-39.adi
eQSL server can process about 1000 QSO per minute. If you have
a lot of QSO to upload, it will take long time. So please be patient.
Uploading file ...
Size: 5492
After upload, please wait, eQSL will return some information!
Information: Received 2285 bytes
Error: No match on eQSL_User/eQSL_Pswd for date 20190526 06:25 "
What is the problem ?
Thank for help and CQRLog (the best logging program on linux )
"Error: No match on eQSL_User/eQSL_Pswd for date 20190526 06:25 "
That is the problem.. You have something wrong with log start or log end
dates...
Check again...
<p>Jarmo</p>
Hi!
This happened two years ago https://cqrlog.com/node/1963
Seems to be similar case.
--
Saku
OH1KH
I changed password three times and at last it works. Thanks for your help to everybody but a question remains : why did the download from eqsl work and the upload to eqsl returned the error message.
Seems illogical to me but... it s allright now !
No problem at all to upgrade to the new version of cqrlog with Mint. All automatic ! FB. Bravo aux développeurs du logiciel; Merci messieurs.
Had the same error yesterday, changed pw on eqsl.net, didn't help. Changed it back, didn't help. Changed the pw to one without any special character like ?=!() => worked!
--
Wolfgang
DJ4QV
HI !
Are we talking about cqrlog 2.4.0(001) or 2.5.0(001) ?
Later should handle better special characters.
--
Saku
OH1KH
same problem, same solution on cqrlog 2.5
Good morning Saku,
I am running 2.5.
73
Wolfgang
--
Wolfgang
DJ4QV
Hi!
I made password from "character like ?=!() => worked!" using source taken from cqrlog 2.5.0 that it uses to encode password at eQSl download.
Result is:
character%20like%20%3F%3D%21%28%29%20%3D%3E%20worked%21
By ascii table:
%20 = space
%3F= ?
%3D= =
%21= !
%28= (
%29= )
%3E= >
So the conversion is correct.
If you start cqrlog from console:
cqrlog --debug=1 > /tmp/debug.txt
Visit eQSL (up or download) and close cqrlog you can dig with text editor your encoded password from /tmp/debug.txt
You should find a line like:
https://www.eqsl.cc/qslcard/DownloadInBox.cfm?UserName=oh1kh&Password=XX...
Using that and ascii table http://www.asciitable.com you can easily check is your passord complete and proprely encoded by cqrlog.
If it is not tell the character(s) where encoding fails.
NOTE: if you are using special UTF8 charcters like û that does not work because encoding routine expects one byte characters between space and ~ (hex codes 0x20 - 0x7e) UTF8 charcters like û (0x02,0x15) have 2 bytes per one character .
--
Saku
OH1KH
Dear Saku,
thanks for ur reply. I started cqrlog by console and investigated /tmp/debug.txt but could neither find a line by grep starting with https://eqsl nor a line containing the expression Password. Am I doing something wrong?
--
Wolfgang
DJ4QV
Hi!
While debug was running did you make eQSL download?
You have to request that to get the line in debug.
To make it easier to find set TRXControl rig poll rate to 20000, do not connect DXCluster or use any remote modes while you make eQSL download.
That way you get less debug lines and it will be easier to find the eqsl line that starts just like you have in preferences/LoTW/eQSL support.
--
Saku
OH1KH
Good morning Saku,
yes, started cqrlog by console, did an upload to eqsl, and got the report that 52 new QSOs have been successfully uploaded. I will give it another go this evening!
CU agn
--
Wolfgang
DJ4QV
Dear Saku,
managed to do the testing as you suggested. Downloading from eqsl is working as expected, the password is completely encoded correctly, as the line starting with https://eqsl... in the debug.txt file states. But the problem remains for uploading.From the debug.txt
Can you confirm?
Best regards,
Wolfgang
--
Wolfgang
DJ4QV
Hi Wolfgang!
Fine! Now we have confirmed download side.
Please check files in your ~/.config/cqrlog/eQSL folder. You will find both uploaded and downloaded files there.
Start of files:
Download:
ADIF 3 Export from eQSL.cc
Received eQSLs for OH1KH QTH Nickname: home
for QSOs between 01-Jan-1982 and 31-Dec-2030 and uploaded on or after 06-Dec-2019 00:00Z
Generated on Saturday, January 23, 2021 at 10:24:00 AM UTC
<PROGRAMID:21>eQSL.cc DownloadInBox
<ADIF_Ver:5>3.1.0
<EOH>
Upload:
ADIF export from CQRLOG for Linux version 2.5.0 (101)
Copyright (C) 2021 by Petr, OK7AN and Martin, OK1RR
Internet: http://www.cqrlog.com
<ADIF_VER:5>3.1.0
<CREATED_TIMESTAMP:15>20210123 102214
<PROGRAMID:6>CQRLOG
<PROGRAMVERSION:11>2.5.0 (101)
<EQSL_USER:5>oh1kh
<EQSL_PSWD:10>XXXXXXXXXX
<EOH>
From upload file you should be able to check the encoding of your password.
--
Saku
OH1KH
Good morning Saku,
checked the upload file in .config/cqrlog/eqsl and PSWD seems to be correct. Number of elements fits to the number of elements in the password if you count the % and the two numbers for the special character as 3 elements.
Wolfgang
--
Wolfgang
DJ4QV
Ok!
Then all is ok.
If you still can not upload, but download works ok open eqsl.cc page, log in and see your profile.
Is the END date (in my picture at bottom right corner) in future? If END is 2020-12-31 then you can not upload to that profile any more.
File:
--
Saku
OH1KH
I'm sorry Saku,
the end date was set to 31.12.2035. Changed it to 2030 but didnt't work either. Hmmm...., I'm clueless but maybe a fault on eqsl's side. I'm changing pw now to be without special characters to upload my QSOs, but if I can be of any help and try things out for u just drop me a line!
73!
--
Wolfgang
DJ4QV
Hi Saku once again,
fyi: shortened my pw but didn't work with special character, put the special character to first position in pw, but didn't help either...
--
Wolfgang
DJ4QV
If encoded password is similar in qQSL receive (that you captured from debug text) and in upload file you checked from ~/.config/cqrlog/eQSL folder the problem can not bee in password or how cqrlog encodes it.
Cqrlog uses same encoding routine in both cases. Result must be same.
I was even thinking do you have special characters in QTH nickname, but the would affect to both up and download.
If you checked your eQSL nicname's end date to be 2035 (or 2030) is the start date also before or at same day as your error says?
"Error: No match on eQSL_User/eQSL_Pswd for date 20190526 06:25 "
So start date must be 2019-05-26 or earlier.
--
Saku
OH1KH
Dear Saku,
start date was 7th of November 2019, when all my logging with eqsl started. Changed it to 7th of may 2019 but still not working. As I am trying to upload new QSOs that never had been uploaded the error message is
Error: No match on eQSL_User/eQSL_Pswd for date 20210201 11:21
--
Wolfgang
DJ4QV
Hands up!
I can not figure anything else to test.
Can you do upload manually using the upload adif file from ~/.config/cqrlog/eQSl ?
--
Saku
OH1KH
Hi Saku,
yes, the manual upload from within eqsl.cc for the adif file in ~/.config/cqrlog/eQSl ist working. So you may take your hands down :-), it is not really a problem for me as I can use a pw without the special character. But maybe our whole procedure is of interest for someone with a similar problem. Thank you for your patience, efforts and your time and please keep up with the fabulous work of cqrlog (I nearly find every month a new feature that is astonishing me!)
73
--
Wolfgang
DJ4QV
Hi Wolfgang!
Can you provide me a list of same special characters you have in your password with count of each character, your password total length and count of up and low case letters?
I will then create similar like password for testing.
--
Saku
OH1KH
Dear Saku,
is there a way to give you the requested information in a private message?
--
Wolfgang
DJ4QV
Look HamQth or QRZ
--
Saku
OH1KH
U got a message via hamqth!
--
Wolfgang
DJ4QV
HI Wolfgang!
Received your mail! Thanks!
I think there is bug in eQSL upload anyway. I have read "EQSL.CC REAL-TIME LOGGING SOFTWARE INTERFACE" explanation and there is not clearly stated that EQSL_PSWD tag in uploaded adif file shoul be/may not be url encoded.
As it is not an url string I assume the password can be in plain format. Cqrlog uses there now url encoding. When I take it away from upload source code my test password that did not work works then. I will test a bit more with different special characters.
Thanks for bug reporting and being patient with finding it out!
--
Saku
OH1KH
Thank you Saku!
Compiled the source code with your suggested changes in the feQSLUpload source file. Now everything works as expected!!!!! Hopefully your pull request will be accepted soon! ufb!
Thx fer ur great help!
--
Wolfgang
DJ4QV
I just wanted to share this with anyone having this problem, Just a couple days ago I upgraded to the latest version of CQRLOG and it seemed to correspond to this problem. However, after reading through all the notes relating to this issue, I tried something very simple. I changed my complex eQSL password to a very basic 8 character one without any special characters. Now the upload works just fine. Obviously eQSL changed something; it is not a CQRLOG problem. My updated CQRLOG version is running flawlessly. Thank-you Petr OK7AN and Martin OK1RR and all the contributors of the greatest ham logger out there! 73's all
Hi,
it is indeed a problem with eqsl and the encoding. Saku just gave me his last proposed changes and I compiled my version of cqrlog with that, resulting in a flawless usability even with special characters (without the special character everythings works right now with the official version). Hopefully Petr is incorporationg Saku's pull request, so that the users don't have to compile their versions in case of the uploadproblem themselves.
73!
--
Wolfgang
DJ4QV
Hi!
Fix is now added to official source.
Either compile that, or upgrade to ready compiled version from my GItHub (cqr0.zip, update script selection #1. READ README!) https://github.com/OH1KH/cqrlog/tree/loc_testing/compiled
--
Saku
OH1KH