Jarvee Problem- EMAIL CONFIRMATION

BotManagement

Newbie
Joined
Jul 16, 2020
Messages
12
Reaction score
3
Hello BlackHatWorld,

I am facing a strange issue with two of my bot accounts. When I try to verify, I am met with the error:
The account requires email confirmation\or needs captcha verification in order to remove the restrictions.
I am signed in on Account 1 on my browser. When I attempt to verify via Jarvee on my server, Instagram displays this screen on my browser:
Instagram Verification.png

I click "This Was Me" and then nothing happens. Whenever I try to re-verify this entire process just loops again.

Other things i've tried:
  • I tried resetting the device IDs for the account.
  • I enabled the "Do not use embedded browser to login to Instagram" feature in the advanced settings.
  • I enabled the "If you have problems with email verification loop in the EB use this option to try to verify via api" checkbox then clicked "Login after successful verification" and clicked "Verify via email" which prompted an alert that said I should have received a code in my email. However, I did not receive a code.
Everything i've tried has had zero effect. I am starting to think it might be a problem with how Jarvee signs in, but I am unsure.

What should I do?
 
From the screenshot, it seems that you are try to login via Embedded Browser.

Try to uncheck it and give it a try again.

Hi, I already did that. My main problem was the "This Was Me" (TWM) block that I suppose appeared due to the IP address I was using. But I solved my problem using a different technique. I moved Jarvee over to the PC that I was logged in on and I was able to successfully validate Account 1. Account 2 however was a different case. Even with the new IP, Account 2 did not validate and the TWM loop began again. I managed to validate Account 2 by signing out of the browser and attempting to send the code to the email (which I enabled automatic email validation for) which finally sent the code to the email and allowed me to validate. I suspect the TWM problem might've been occurring due to me being signed in on the browser.
 
Back
Top