search

Hari-Nagarajan / fairgame

Tool to help us buy hard to find items.
GNU General Public License v3.0
2.44k stars 804 forks source link

"Timed out waiting for the flyout to open and populate." #717

Open caseych4n opened 3 years ago

caseych4n commented 3 years ago

Describe the bug Not sure if this is a bug or not, but this only happens for pages with the "see all buying options" window in the screenshot Screenshot 2021-04-22 012026

To Reproduce Steps to reproduce the behavior: Run the code with these ASIN's as examples: This issue happens with multiple items here are some example asins B08VLLBFR3 (zotac rtx 3080 white) B08P7ZKQPP (zotac rtx 3070 white)

this is what the command prompt shows when the error shows up: timedoutzotac

After I clicked, "see all buying options," the code would run through and then refresh then run into the same problem again.

Desktop (please complete the following information):

the bot runs fine on the items that are completely out of stock, but not on one's that have scalpers and another third party amazon sellers.

HaloGeekster commented 3 years ago

@caseych4n I have the same issue occasionally. (Though I assume its my fault for running 12+ instances at the same time.) Watching the browser window, I see the fly-out pop out for a fraction of a second and then immediately close itself while the dark overlay on the rest of the page remains I fixed it once by clearing browser-data, and another time by 'End Task'ing some extra instances of pipenv.exe that remained open in background processes for some reason.

Edit: It could also be an anti-botting measure, I've noticed I cant access my account page from browser anymore. I just get a "Sorry, we couldn't find that page" with a dog.

tgadberry1 commented 3 years ago

I noticed this issue for the first time today when I was setting up a 3rd machine to watch additional items. Namely, the 5900X but not 3060Ti's gave me this issue. As @HaloGeekster mentioned, it may be a botting issue. When it happens on fair game, it happens for me just the same when I manually try to check all buying options. However, open that same page in an incognito tab and it works just fine.

IvanShift commented 3 years ago

Edit: It could also be an anti-botting measure, I've noticed I cant access my account page from browser anymore. I just get a "Sorry, we couldn't find that page" with a dog.

I called Amazon support. They have no idea why this is happening or what to do. But they gave me this link: https://amazon.com/access It shows the Amazon site as a mobile version where you can access to "Account"-page.

jobes911 commented 3 years ago

I got the same problem, Captcha and the See all buyin option button / slide on the right side of the screen remain empty and the bot doesnt work.

tgadberry1 commented 3 years ago

Curious. How many of you were running multiple instances on your account (either on one or multiple devices), and how low did you set the delay?

tgadberry1 commented 3 years ago

Edit: It could also be an anti-botting measure, I've noticed I cant access my account page from browser anymore. I just get a "Sorry, we couldn't find that page" with a dog.

I called Amazon support. They have no idea why this is happening or what to do. But they gave me this link: https://amazon.com/access

To be fair, I doubt the standard Amazon customer service rep is versed enough to know about all anti-bottling measures the devs may have slipped in. I’m going to kill all instances today and give it 24hrs to see if it resets.

tgadberry1 commented 3 years ago

To be fair, I doubt the standard Amazon customer service rep is versed enough to know about all anti-bottling measures the devs may have slipped in. I’m going to kill all instances today and give it 24hrs to see if it resets.

Update: Once all instances were stopped, my Amazon account looks like it returned to normal within an hour or two. For now, the solution seems to be to exercise caution and don't get too greedy.

Amazon may have implemented these soft blocks to throttle bot traffic/efficacy. Consider 1) increasing the delay between ASIN cycles, 2) don't run multiple devices from multiple locations, and 3) keep it to one or two instances of the program. If you happen to dial-in more precise tolerances please share them!

JCrowe86 commented 3 years ago

Having the same issue. Only running one instance with 2 ASINs, 1.5sec delay. Kept getting the error a lot yesterday. Ran almost all day with no issue it but something triggered it a bit ago and now I can't get it to go away.

Edit - If I open a new chrome window and access Amazon, I get a captcha, flyout does not work for "See all buying options" It shows up for a split second then goes away. Also cant access my account as it gives "Sorry, Couldn't find that page"

Went and opened Amazon in Edge and signed in, no captcha, and all functions working normally. Not sure it's on Amazon's side unless they track activity by browser somehow.

tgadberry1 commented 3 years ago

Well, I said everything was back to normal a little too early. My account still seems to have a soft-ban. Looking back through older issues posted, this has been a very common issue. I can’t get a definite answer as to how long the limits will last. I would strongly recommend that the ReadMe include a warning early on about too much/too fast and how it can impact accounts. There are reports of it happening even with the default 3 second delay. I will update once my account is back to normal or if I have to go through Amazon support. On Apr 23, 2021, 4:44 PM -0500, JCrowe86 @.***>, wrote:

Having the same issue. Only running one instance with 2 ASINs, 1.5sec delay. Kept getting the error a lot yesterday. Ran almost all day with no issue it but something triggered it a bit ago and now I can't get it to go away. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

DakkJaniels commented 3 years ago

You are welcome to make a PR to write whatever warning you think is appropriate. We already tell people not to run multiple instances, but people don't seem to care. image

tgadberry1 commented 3 years ago

Ah, I interpreted “concurrently” as two instances on the same device. Semantic issue on my part.

Thanks! I’ll try to clarify when I put something together! On Apr 23, 2021, 6:26 PM -0500, DakkJaniels @.***>, wrote:

You are welcome to make a PR to write whatever warning you think is appropriate. We already tell people not to run multiple instances, but people don't seem to care. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

Eternity-Soap commented 3 years ago

I agree that this appears to be an anti-botting measure that's triggered by running multiple instances. I also got greedy and disregarded the warnings about doing so and am having this problem as well. Interestingly it only seems to affect my chrome browser; I have no difficulty looking at purchase options when using Edge manually. It also only seems to affect the offending account and leaves others coming from the same network alone.

CptnFluffy commented 3 years ago

I started having this problem yesterday. I was running two instances with a one second delay. I turned it off overnight and started it again this morning, but only one instance with a two second delay. So far it's been running for about five hours and there haven't been any problems. My moneys on anti-botting measure as well.

CJoseFlores commented 3 years ago

I agree that this appears to be an anti-botting measure that's triggered by running multiple instances. I also got greedy and disregarded the warnings about doing so and am having this problem as well. Interestingly it only seems to affect my chrome browser; I have no difficulty looking at purchase options when using Edge manually. It also only seems to affect the offending account and leaves others coming from the same network alone.

It seems that amazon does not do any soft-banning by IP, and it's only per account. One thing I did note from others (including from a previous comment in this thread) is that you can check if you're soft banned by attempting to access the 'Account' page. Even if the fly-out works on some browsers, if you can't access the 'Account' page, you're still soft banned.

tgadberry1 commented 3 years ago

In my experience, shadow bans clear ~24 hours after you halt all bots on your account. There's a new "Disclaimer" section on the README that helps bring the issue forward to new users.

On Mon, Apr 26, 2021 at 4:45 PM Carlos Flores @.***> wrote:

I agree that this appears to be an anti-botting measure that's triggered by running multiple instances. I also got greedy and disregarded the warnings about doing so and am having this problem as well. Interestingly it only seems to affect my chrome browser; I have no difficulty looking at purchase options when using Edge manually. It also only seems to affect the offending account and leaves others coming from the same network alone.

It seems that amazon does not do any soft-banning by IP, and it's only per account. One thing I did note from others (including from a previous comment in this thread) is that you can check if you're soft banned by attempting to access the 'Account' page. Even if the fly-out works on some browsers, if you can't access the 'Account' page, you're still soft banned.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://urldefense.com/v3/__https://github.com/Hari-Nagarajan/fairgame/issues/717*issuecomment-827165430__;Iw!!KwNVnqRv!WHJij9B3GywM9h9uik_k9BOMNy__MmAVM6IAg7ybcTaGrPnMYh7BGwKD22kcVGTAJh4$, or unsubscribe https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ACZ647WZN3PL2DRJWSIWZYLTKXNGBANCNFSM43L6TLGA__;!!KwNVnqRv!WHJij9B3GywM9h9uik_k9BOMNy__MmAVM6IAg7ybcTaGrPnMYh7BGwKD22kcooh4zoE$ .

b-hairston commented 3 years ago

Just a quick update if people are still having issues, clearing cookies in the browser window that fairgame is running in should fix the issue mentioned above. At least it has been a solution that has worked in my case

mlgvain commented 3 years ago

Just a quick update if people are still having issues, clearing cookies in the browser window that fairgame is running in should fix the issue mentioned above. At least it has been a solution that has worked in my case

I'm having this issue with 0.6.8 It used to not have a problem, then something happened over-night and it's giving me the same thing.

I tried clearing the cookies, but that didn't seem to help.

Scope666 commented 3 years ago

Also having this problem, started yesterday morning, I think Amazon is getting more aggressive with their anti-bot settings. Clearing cookies does NOT help. (soft-ban, you see the dogs when you click on the ACCOUNT page)

mlgvain commented 3 years ago

Also having this problem, started yesterday morning, I think Amazon is getting more aggressive with their anti-bot settings. Clearing cookies does NOT help. (soft-ban, you see the dogs when you click on the ACCOUNT page)

Yeah, that's what I was getting, but oddly enough, if I used a different browser it let me go to my Account page with no issues.

Scope666 commented 3 years ago

I'm seeing the same, they're probably soft-banning a combo of the IP address AND the user agent of the browser.

BorisG491 commented 3 years ago

It's not just IP an user agent. In my case I think it's the account as well. I can't get the "see all buying options" to work even on my phone's amazon app. Used a different IP, still not working. Using edge, still not working. Registered a new account and running from a different IP, it works again.

ghost commented 3 years ago

So what's the fix for this ... You guys just keep making new accounts? Mine did this after less than 12hrs ......

Scope666 commented 3 years ago

Using the --delay parameter fixed it for me, around 7 - 8 seconds seems to work.

DeathsSatellite commented 3 years ago

Had the same issue. An ipconfig/release and then ipconfig/renew seemed to work for me.

Jay311xx commented 3 years ago

Just happened to me only running one instance. Cookies and ipconfig/release ipconfig/renew did not work. First time using app for less than an hour. I was only doing one item. So maybe because it was spamming that item so fast I got a ban. Any fix besides just waiting? Guess I will just put some more items in next time I run it.

Jay311xx commented 3 years ago

Temp ban again today after running it for an hour. Was doing 4 items this time so it wasn't because of spamming same item. Think app is broken atm so once fixed I will start with 8 second delay and if that works keep going down 1 second. Will post results.

Liang2527 commented 3 years ago

Temp ban again today after running it for an hour. Was doing 4 items this time so it wasn't because of spamming same item. Think app is broken atm so once fixed I will start with 8 second delay and if that works keep going down 1 second. Will post results.

Hi, DId you get any results?