LoTW Incoming authentication fails although LoTW website login works (RUMlogNG 6.5, macOS Sequoia)

[Toru Mori]

Hello Tom,
I have been trying to solve a problem with LoTW Incoming, but I have now reached the point where I believe it may be a bug or an incompatibility.

Environment

• RUMlogNG 6.5 (724), Mac App Store version

• macOS Sequoia 15.4.1

• TQSL installed in /Applications

The problem
LoTW upload works perfectly, but LoTW Incoming always fails.

When I select QSL → LoTW Incoming → Load data from ARRL, the embedded LoTW login page is displayed.
Even after entering the correct LoTW username and password, it always reports:
Username/password incorrect
followed by:
Error while downloading data

What I have already verified

• I can log into the LoTW website successfully with Safari using exactly the same username and password.

• My LoTW password contains only letters and numbers (no special characters).

• Uploading new QSOs from RUMlogNG works correctly.

• I can manually download lotwreport.adi from the LoTW website.

• The downloaded ADIF contains 8 confirmed QSOs.

• The corresponding QSOs already exist in my RUMlogNG database with identical date, time, callsign, band and mode.

• I tested both RUMlogNG 5.19.5 and 6.5 (724); the behavior is identical.

• "Last LoTW QSL" remains at 12 Feb 1982 and is never updated.

Since LoTW upload works and manual download from the website also works, it appears that only the authentication used by LoTW Incoming is failing.

Is this a known issue, or is there anything else I should check?

Thank you very much for your help.
73,
Toru Mori
JG2TKH / JK1AKC

[DL2RUM]

Do not interact with the displayed LoTW login page! This page is displayed just to see the error message.
In the RUMlog LoTW settings select explicit your callsign in the For Callsign field.

[Toru Mori]

Thank you for your quick reply.
I changed the For callsign field from "All callsigns" to JK1AKC and restarted RUMlogNG.
Unfortunately, the behavior is unchanged.

The LoTW Incoming list remains empty.
Clicking Load data from ARRL still displays the LoTW login page.

As you suggested, I do not interact with the displayed login page.

Last LoTW QSL still remains 12 Feb 1982 and is never updated.

Since I can manually download lotwreport.adi from the LoTW website using the same account, I expected the incoming list to be populated or at least the "Last LoTW QSL" field to be updated.

Is there anything else I should check, or would you like me to enable debug logging?

[DL2RUM]

If you are absolutely certain that the user name (callsign) and password are correct, I'm out of ideas.
When you use a file based logbook (not iCloud synced) you could send me the file for an investigation.

[Toru Mori]

Thank you very much.
Yes, I am absolutely certain that the username and password are correct because I can log in to the LoTW website with the same credentials and manually download lotwreport.adi.
I am using a file-based logbook (not iCloud synced).
I will send you a copy of the logbook database for investigation.

[Toru Mori]

Hi Tom,
Thank you very much for your help.

The issue has now been resolved.

The cause was that different LoTW passwords had been stored in my RUMlogNG logbooks, although I believed that I had entered the same password in each one.

Tom checked the logbook files and found that the stored passwords were actually different.
I then changed my LoTW password on the LoTW website and copied and pasted the new password into both RUMlogNG logbooks.

After that:

• LoTW Incoming worked correctly for JK1AKC

• The login error disappeared

• 45 new LoTW confirmations were downloaded

• The “Last LoTW QSL” date was updated correctly

For JG2TKH, “No new QSLs!” is displayed because there are currently no new confirmations. Tom also explained that the “Last LoTW QSL” date will be updated when new QSLs are received.

So, for anyone experiencing a similar problem, I recommend changing the LoTW password and then using copy and paste to enter exactly the same password into each RUMlogNG logbook.

Many thanks again to Tom for his patience and detailed investigation.

73,
Toru
JK1AKC / JG2TKH