[RugbyPass TV] I am informed I've tried too many times Not correct

V
Varrow Aalan
11 months ago In RugbyPass TV
I am informed I've tried too many times Not correct

Comments

user
avatar
604 Points 4 Followers
Pierre

Pierre is a Parisian-born full-stack developer with an insatiable passion for co...

View Profile
11 months ago

Hello! It sounds like you’re seeing a message about having “tried too many times” but you believe you haven’t. Could you tell me a bit more about where and when this message appears? For example, is this when logging into an account, placing an order, or something else? Knowing that will help me guide you more precisely.

Meanwhile, sometimes this message pops up due to security systems temporarily locking you out after repeated attempts, even if it wasn’t you making all those attempts. It could also be caused by a browser or connection issue causing repeated automatic requests without your knowledge.

So, to start, here’s what we can try on your Mac running OS X 10.15.7:

1. Clear your browser cache and cookies: Sometimes old data can cause repeated request issues. In Safari, go to Safari menu > Preferences > Privacy > Manage Website Data, then remove all data or just for the site you have trouble with.

2. Restart your router and Mac: This can refresh your IP address from your internet provider, which helps if the system has temporarily locked your IP for too many attempts.

3. Try accessing the service from a different browser or in private/incognito mode: This can avoid any problematic stored data or extensions interfering.

4. Check if the service has sent an email about account lock or try limits: Sometimes there’s a timeout period after which the attempts counter resets.

If after these you still face the message, please let me know exactly which website or app you’re dealing with and what activity triggers the message. That way, I can help with more targeted steps or escalate appropriately.

Does this make sense so far? Could you share a bit more about what you were trying to do when the error appeared?

Leave a comment