I've analyzed the issue that prevents the use of the Widget.
The issue is that when the Widget is reserving drivers, the server responds with a "200 OK" response code, which should mean that everything is OK. However, later on, when the Widget attempts to book a race, it turns out that the server hadn't reserved any drivers, as verified through a few debugging reports. A similar but less common version of this bug is that the server will reserve the drivers and even verify that they've been reserved, but it still won't allow us to start the race. I am adding a test to version 1.5 which will check for this problem.
One forum member graciously allowed me to access his account so I could try to see the issue firsthand, and attempt to see how the official Remote Race page coped with that error. Alas, 14 perfect races later, I gave up trying to reproduce the problem there.
I'm estimating that the Widget has around 1,200 active users. Based upon the number of people who are posting in this thread that they have this issue, I'm concluding that, though serious, the problem affects a small subset of users. And even then,
it only appears to be sporadic. Due to the nature of the bug being server-based, there is not much I can do to fix it, either.
Some users have stated that one of the versions in the 0.9 series was the most reliable for them. I can retrofit the most stable version in that series with the new authentication code in the hopes that it will work better for you, but I won't be able to add the new driver selection feature into it.
If you are affected by this bug and you've sponsored development, I'd be happy to refund your money
send me a PM with the PayPal email address you donated with and I'll get that processed for you.