Automatic update to EQSL has stopped working

[W4EBB]

Background:
Log4OM version is 1.32
Doing FT-8 with WSJT-X, JT-Alert and HRD for cat control
The automatic update had been working for one year
I have been down for 2 months due to home remodeling - including packing away all equipment.

Now I have reinstalled everything, did all software updates, and am back on FT8 with everything working except EQSL.
The automatic update for QRZ is working.
The update for LOTW via QSL management works.

When the automatic update for EQSL failed I tried to update via QSL management but that fails with "no match on app_qth_nickname". I had never tried this before so I do not know if this ever worked. I do know that the nickname is the same on EQSL and Log4OM.

I have tried looking at the "Show Log" but I do not see any obvious entries - at least to me.

So, some help will be appreciated. Is it EQSL or Log4OM or something else?

[K7PT]

What version of Log4OM are you using?

[DF5WW]

Hi Chuck,

he´s using 1.32 as he wrote at the top of his post

Hello nameless,

please login to your eQSL account and check what nickname you are using there for your account.
B.t.w. it could be "Home" or something else. In the Log4OM eQSL settings you must use exact the
same for your QTH Nickname or upload fails with "no match" as described.

[W4EBB]

As I said in my post, the names in EQSL and Log4OM are the same.

[G4POP]

Have you made certain that your user name and password DON'T have any special characters in them like.......

+×÷=@#$%^&*-'!?()¥₩£€_/

Special characters are NOT acceptable

[W4EBB]

Hello Terry:
I would like to restate my problem(s):

The #1 problem is that after one year working every time the automatic update to EQSL fails every time.

The #2 problem is that while trying to fix #1, in the meantime, I tried to use QSL Management to update EQSL. That fails every time with "no match on app_qth_nickname". The nicknames are the same on Log4OM and EQSL.

As said in my original post I do not know if I have done something. The process I use is WSJT-X and JT-Alert puts the QSO in Log4OM but it doesn't automatically get to EQSL as before.

Thanks
Charlie
W4EBB

[G4POP]

Send me a support request with ADIF file as detailed here http://www.log4om.com/log4om-support/

[W4EBB]

Okay - I found the problem - it was at EQSL and caused by me.

I have two accounts and EQSL was getting mixed up on which one to access - hence the mismatch on Nickname.

The cause was overlapping dates - however it was like that since day 1 - so EQSL must have made changes to cause it to now fail. Anyway, I corrected the dates and now all is well.

The TRACE was very helpful to narrow down the problem.

One additional item - I messed up when joining the forum - I should have made my username W4EBB - can you fix that for me or is there a way that I can do it?

Thanks to all,
Charlie

[G4POP]

Done

[W4EBB]

Terry:
Thanks!
Charlie