-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No sites work and proxy doesnt work #33
Comments
@authsoftware thanks for opening this ticket. Regarding the proxy issues, please see #29. And regarding the |
Can you also provide some details to reproduce the issue on Footlocker? Preferably a I recently fixed an unrelated issue with the footsites here. |
I am also not having any issues with |
Yes I will send you the tasks I have so you could test them on Foots, Shopify, Supreme |
Supreme
Shopify
Footlocker
|
@authsoftware using a The reason I made these fields nullable is for site integrations or individual products where they are N/A e.g no shipping speed or style options on Supreme, or products without size options. |
Okay thank you, I will test that and let you know |
Okay so after fixing that and fixing the proxies issue, this is the error I have now
task object
|
@authsoftware thanks for this, I will test with this I have seen this error from puppeteer before, particularly when using headless mode. Some websites will reject the headless user agent so we need to manually set the user agent when the page is created. I will verify that this is the issue and then put up a quick fix for it. |
@authsoftware this looks to be the case, can you confirm that it is working for you in headful mode? |
@samc621 I did enable headful mode by making headless false in cluster.js but i have an issue with almost any site whenever you go to the product page it keeps going back to the main page for example on champs it goes to the product page then redirects to the home page then this issue comes up
|
@authsoftware this is happening for you with the sample Champs task above? It is working fine for me, at least in headful mode. |
@samc621 Yes it is happening to me in all sites |
Based on the selector in that stack trace, it sounds like the modal which sometimes appears on the footsites is not appearing for you. Using I understand that you're seeing this behaviour across sites, but I will need stack traces from the others, then. This specific error is with a selector on the footsites. |
I am seeing this error as well (on headless) @samc621:
Here is the task JSON I used:
edit: I am seeing this as a the body response via:
Is there a way to set the user agent dynamically with somehow? Maybe that is still the issue? |
After playing around this a little more, I was able to get past the error with the following:
This got the timeout errors to go away. (note I edited this a couple times) |
@labboy0276 thanks for the updates here! There's a lot we can do around randomizing browser fingerprints, and starting with the UA is a great idea. If this has been tested and confirmed to help address a problem you are facing, please feel free to open a Pull Request. I am happy to try it on my end and then merge it as long as it works. |
@labboy0276 as for this error:
Can you try the suggestion I mentioned above, which is to add So line 256 would look like:
What I think is going on here is that this modal only shows on some of the footsites, but not Champs. Using the default timeout from Puppeteer, it will timeout after 30s, which will break your task midway. But with the timeout of 0, it will basically never time out, but listen asynchronously (non-blocking) and close the modal if it does ever appear. I suggest trying this and see if it works. If it does, seems like a quick fix we can get in there (feel free to open a PR). |
@samc621 I put in that PR. I didn't have issues with that timeout after I fixed everything I mentioned. If it does happen again, I can try your suggestion. |
@labboy0276 thanks for that! So just to confirm, this fix is just for the |
@samc621 the user agent issue fixes all sites for peoples who use headless. |
I keep getting Error 429, too many requests, whenever there's a drop.. for footsites. Anyone knows a way round this? |
@labboy0276 thank you! I am testing that PR now. |
@samc621 and @labboy0276 , based on the discussions and the closed PR #39, I am guessing we can close this issue? |
@13ROY yes, I am closing this issue now. |
I have tried to use proxies but none worked and it keeps using local to open the sites.
Also I cannot get anything to actually checkout, footlocker keeps saying product not found on both product id and link, nike wont add to bag, shopify keeps giving an error of
on champs it is stuck on closing modal.
Supreme this is the error I receive
The text was updated successfully, but these errors were encountered: