Skip to content
This repository has been archived by the owner on Feb 20, 2024. It is now read-only.

IgActionSpamError #29

Open
GaWr26 opened this issue Oct 21, 2019 · 15 comments
Open

IgActionSpamError #29

GaWr26 opened this issue Oct 21, 2019 · 15 comments

Comments

@GaWr26
Copy link

GaWr26 commented Oct 21, 2019

I got this today. Unfortunately I believe it's a block from IG...

(node:17073) UnhandledPromiseRejectionWarning: IgActionSpamError: POST /api/v1/media/2095210727513015946_6864386408/like/ - 400 Bad Request; feedback_required
    at Request.handleResponseError (/home/pi/jinsta/node_modules/instagram-private-api/dist/core/request.js:79:20)
    at Request.send (/home/pi/jinsta/node_modules/instagram-private-api/dist/core/request.js:49:28)
(node:17073) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:17073) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

@breuerfelix
Copy link
Owner

breuerfelix commented Oct 21, 2019

if the mentioned PR is merged, try the following:

  • run jinsta with jinsta -r -s my_seed -u bla -p bla
  • if you use advanced config set config.reset = true and config.seed = 'my_seed'
  • try if it works :)

you have to use -r or config.reset only if you choose a new seed key because this means to reset the old session and generate a new one

if it does work out, try to get the value when you experience a block.
if it is 30 for example, run the bot twice a day with a limit of 20 and increment this each day by 2 to 5 and see if you hit the limit again

try to reuse your old seed keys from time to time and increase their limit aswell, i would like to know if instagram saves the device id with the interaction limit

@GaWr26
Copy link
Author

GaWr26 commented Oct 22, 2019

hm Felix, ran it again today with reset and new seed and got the 400 Error again.
Now I see this on App and desktop when trying to log in to Instagram:
Bildschirmfoto 2019-10-22 um 13 44 14
How bad is this? Never seen this before...
Not sure how many likes but the progress counter went above 2000

@breuerfelix
Copy link
Owner

strange... dont think that this is too bad, what happens when you say get help logging in ?

@GaWr26
Copy link
Author

GaWr26 commented Oct 23, 2019

clicking the link brings me here: https://help.instagram.com/358911864194456
I have no clue what to do about this... will send you my logs

Edit: The logfile is empty... 0 Bytes...

@mikedigriz
Copy link

mikedigriz commented Oct 23, 2019

same thing happening to me
it's not a ban
you mast change password (reset by email)
until you see a request to confirm the information

i used a vpn, and differ browsers
reset cache and cookie
something of this helps me after 30+ iterations
then I saw a new form

my steps:

  1. logout
  2. login in instagram via browser
  3. press forgot password
  4. reset by email
  5. enter new passwords
  6. go to mail and klick on ''secure your account here'' in new letter
    repeat 6 again and again with switch vpn

I found it here

@breuerfelix
Copy link
Owner

breuerfelix commented Oct 23, 2019

the question is, why is this happening ? what have you done different than the others ?

have you used many different seeds ?

cause if this keeps happening to users, i will shut the bot temporarly because thats harder to fix than a 3 day ban ...

@GaWr26
Copy link
Author

GaWr26 commented Oct 23, 2019

Thank you very much @mixaxdd! I got my account back. I used a vpn but not sure if this is really necessary... What a damn dodgy process. I was clicking about with no luck until at some point a page showed up where it showed my profile information and I approved that and now I'm back in. What is this?

Well, never mind. Tomorrow I will start easy again with 10 likes...

@mikedigriz
Copy link

i used outdated version jinsta - 0.0.14
and i have this error (400 Bad Request)
spammed the error several times
may be it work so fast?
then Instagram detect that i use some illegal service
i change password and go asleep two days
all is good, i do nothing
no instapy and jinsta
and suddenly this strange block

@GaWr26
Copy link
Author

GaWr26 commented Oct 24, 2019

Today I ran jinsta gain with limiting likes to 10 with a new seed.
After 9 likes I got 400 Bad Request; feedback_required.

Feels like my account is flaged just as it was using InstaPy.
I hope this is not bad news for the approach and there's a way around this

@pavbro
Copy link

pavbro commented Oct 24, 2019

I'm catching this sometimes. Can you make some changes in the code to continue process instead of exit with Exception?

@GaWr26
Copy link
Author

GaWr26 commented Oct 25, 2019

Better day today. I ran with reset = true and a new seed.
It did 35 likes and ended as expected. Also logs were properly written.

Unfortunately like_limit was ignored which I had set to 8 so there seems to be a bug.

@mikedigriz
Copy link

I have bloked again. But easy got my account back. Reset password and click in mail "secure your account here" but open it in private window. Yes, confirmation window! Without private window it show block every time.

@micheledellaguardia
Copy link

I had the same problem, but I saw that jinsta is accessing Instagram every time with a different user agent.
Here are a couple of security confirmation email I got from Ig:

Cattura_1256

Cattura_1308

Is there a way to force a single user agent for any session, as should be using just my own mobile device? With an always different user agent i think it's easier for Ig to suspect of a bot activity.
Thanks a lot

@breuerfelix
Copy link
Owner

do you always use the same seed ? or do you change it ?

it should use the same user agent with the same seed / username :) but let me know !

@micheledellaguardia
Copy link

Hi, I had to change the seed (-r -s newseed) because of a IgActionSpamError, but after that I got this on Instagram App and a SMS/Confirmation code request on Jinsta. Is there a way to force a user agent even changing the seed?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants