www.dl2rum.de

I’m having a problem with LotW incoming using RUMLogNG Version 2.14 (130) running on a MacBook Pro under OSX El Capitan Version 10.11.6.

I have the same problem on my other MacBook under macOS Sierra. (I have tried both in case it was due to a change from El Capitan to Sierra.)

When I go to the QSL menu and select LotW in, I get the ARRL login page for LotW. (I get this even though my user name and password are entered on the LotW preferences screen.)

I type in my LotW user name and password and then select the Log On button below these fields. Nothing happens. If I then select the Log On at the top right of the LotW page, I am taken to my (logged in) home page.

I then go to the bottom of the window and select “Read Data from ARRL” and I’m taken back to the LotW login screen and nothing further appears to happen. I am apparently still logged into LotW, because if I again select the Log On at the top right of the LotW page, I return to my (logged in) home page.

I can’t find any way to get past this point to be able to download my new QSLs.

My last successful QSL download was 5 September 2016. (Even then, however, I had been forced to enter my LotW user name and password at the LotW login page and then select “Read Data from ARRL” at the bottom of the window. At that point RUMLogNG would read in the latest QSLs and process them correctly.)

As far as I can recall, I have made no other changes to this machine other than updating RUMLogNG and Apple and other software through the App store.

I would appreciate any suggestions as to how I could proceed with debugging.

Thanks very much.

Brett VE7GM

You miss understood somethings.
You have to enter your user name and password into the preferences!
When data are read from the ARRL and all is okay, the QSOs show up in a table in this window.
When something is going wrong for any reason, the ARRL server answers with a web page. This is for your information only! You don't have to interact with this page! The reason for the error should be stated on this page somewhere.

A common problem is the chosen password. You should avoid special characters.

Thanks very much for the fast reply.

I had my user name and password in the preferences, but I also had a special character in my password. I've now changed my password to have no special characters and all is now working.

Many thanks for the help and for the fine program.

Brett VE7GM