Pheonix - Talkback rises.

You only register one authenticator at a time. (you can copy the settings to another autrhenticator...but it needs to be the same secret, generating the numerically same one time code every time).

It does not matter where this authenticator is (phone, laptop, password vault...I have THE SAME setting in all three, and all three generate the same code), but wherever you log in, you use this ONE code (that changes every thirty seconds or whatever).

So if the laptop works, you have used the correct authenticator (which therefore must be correctly registered to turnstile - and you can only have one registered to turnstile at a time) to generate the code to log in. USE THIS SAME AUTHENTICATOR TO LOG IN ON YOUR PHONE.

If you pghone doesn't log in correctly using this code, clear your cookies on your phone browaser, and log in again.

If you can use a OTP code from an authenticator to log in anywhere, then you can use it to log in anywhere else.

There was a recommendation for Authy on ios. Use that (or something like it) to generate the OTP code on your phone.

Go to turnstile turnstile.trentend.uk/ using your phone. Click lost your device. It will send you an authentication email. Open that email in the same browser on your phone that you visited turnstile with. Use that QR code, or the key on the same page, to register Authy (or another authenticator) on your phone.

You should now be able to log in using the same browser on your phone, using the OTP code generate by authy on your phone. If you can't clear the cookies on your phone browser and try again.

When you can log in on your phone, do nothing else, do not register another authenticator on turnstile.

Visit turnstile on your laptop broswer. Log out if you have to). Log back in (your username and password remains what it has always been during this process) using the code provided using Authy on your phone (look at it, manually copy it to the log in on your laptop). If you do this before the timeout period you should be logged in.

One authenticator, providing one OTP code. You can then copy the details from authy on your phone so that other authenticators provide the SAME OTP code at all times.

Authenticator log in not required for partridge. It's the username and password correctly incorporated into the URL. See the partridge thread.

DAB not available on the Nottingham transmitter this morning. It's on FM, because it's all I can get.

That is a sign that the username and password encoded in the URL, has not been recognised/validated. Check the spelling, and form of the URL.

Are you using the correct username, password, and form of URL? It is working for all others reporting, and nothing has changed on the backbend. My test connections all work exactly as before the move.

I am unable to duplicate your problem. If I can't duplicate it, I can't problem solve it.... Because it is a problem that doesn't actually exist.

Check your credentials again. Check the url form and that there are no typos. There is no observable reason that a correctly formatted request should fail. The error message you previously mentioned suggested that your username, password, or the URL form were incorrect.

If you have changed the password, the old password won't work in the url, only the current registered password... Because the admission is based on the current credentials stored in the credentials backend.

Awl gud nah?

I can get radio Newark, radio Derby, but no radio Nottingham on DAB from my current location in cotgrave. It will no doubt resurface at some point depending on the weather. In the meantime I shall put it on the wonderful notts commentary, as more here are fans of the bigger club in Nottingham than the foresters. Or so it seems.....