Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Any action with account is blocked for security but no email is recieved

  • 3 antwurd
  • 4 hawwe dit probleem
  • 20 werjeftes
  • Lêste antwurd fan mpowend

more options

I had an old version of firefox on my mint64 system and I was (and still is) logged in my account there. But when I tried to log into a new firefox developer edition it said request blocked for security reasons. now whatever I try, like adding secondary email or changing password, is blcoked for security reasons. and I received no email from firefox so I'm just locked out. how to regain my access?

I had an old version of firefox on my mint64 system and I was (and still is) logged in my account there. But when I tried to log into a new firefox developer edition it said request blocked for security reasons. now whatever I try, like adding secondary email or changing password, is blcoked for security reasons. and I received no email from firefox so I'm just locked out. how to regain my access?

Keazen oplossing

when I checked today, the problem was solved by itself and I could login successfully. I didn't take any special action. seems like the problem was in server side and waiting solves it.

Dit antwurd yn kontekst lêze 👍 0

Alle antwurden (3)

more options

Hello, I'm scared to don't understand. You have an account on this website (support.mozilla.org) and you try to access your account from 2 different browsers? Can you access to your account and click Sign Out from your user menu?

more options

I mean the firefox sync account. I'm logged in it on my old version of firefox. but when I try to login on the new version, I get "request is blocked for security reasons". also trying to change password or email in "manage account" in the old version leads to the same message.

more options

Keazen oplossing

when I checked today, the problem was solved by itself and I could login successfully. I didn't take any special action. seems like the problem was in server side and waiting solves it.

Bewurke troch mpowend op