-
Notifications
You must be signed in to change notification settings - Fork 641
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
Control proxy-chain's 'host' parameter from Apify's launchContext #2434
Comments
Hello @zuccon ! Are you sure this is an issue for this package ( As far as I understand - you want this "immediate" proxy server inside |
Hi @barjin, thanks for answering.
As far as I understood the https://docs.apify.com/sdk/js/docs/1.3/api/apify#apifylaunchpuppeteerlaunchcontext So in order for it to work, I believe this option needs to be propagated from
yes, this is the goal |
Hello again! I see that you're mentioning the npm ls crawlee apify apify-client proxy-chain puppeteer From your message, it seems that you're using Looking forward to hearing from you soon. Cheers! |
Hi @barjin, this is the output of
Is v2 also too old for this feature? |
Yes, In order to fix this in your project, you'll first have to switch your project to Crawlee. Here's the upgrading guide for it - feel free to ask questions if you encounter any problems on the way. |
Closing due to inactivity. |
The
host
argument has been added to proxy-chain, for its listener to be bound to something else than0.0.0.0
.However it's not possible to set this parameter while launching Puppeteer as it's not available in the
launchContext
.Is it possible to add this option to the
launchContext
, or do you have any advice for launching Puppeteer with a customizedproxy-chain
instance which has this argument too?Thanks!
The text was updated successfully, but these errors were encountered: