ProxyV4

I-Puppeteer ene-proxy eqinisekisiwe: ifulegi lokuvula kanye nokungena

· Updated:

Ukuqinisekiswa kwe-proxy ku-Puppeteer kwenzeka ezindaweni ezimbili: ikheli le-proxy lifakwa efulegini lokuvula le---proxy-server=http://ip:port, kanti igama lomsebenzisi nephasiwedi kufakwa ku-await page.authenticate({ username, password }). I-Chrome iphendula inselele ye-407 ye-proxy ngaleyo mininingwane yokungena nge-DevTools Protocol, ukuze iskripthi sakho se-Node.js sisebenzise i-IP ye-ProxyV4 ngaphandle kwesandiso sesiphequluli.

Puppeteer · HTTP
--proxy-server=http://ip:port + page.authenticate({ username, password })
I-IPv4 eyimfihlo (datacenter)
🇺🇸 United States
Kukhona esitokweni
Kusukela
$1.10 / IP / ngenyanga
Izaphulelo zenani
  • 1 IP$1.85
  • 3+ IPs$1.70
  • 10+ IPs$1.60
  • 25+ IPs$1.50
  • 50+ IPs$1.40
  • 100+ IPs$1.30
  • 200+ IPs$1.20
  • 500+ IPs$1.10
Thenga e-United States
I-IPv4 eyimfihlo (datacenter)
🇸🇬 Singapore
Kukhona esitokweni
Kusukela
$1.10 / IP / ngenyanga
Izaphulelo zenani
  • 1 IP$1.85
  • 3+ IPs$1.70
  • 10+ IPs$1.60
  • 25+ IPs$1.50
  • 50+ IPs$1.40
  • 100+ IPs$1.30
  • 200+ IPs$1.20
  • 500+ IPs$1.10
Thenga e-Singapore

Ukuqinisekisa kommeleli we-Puppeteer: isibonelo esiphelele

Dlulisa ikheli lommeleli ku---proxy-server bese ufaka imininingwane yokungena nge-page.authenticate() ngaphambi kokuzulazula kokuqala. Lesi sikripthi senza lokho kanye futhi sishicilela i-IP yokuphuma, ukuze uqinisekise ummeleli ngokugijima kanye kuphela:

// 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();
  }
})();

Okukhiphayo kufanele kubonise isimo esingu-200 kanye ne-IP yommeleli. I-407, ERR_TUNNEL_CONNECTION_FAILED noma i-IP yakho kusho ukuthi enye yezingxenye ezimbili ayikho; proxy not working ibala izimbangela ezijwayelekile ngethuluzi ngalinye.

Kungani ukungena kungeyona ingxenye yefulegi

I-Chrome ayiyamukeli imininingwane yokungena ngaphakathi kwe---proxy-server. Uma ubhala --proxy-server=http://user:pass@ip:port, isiphequluli asikwazi ukusebenzisa leli nani futhi izicelo ziyahluleka, ngokuvamile nge-ERR_NO_SUPPORTED_PROXIES. Gcina ifulegi lisekhelini nembobo kuphela, bese unikeza ikhasi imininingwane yokungena.

UkulandelanaUkubizaLokho okwenzayo
1puppeteer.launch({ args: ['--proxy-server=http://ip:port'] })Itshela i-Chrome ukuthi yimuphi ummeleli okufanele isicelo ngasinye sisisebenzise
2await page.authenticate({ username, password })Ihlinzeka ngemininingwane yokungena lapho ummeleli ephendula nge-407
3await page.goto(url, { waitUntil: 'domcontentloaded' })Ilayisha okuhlosiwe ngommeleli oqinisekisiwe

Amathebhu, izimo nama-IP angaphezu kowodwa

  • page.authenticate() isethwa ekhasini ngalinye: ithebhu ngayinye evela ku-browser.newPage() idinga ukubizwa kwayo ngaphambi kwe-goto() yokuqala
  • Ifulegi lokuqalisa lilungisa ummeleli oyedwa wesiphequluli sonke. Ku-IP ehlukile ngomongo ngamunye kunqubo eyodwa ye-Chrome, sebenzisa http://user:pass@ip:port ngayinye nge-anonymizeProxy() evela ephaketheni le-proxy-chain bese udlulisela umphumela njenge-proxyServer ku-browser.createBrowserContext({ proxyServer })
  • Ukusetha kusebenza ngendlela efanayo nge-puppeteer-extra kanye ne-puppeteer-extra-plugin-stealth
  • Njalo phetha nge-browser.close(), kuhlanganise nasezindleleni zamaphutha, kungenjalo izinqubo ze-headless Chrome zinqwabelana kuseva

I-Puppeteer enommeleli we-SOCKS5

I-Chrome ingasebenzisa ummeleli we-SOCKS5 (--proxy-server=socks5://IP:PORT) kodwa ayikwazi ukungena kuyo, futhi page.authenticate() ayisebenzi ku-SOCKS. Ngommeleli we-ProxyV4 (i-SOCKS5 inikezwa ngaphandle kwase-Vietnam; ama-IP ase-Vietnam angawama-HTTP kuphela) unezinketho ezimbili ezicacile: shintsha i-oda libe yimodi ye-HTTP noma imodi ekabili bese usebenzisa isibonelo esingenhla, noma vumela i-proxy-chain ivule isidlulisi sendawo esingenaphasiwedi esikungenela yona:

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);

Ukungena ngohlu oluvunyelwe lwe-IP kuyindlela yesithathu: engeza i-IP yomphakathi yomshini ku-oda bese i-Chrome ixhuma ngaphandle kwanoma yimiphi imininingwane yokungena.

Ukukhetha ama-IP eqenjini le-Puppeteer

I-headless Chrome idawuniloda amakhasi agcwele, izikripthi nezithombe, ngakho-ke ithrafikhi elinganiselwayo inqwabelana ngokushesha. Abammeleli be-ProxyV4 be-IPv4 eyimfihlo kanye ne-ISP emile abanamingcele yomkhawulokudonsa, i-IP ngayinye isiza ikhasimende elilodwa kuphela, futhi ukuvuselela kugcina ikheli elifanayo, okubalulekile lapho iseshini noma uhlu oluvunyelwe luboshwe kulo. Qhathanisa umkhiqizo we-IPv4 eyimfihlo kanye nomkhiqizo we-ISP emile uma isayithi eqondwe iphatha amabanga esikhungo sedatha ngendlela ehlukile.

Isinyathelo ngesinyathelo

  1. 1

    Vula i-Chrome ngekheli le-proxy

    Qala isiphequluli nge-const browser = await puppeteer.launch({ args: ['--proxy-server=http://ip:port'] });, usebenzisa i-IP nembobo evela ku-oda lakho le-ProxyV4.

  2. 2

    Qinisekisa ithebhu

    Vula ikhasi nge-const page = await browser.newPage(); bese ubiza i-await page.authenticate({ username: 'USER', password: 'PASS' }); ngaphambi kwanoma yikuphi ukuzulazula.

  3. 3

    Funda i-IP yokuphuma

    Zulazula nge-await page.goto('https://proxyv4.com/api/my-ip'); bese uhlola ukuthi impendulo ibonisa ikheli le-proxy.

  4. 4

    Vala isiphequluli

    Qeda nge-await browser.close(); ukuze kungabikho inqubo ye-Chrome esala isebenza.

Imibuzo evame ukubuzwa

Yini ebangela i-ERR_NO_SUPPORTED_PROXIES ku-Puppeteer?

Imininingwane yokungena ngaphakathi kwefulegi, njengakwi---proxy-server=http://user:pass@ip:port. Sebenzisa i---proxy-server=http://ip:port bese udlulisa igama lomsebenzisi nephasiwedi nge-page.authenticate().

Ithebhu yami yokuqala iyasebenza kodwa entsha ithola i-HTTP 407. Kungani?

Ukuqinisekisa kugcinwa ekhasini ngalinye. Biza i-await newTab.authenticate({ username, password }) ekhasini ngalinye olivulayo ngaphambi kokuba lizulazule.

Ingabe isiphequluli esisodwa se-Puppeteer singasebenzisa abammeleli abaningi ngesikhathi esisodwa?

Hhayi ngefulegi lokuqalisa lodwa. Sebenzisa i-proxy-chain ukuguqula ummeleli ngamunye oqinisekisiwe abe yikheli lendawo futhi unikeze umongo ngamunye wesiphequluli i-proxyServer yawo, noma qala isiphequluli esisodwa ngommeleli ngamunye.

Ngibahlola kanjani abammeleli abaningi ngaphambi kokubanikeza i-Puppeteer?

Banamathisele ku-proxy checker; iphatha abangafika ku-100 ngesikhathi futhi ayigcini amaphasiwedi.

Kungani page.authenticate() ingasebenzi nommeleli wami we-SOCKS5?

I-Chrome ayikusekeli ukungena ngegama lomsebenzisi nephasiwedi kwe-SOCKS5, ngakho-ke akukho okumele i-Puppeteer ikuphendule. Sebenzisa imodi ye-HTTP ye-oda, isidlulisi sendawo esivela ku-proxy-chain, noma ukungena ngohlu oluvunyelwe lwe-IP.

Imithombo

Ama-IP angalinganiselwe e-Chrome engenakhanda

I-IPv4 eyimfihlo emazweni angu-7 kanye ne-ISP emile e-US nase-Vietnam, kukhishwa ngokuzenzakalelayo ngemva kokukhokha, ikhasimende elilodwa nge-IP ngayinye.

Hlola amanani abukhoma ase-US

Related articles

Ama-proxy ngezinkundla
Ama-proxy okukrwela iwebhu: iqoqo elimile lama-IP anethrafikhi engalinganiselwa
Ama-proxy okukrwela iwebhu e-Python, Scrapy, Playwright ne-Selenium: iqoqo lama-IPv4 ayimfihlo nama-ISP amile, i-bandwidth engapheli, namanani anqunyiwe nge-IP.
Ukusetha i-proxy
Ukuqinisekiswa kwe-proxy ye-Playwright, i-IP eyodwa emile kumongo ngamunye
Nikeza umongo we-Playwright ngamunye i-proxy ye-HTTP(S) eqinisekisiwe ku-Node.js noma Python, fanisa isikhathi nolimi ne-IP bese uqinisekisa ikheli lokuphuma.
Ukusetha i-proxy
Ama-proxy aqinisekisiwe ku-Node.js: Axios, native fetch ne-Got
Qondisa izicelo ze-Node.js ne-TypeScript nge-proxy ye-HTTP(S) eqinisekisiwe: https-proxy-agent ye-Axios, undici ProxyAgent ye-fetch, ne-hpagent ye-Got.
Amathuluzi amahhala
Bhala kabusha uhlu lwe-proxy lube yifomethi elindelwe ithuluzi lakho
Guqula izinhlu ze-proxy kusiphequluli phakathi kwe-ip:port:user:pass, user:pass@ip:port, ama-URL e-http://, ama-URI e-SOCKS5, i-JSON ne-FoxyProxy, ngobuningi.
Ama-proxy ngezinkundla
Ama-proxy wokulandelela izinga le-SEO: bona ikhasi lemiphumela elibonwa umuseshi wendawo
Ama-proxy e-SEO ane-IPv4 eyimfihlo e-US, UK, Vietnam, Japan nezinye izimakethe ezi-4 ukuze izinga, ama-local pack nezikhangiso kufane nalokho okubonwa abendawo.
Ama-proxy ngezinkundla
Ama-proxy e-YouTube: vimbela isiteleka sesiteshi esisodwa ukuthi singathinti ezinye
Ama-proxy e-YouTube abadali neziteshi eziningi: i-static ISP noma i-IPv4 eyodwa esiteshini, ukuze isiteleka noma ukuvalwa kungathinti ezinye iziteshi.
IPV4 · united states
Iqoqo Lama-Proxy E-IPv4 Yangasese Yase-US Lokukhipha Idatha, Ukulandelela Amazinga Nokuhlola Izikhangiso
Thenga ama-proxy e-IPv4 yangasese ase-US: ama-IP e-datacenter, ikhasimende lilinye nge-IP, i-bandwidth engapheli. Yenzelwe uku-scrape, i-SERP nezikhangiso.
IPV4 · singapore
I-Proxy Ye-IPv4 Yangasese Yase-Singapore: I-IP Eyodwa Engashintshi Yesitolo Ngasinye Ne-akhawunti Yesikhangiso
I-proxy yangasese ye-IPv4 yase-Singapore: i-IP ye-datacenter emile yakho wedwa, yezitolo ze-Lazada ne-Shopee SG, ama-ad account e-SG nokuzenzekelayo kwesifunda.