ProxyV4

Puppeteer tare da ingantaccen proxy: tutar farawa tare da shiga

· Updated:

Tantancewar proxy a Puppeteer na faruwa ne a wurare biyu: adireshin proxy na shiga cikin tutar farawa ta --proxy-server=http://ip:port, sannan sunan mai amfani da kalmar sirri na shiga cikin await page.authenticate({ username, password }). Chrome yana amsa kiran 407 na proxy da waɗannan bayanan shiga ta hanyar DevTools Protocol, don haka lambar rubutunka ta Node.js za ta iya amfani da IP na ProxyV4 ba tare da ƙarin tsawo na burawza ba.

Puppeteer · HTTP
--proxy-server=http://ip:port + page.authenticate({ username, password })
Private IPv4 (datacenter)
🇺🇸 United States
Akwai a ajiye
Daga
$ 1.10 / IP / wata
Rangwamen yawan oda
  • 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
Sayi United States
Private IPv4 (datacenter)
🇸🇬 Singapore
Akwai a ajiye
Daga
$ 1.10 / IP / wata
Rangwamen yawan oda
  • 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
Sayi Singapore

Tabbatar da proxy a Puppeteer: cikakken misali

Shigar da adireshin proxy a cikin --proxy-server sannan bayanan shiga ta page.authenticate() kafin lodawa ta farko. Wannan rubutun yana yin hakan daidai kuma yana nuna IP din fita, don haka za ka iya tabbatar da proxy a gudu daya:

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

Sakamakon ya kamata ya nuna matsayi 200 da IP din proxy. Samun 407, ERR_TUNNEL_CONNECTION_FAILED ko IP dinka na asali yana nufin daya daga cikin bangarorin biyu ya bace; proxy ba ya aiki yana lissafa dalilan da aka saba samu ga kowace manhaja.

Dalilin da ya sa bayanan shiga ba sa cikin flag

Chrome ba ya karbar bayanan shiga a cikin --proxy-server. Idan ka rubuta --proxy-server=http://user:pass@ip:port, burauzar ba za ta iya amfani da shi ba kuma buƙatun za su fadi, galibi tare da ERR_NO_SUPPORTED_PROXIES. Bar flag din ga adireshi da kofa (port) kawai, sannan ka mika bayanan shiga ga shafin.

JeriKiraAbin da yake yi
1puppeteer.launch({ args: ['--proxy-server=http://ip:port'] })Yana gaya wa Chrome wane proxy ya kamata kowace buƙata ta yi amfani da shi
2await page.authenticate({ username, password })Yana bayar da bayanan shiga lokacin da proxy ya mayar da martanin 407
3await page.goto(url, { waitUntil: 'domcontentloaded' })Yana loda shafin da aka nufa ta hanyar ingantaccen proxy

Shafukan tab, mahallai da IP fiye da daya

  • Ana saita page.authenticate() ne ga kowane shafi: kowane tab daga browser.newPage() yana buƙatar kiransa na kansa kafin goto() ta farko
  • Flag din kaddamarwa yana daidaita proxy guda daya ne ga daukacin burauzar. Don samun IP daban ga kowane mahallin bincike a cikin aikin Chrome guda daya, sarrafa kowane http://user:pass@ip:port ta hanyar anonymizeProxy() daga kunshin proxy-chain sannan ka mika sakamakon a matsayin proxyServer zuwa browser.createBrowserContext({ proxyServer })
  • Tsarin yana aiki iri daya da puppeteer-extra da puppeteer-extra-plugin-stealth
  • Koyaushe ka kammala da browser.close(), har ma a hanyoyin kurakurai, in ba haka ba ayyukan headless Chrome za su taru a kan uwar garken

Puppeteer tare da proxy na SOCKS5

Chrome na iya amfani da proxy na SOCKS5 (--proxy-server=socks5://IP:PORT) amma ba zai iya shiga ciki ba, kuma page.authenticate() ba ya aiki da SOCKS. Tare da proxy na ProxyV4 (ana ba da SOCKS5 a wajen Vietnam; IP na Vietnam na HTTP ne kawai) kana da zabuka biyu masu kyau: sauya odar zuwa HTTP ko yanayin dual sannan ka yi amfani da misalin da ke sama, ko kuma ka bar proxy-chain ya bude mai tura saƙo na gida mara kalmar sirri wanda zai shiga a madadinka:

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

Shiga ta hanyar whitelist na IP ita ce hanya ta uku: ƙara IP na jama'a na na'urar zuwa odar kuma Chrome zai haɗa ba tare da wani bayanin shiga ba.

Zabar adiresoshin IP don rukunin Puppeteer

Headless Chrome yana sauke cikakkun shafuka, rubutun lissafi da hotuna, don haka amfani da data mai iyaka yana taruwa da sauri. Keɓaɓɓun IPv4 da proxies na ISP na tsaye na ProxyV4 ba su da iyakancewar bandwidth, kowane IP yana yi wa abokin ciniki guda daya kawai aiki, kuma sabuntawa yana riƙe adireshi guda, wanda ke da muhimmanci lokacin da zama ko allow-list ya danganta da shi. Kwatanta samfurin keɓaɓɓen IPv4 da samfurin ISP na tsaye idan shafin da aka nufa yana duba kewayon datacenter daban.

Mataki bayan mataki

  1. 1

    Fara Chrome tare da adireshin proxy

    Fara burawzar tare da const browser = await puppeteer.launch({ args: ['--proxy-server=http://ip:port'] });, ta amfani da IP da port daga odarka ta ProxyV4.

  2. 2

    Tantance shafin

    Bude shafi tare da const page = await browser.newPage(); sannan ka kira await page.authenticate({ username: 'USER', password: 'PASS' }); kafin kowane kewaya.

  3. 3

    Karanta IP na fita

    Kewaya tare da await page.goto('https://proxyv4.com/api/my-ip'); sannan ka duba cewa amsar tana nuna adireshin proxy.

  4. 4

    Rufe burawzar

    Kammala tare da await browser.close(); domin kada wani aikin Chrome ya ci gaba da gudana.

Tambayoyi da aka fi yi

Me ke haifar da ERR_NO_SUPPORTED_PROXIES a Puppeteer?

Sanya bayanan shiga a cikin flag, kamar --proxy-server=http://user:pass@ip:port. Yi amfani da --proxy-server=http://ip:port sannan ka tura sunan mai amfani da kalmar sirri ta hanyar page.authenticate().

Shafina na farko yana aiki amma sabon shafi yana samun HTTP 407. Me ya sa?

Ana adana tabbatarwar shiga ne ga kowane shafi daban. Kira await newTab.authenticate({ username, password }) a kowane shafin da ka bude kafin ya loda.

Shin burauzar Puppeteer guda daya za ta iya amfani da proxies da yawa a lokaci guda?

Ba ta hanyar flag din kaddamarwa kadai ba. Yi amfani da proxy-chain don mayar da kowane proxy mai bayanan shiga zuwa adireshi na gida sannan ka ba kowane mahallin burauza nata proxyServer, ko kuma ka bude burauza guda daya ga kowane proxy.

Ta yaya zan gwada proxies da yawa kafin in saka su a Puppeteer?

Manna su a cikin proxy checker; yana duba har zuwa 100 a lokaci guda kuma ba ya adana kalmomin sirri.

Me ya sa page.authenticate() ba ya aiki da proxy na na SOCKS5?

Chrome ba ya goyon bayan shiga da sunan mai amfani da kalmar sirri don SOCKS5, don haka babu abin da Puppeteer zai amsa. Yi amfani da yanayin HTTP na odar, mai tura saƙo na gida daga proxy-chain, ko kuma shiga ta hanyar whitelist na IP.

Tushe

IP marasa iyaka don headless Chrome

Keɓaɓɓen IPv4 a ƙasashe 7 tare da tsayayyen ISP a US da Vietnam, wanda ake bayarwa kai tsaye bayan biya, abokin ciniki ɗaya ga kowane IP.

Duba farashin US na yanzu

Related articles

Furoksi ta manhaja
Proxies don web scraping: kafaffen rukunin IP tare da zirga-zirgar bayanai marar iyaka
Proxies na web scraping don Python, Scrapy, Playwright da Selenium: rukunin keɓaɓɓen IPv4 da static ISP, bandwidth marar iyaka, kafaffen farashin kowace IP.
Saitin furoksi
Tabbatar da Playwright proxy, tsayayyen IP guda daya ga kowane context
Ba kowane Playwright browser context nasa proxy na HTTP(S) mai tabbatarwa a Node.js ko Python, daidaita lokaci da yare da IP, sannan ka duba adireshin fita.
Saitin furoksi
Proxies masu shaidar shiga a Node.js: Axios, native fetch da Got
Tura buƙatun Node.js da TypeScript ta hanyar proxy na HTTP(S) mai tantancewa: https-proxy-agent don Axios, undici ProxyAgent don fetch, hpagent don Got.
Kayan aiki na kyauta
Sake rubuta jerin proxy zuwa tsarin da kayan aikinku ke buƙata
Sauya jerin proxy a burawzarku tsakanin ip:port:user:pass, user:pass@ip:port, http:// URLs, SOCKS5 URIs, arrays na JSON da fayilolin FoxyProxy a dunkule.
Furoksi ta manhaja
Wakilai don bin diddigin matsayin SEO: ga shafin sakamako kamar yadda mai bincike na asali yake gani
Wakilan SEO masu zaman kansu na IPv4 a Amurka, Birtaniya da sauran kasuwanni, domin matsayi da tallace-tallace su zama daidai da abin da 'yan gari ke gani.
Furoksi ta manhaja
Furoksi don YouTube: hana matsalar tasha ɗaya shafar sauran tashoshi
Furoksin YouTube na masu tashoshi da yawa da ƙungiyoyi: tsayayyen ISP ko IPv4 ɗaya ga kowace tasha, don dakatarwa ko goge tasha ɗaya ya tsaya a kanta kawai.
IPV4 · united states
Rukunin Keɓaɓɓun IPv4 Proxy na Amurka domin Scraping, Bibiyar Matsayi da Duba Talla
Sayi US private IPv4 proxy: tsayayyun IP na datacenter na US, mutum ɗaya kowace IP, bandwidth marar iyaka. Don scraping, bin SERP da duba tallan Amurka.
IPV4 · singapore
Keɓaɓɓen IPv4 Proxy na Singapore: Kafaffen IP Guda Ɗaya ga Kowanne Shago da Asusun Talla
Private IPv4 proxy na Singapore: tsayayyen IP na cibiyar bayanai ta SG don kai kadai, don shagunan Lazada da Shopee SG, asusun talla da sarrafa aiki.