Puppeteer leh baroksi la xaqiijiyay: calanka furitaanka iyo gelitaanka
Waxaa qoray Kooxda Injineernimada ee ProxyV4 · Updated:
Xaqiijinta baroksiga Puppeteer waxay ka dhacdaa labo meel: ciwaanka baroksiga wuxuu galaa calanka furitaanka ee --proxy-server=http://ip:port, magaca isticmaalaha iyo erayga sirta ahna waxay galaan await page.authenticate({ username, password }). Chrome wuxuu xogtaas aqoonsiga kaga jawaabaa caqabadda 407 ee baroksiga isagoo adeegsanaya DevTools Protocol, si qoraalkaaga Node.js u isticmaalo IP-ga ProxyV4 la'aanteed kordhinta biraawsarka.
--proxy-server=http://ip:port + page.authenticate({ username, password })- 1 IPUS$1.85
- 3+ IPUS$1.70
- 10+ IPUS$1.60
- 25+ IPUS$1.50
- 50+ IPUS$1.40
- 100+ IPUS$1.30
- 200+ IPUS$1.20
- 500+ IPUS$1.10
- 1 IPUS$1.85
- 3+ IPUS$1.70
- 10+ IPUS$1.60
- 25+ IPUS$1.50
- 50+ IPUS$1.40
- 100+ IPUS$1.30
- 200+ IPUS$1.20
- 500+ IPUS$1.10
Xaqiijinta proxy ee Puppeteer: tusaale dhammaystiran
Ku gudbi cinwaanka proxy-ga --proxy-server xogta gelitaankana ku gudbi page.authenticate() ka hor socdaalka koowaad. Script-kani sidaas saxda ah ayuu sameynayaa wuxuuna daabacayaa IP-ga bixitaanka, si aad proxy-ga ugu xaqiijiso hal orod kaliya:
// npm i puppeteer
const puppeteer = require('puppeteer');
const PROXY = { host: 'IP', port: 'PORT', username: 'USER', password: 'PASS' };
(async () => {
const browser = await puppeteer.launch({
args: [`--proxy-server=http://${PROXY.host}:${PROXY.port}`],
});
try {
const page = await browser.newPage();
await page.authenticate({ username: PROXY.username, password: PROXY.password });
const res = await page.goto('https://proxyv4.com/api/my-ip', { waitUntil: 'domcontentloaded' });
console.log(res.status(), await page.evaluate(() => document.body.innerText));
} finally {
await browser.close();
}
})();Natiijadu waa inay muujisaa heerka 200 iyo IP-ga proxy-ga. 407, ERR_TUNNEL_CONNECTION_FAILED ama IP-gaaga gaarka ah waxay la macno tahay in labada qaybood midkood maqan yahay; proxy aan shaqaynayn wuxuu taxayaa sababaha caadiga ah qalab kasta.
Sababta gelitaanku uusan uga mid ahayn calanka
Chrome ma aqbalo xogta gelitaanka gudaha --proxy-server. Haddii aad qorto --proxy-server=http://user:pass@ip:port, browser-ku ma isticmaali karo qiimahaas codsiyaduna way fashilmayaan, sida caadiga ah qaladku waa ERR_NO_SUPPORTED_PROXIES. Calanka ku koob cinwaanka iyo port-ka, xogta gelitaankana ku wareeji bogga.
| Kala-horreynta | Wicitaanka | Waxa uu qabto |
|---|---|---|
| 1 | puppeteer.launch({ args: ['--proxy-server=http://ip:port'] }) | Wuxuu Chrome u sheegaa proxy-ga ay tahay inuu codsi kasta isticmaalo |
| 2 | await page.authenticate({ username, password }) | Wuxuu bixiyaa xogta gelitaanka marka proxy-gu ku soo jawaabo 407 |
| 3 | await page.goto(url, { waitUntil: 'domcontentloaded' }) | Wuxuu bartilmaameedka ku soo shubaa proxy-ga la xaqiijiyay |
Tab-yada, xaaladaha iyo in ka badan hal IP
page.authenticate()waxaa loo dejiyaa bog kasta goonidiisa: tab kasta oo ka yimaadabrowser.newPage()wuxuu u baahan yahay wicitaan u gaar ah ka horgoto()ugu horreeya- Calanka furitaanku wuxuu hal proxy ku hagaajiyaa browser-ka oo dhan. Si aad IP kala duwan ugu hesho context kasta oo ku dhex jira hal nidaam Chrome ah, mari
http://user:pass@ip:portkastaanonymizeProxy()oo ka tirsan xirmadaproxy-chainnatiijadana u gudbi sidiiproxyServeroo la siiyobrowser.createBrowserContext({ proxyServer }) - Habayntu si la mid ah ayey ula shaqaysaa
puppeteer-extraiyopuppeteer-extra-plugin-stealth - Had iyo jeer ku dhammee
browser.close(), xitaa dariiqyada khaladaadka, haddii kale hawlaha headless Chrome ayaa ku kor urursanaya server-ka
Puppeteer oo wata proxy SOCKS5 ah
Chrome wuu isticmaali karaa proxy SOCKS5 ah (--proxy-server=socks5://IP:PORT) laakiin ma gali karo midkaas, page.authenticate()-na ma khuseeyo SOCKS. Marka aad haysato proxy ProxyV4 ah (SOCKS5 waxaa laga bixiyaa meel ka baxsan Vietnam; IP-yada Vietnam waa HTTP keliya) waxaad haysataa laba ikhtiyaar oo suubban: u beddel dalabka habka HTTP ama qaabka labanlaabka ah (dual mode) oo isticmaal tusaalaha kore, ama u oggolow proxy-chain inuu furo sii-gudbiye maxalli ah oo aan password lahayn kaas oo kuu gelaya adiga:
const proxyChain = require('proxy-chain');
const local = await proxyChain.anonymizeProxy('socks5://USER:PASS@IP:PORT');
const browser = await puppeteer.launch({ args: [`--proxy-server=${local}`] });
// ... when done:
await browser.close();
await proxyChain.closeAnonymizedProxy(local, true);Gelitaanka liiska cad ee IP (whitelist) waa habka saddexaad: ku dar IP-ga guud ee aaladda dalabka Chrome-kuna wuxuu ku xirmi doonaa iyadoo aan wax xog gelitaan ah loo baahnayn.
Xulashada IP-yada koox Puppeteer ah (fleet)
Headless Chrome wuxuu soo dejiyaa bogagga buuxa, qoraallada (scripts) iyo sawirrada, markaa taraafikada la cabbiro si dhakhso ah ayey u kordhaysaa. Proxy-yada ProxyV4 ee gaarka ah ee IPv4 iyo ISP ma guurtada ah (static) ma laha cabbirka bandwidth-ka, IP kasta wuxuu u adeegaa hal macmiil oo keliya, cusboonaysiintuna waxay ilaalisaa isla cinwaanka, taas oo muhiim ah marka session ama liiska la oggol yahay ku xiran yahay. Isbarbardhig badeecada IPv4 ee gaarka ah iyo badeecada ISP ee ma guurtada ah haddii bogga bartilmaameedka ahi uu ula dhaqmo qaybaha datacenter-ka si ka duwan.
Tallaabo tallaabo
- 1
Ku fur Chrome ciwaanka baroksiga
Ku bilow biraawsarka
const browser = await puppeteer.launch({ args: ['--proxy-server=http://ip:port'] });, adoo adeegsanaya IP-ga iyo dekedda ka timid dalabkaaga ProxyV4. - 2
Xaqiiji tab-ka
Ku fur bog
const page = await browser.newPage();oo wacawait page.authenticate({ username: 'USER', password: 'PASS' });ka hor socod kasta. - 3
Akhri IP-ga bixitaanka
Ku fur
await page.goto('https://proxyv4.com/api/my-ip');oo hubi in jawaabtu ay muujinayso ciwaanka baroksiga. - 4
Xir biraawsarka
Ku dhammee
await browser.close();si aanu u harin wax hannaan Chrome ah oo shaqaynaya.
Su'aalaha badanaa la isweydiiyo
Maxaa sababa ERR_NO_SUPPORTED_PROXIES gudaha Puppeteer?
Xogta gelitaanka oo la dhex geliyo calanka, sida --proxy-server=http://user:pass@ip:port. Isticmaal --proxy-server=http://ip:port oo username-ka iyo password-ka ku dhex gudbi page.authenticate().
Tab-kayga koowaad wuu shaqaynayaa laakiin tab cusub wuxuu helayaa HTTP 407. Sababtu waa maxay?
Xaqiijinta waxaa loo kaydiyaa bog kasta goonidiisa. U wac await newTab.authenticate({ username, password }) bog kasta oo aad furto ka hor inta uusan socdaalin.
Miyuu hal browser oo Puppeteer ah isticmaali karaa dhowr proxy isku mar?
Keliya calanka furitaanka laguma samayn karo. Isticmaal proxy-chain si aad proxy kasta oo la xaqiijiyay ugu beddesho cinwaan maxalli ah oo sii browser context kasta proxyServer u gaar ah, ama bilow hal browser proxy kasta.
Sideen u tijaabiyaa proxy-yo badan ka hor inta aanan siin Puppeteer?
Ku dheji hubiyaha proxy-ga; wuxuu qaadaa ilaa 100 markiiba mana kaydiyo ereyada sirta ah.
Maxay page.authenticate() ula shaqayn la'dahay proxy-gayga SOCKS5?
Chrome ma taageero gelitaanka username iyo password ee SOCKS5, markaa ma jiro wax ay Puppeteer ka jawaabto. Isticmaal habka HTTP ee dalabka, sii-gudbiye maxalli ah oo ka socda proxy-chain, ama gelitaanka liiska cad ee IP.
Ilaha
IP-yo aan xaddidnayn oo loogu talagalay headless Chrome
IPv4 gaar ah oo ku yaal 7 waddan iyo weliba ISP ma guurto ah oo ku yaal US iyo Vietnam, oo si toos ah loo bixiyo lacag-bixinta ka dib, hal macmiil IP kasta.
Fiiri qiimaha tooska ah ee US