I agree with the above posts, this is absolute rubbish Why on Earth would they make changes like this at a time like this! The next phase will be to see what happens with the HRD 5.xx free version, will it be supported or will this be the moment when they say get 6.x or say goodbye to using LoTW with the HRD software.

Logged

“A lie can travel half way around the world while the truth is putting on its shoes.” (Mark Twain)

I agree with the above posts, this is absolute rubbish Why on Earth would they make changes like this at a time like this! The next phase will be to see what happens with the HRD 5.xx free version, will it be supported or will this be the moment when they say get 6.x or say goodbye to using LoTW with the HRD software.

Some users are able to upload their loads to LoTW: in the last 5 hours, I've personally tracked the # of QSO processed and it has climbed several tens of thousands. Also see W1VT's post.

So it may or may not be something that originated with the LoTW folks. It could be other problems ... perhaps coming from the ARRL's service provider, DNS failures, faulty equipment, etc. So it is a bit premature to make any claims at this point (including that it is specifically HRD-related). Like I said in one of my earlier posts, we'll probably have to wait till early next week to find out exactly what happened. At least for me, a few days of no uploads isn't going to kill me.

Yesterday afternoon, LotW Management changed the LotW Server's URL address. They did this in a way that they expected would be transparent, and so issued no warning to developers of applications that interoperate with the LotW. However, the change was not transparent, causing many such applications to lose the ability to interact with the LotW Server.

To compensate for the URL change, I released a new version of DXKeeper (DXLab's logging component) last night.

This morning, LotW Management identified the error that prevented the Server's old URL from continuing to work. That error has been corrected, so all applications that could previously interoperate with the LotW Server should again be able to do so.

I agree with the above posts, this is absolute rubbish Why on Earth would they make changes like this at a time like this! The next phase will be to see what happens with the HRD 5.xx free version, will it be supported or will this be the moment when they say get 6.x or say goodbye to using LoTW with the HRD software.

If vers 5.xx won't load up to LOTW then I will say good by to HRD and not upgade any time period. It has benn on my mind to do so but I figured I would let them get the bugs out (say by vers. 7) before I buy it!!

It looks like the ARRL has indeed rolled back the changes. Using the original https://p1k.arrl.org URLs in HRD 5, I was able to upload my contacts moments ago that I did since May 12. (The world has not ended, woohoo!)

I did notice one oddity not related to HRD 5. If you go to the web site itself using the p1k.arrl.org, you'll be able to log in, but if you try to click on Your QSOs, it kicks you out back to the login screen, but this time the login screen has the lotw.arrl.org URL and if you log in there, all works fine. Probably an SSL thing.

My thanks to ARRL for rolling this back while everyone is probably involved in supporting Dayton and not taking a position that would have required those running old/unsupported logging programs to switch or upgrade. (I'm sure there will be a change in LOTW in the future that will require me to upgrade, but something this arbitrary doesn't seem like it should be it).

Copyright 2000-2016 eHam.net, LLC
eHam.net is a community web site for amateur (ham) radio operators around the world.
Contact the site with comments or questions.
WEBMASTER@EHAM.NETSite Privacy Statement