Ngemuva kwe-ERR_TUNNEL_CONNECTION_FAILED: ukufunda impendulo ye-CONNECT ye-proxy
Updated:
I-ERR_TUNNEL_CONNECTION_FAILED ivela lapho i-Chrome icela i-proxy ukuthi ivule umhubhe wekhasi le-https:// bese i-proxy yenqaba. I-Chrome ithumela isicelo se-CONNECT, ilindele imvume, kodwa ithole isimo sephutha esikhundleni salokho. Inkinga ukuthi i-Chrome iyasifihla leso simo, ngakho-ke umsebenzi wakho wokuqala ukuthola ikhodi yangempela.
Izimbangela ezingaba khona, ngokulandelana
- Iskripthi sivula i-Chrome ngaphandle kwemininingwane yokungena. Ifulegi le-
--proxy-serverliphatha i-host nembobo kuphela; noma iyiphi i-user:pass oyifaka lapho iyalahlwa. I-Puppeteer noma i-Selenium kumodi ye-headless ibe isithola i-407 bese iyibika njengokuhluleka komhubhe. - Uhlelo lokusebenza olungemuva kwe-proxy ye-Wi-Fi edinga iphasiwedi. Izinhlelo zokusebenza azinaso isikrini sokungena, ngakho-ke izicelo zazo ze-HTTPS ziyehluleka ngisho noma isiphequluli sefoni sisebenza.
- I-proxy ayikwazi ukufinyelela lapho iya khona. Iphendula i-CONNECT ngo-502. Ikhasi le-502 Bad Gateway lichaza kabanzi ngalesi simo.
- Yizingosi ezithile kuphela ezihlulekayo. Indawo okuyiwa kuyo ayisebenzi noma iyanqaba, kuyilapho yona leyo proxy ivula ezinye izingosi ngaphandle kwenkinga.
Esikubonile ekuhloleni
Senze zombili izimo ezivamile ku-proxy yokuhlola, ebhalwe kabusha ngezansi njenge-203.0.113.10:8080 enokungena okungu-user123:pass456. Emgqeni ngamunye i-Chrome ibonise umlayezo ofanayo, yingakho ikutshela okuncane kakhulu iyodwa.
| Impendulo ye-proxy ku-CONNECT | Chrome | curl |
|---|---|---|
407, futhi ayikho indlela yokuthayipha iphasiwedi (i-headless Chrome) | ERR_TUNNEL_CONNECTION_FAILED | curl: (56) CONNECT tunnel failed, response 407 |
502, i-proxy ayikwazanga ukufinyelela kusayithi | ERR_TUNNEL_CONNECTION_FAILED | curl: (56) CONNECT tunnel failed, response 502 |
Thola ikhodi yesimo efihliwe
Sebenzisa i-curl -v -x http://user123:[email protected]:8080 https://example.com ngamanani akho e-proxy bese ufunda impendulo elandela i-> CONNECT example.com:443 HTTP/1.1. I-407 ikuthumela kumhlahlandlela we-407. I-502 ikhomba endaweni okuyiwa kuyo noma emzileni ongaphesheya kwe-proxy.
Ukhetha ukungavuli itheminali? I-proxy checker ibika izimo ezimbili ezifanayo njenge-auth failed (407) kanye ne-HTTP 502.
Qaphela ukuthi iwindi le-Chrome elivamile, elibonakalayo liphatha i-407 ngendlela ehlukile: libonisa ibhokisi lokungena le-username nephasiwedi ye-proxy esikhundleni sephutha lomhubhe. Yingakho amaphutha omhubhe abangelwa yi-407 evela kakhulu ekuzisebenzeleni nasezinhlelweni zokusebenza ezingakwazi ukukwazisa.
Izixazululo zendawo ngayinye yokusebenza
- Puppeteer: qala nge-
--proxy-server=http://host:port, bese ubiza i-page.authenticate({ username, password })ngaphambi kokuzulazula kokuqala. Isibonelo esigcwele sisesiqondisweni se-Puppeteer proxy. - Playwright: faka i-
proxy: { server, username, password }ezinkethweni zokuqala; i-Playwright iphendula i-407 ngokwayo. Bheka ukusetha kwe-Playwright. - Selenium: I-Chrome ngeke yamukele i-user:pass kulayini wayo womyalo. Umhlahlandlela we-Selenium ubala izindlela ezisebenzayo.
- Desktop Chrome ku-Windows: lapho ibhokisi lokungena lingaveli nhlobo, isandiso kungenzeka siyayivimba. Zama futhi ewindini elinezandiso ezikhutshaziwe.
- Izingcingo: izinhlelo zokusebenza ezidinga i-proxy egunyaziwe zisebenza kangcono kakhulu ngohlelo lokusebenza lwe-proxy olusekela i-user:pass, njengoba kuchazwe kumhlahlandlela wokusetha i-Android.
Isinyathelo ngesinyathelo
- 1
Thola ukuthi i-proxy iphendule ntoni
Sebenzisa i-
curl -v -xngomugqa wakho we-proxy, noma i-checker, ukuze ubone ukuthi impendulo ku-CONNECT ngu-407 noma ngu-502. - 2
407: faka imininingwane yokungena ngendlela efanele
Ekuzisebenzeleni, sebenzisa isici sokuqinisekisa selabhulali kunokufaka i-user:pass ngaphakathi kwe-
--proxy-server. - 3
502: hlola indawo ehlukile okuyiwa kuyo
Vula isayithi enkulu, ezinzile efana ne-example.com usebenzisa yona leyo proxy. Uma ilayisha, inkinga ikusayithi yasekuqaleni.
- 4
Qinisekisa i-IP yokuphuma
Lapho umhubhe uvuleka, layisha i-IP yami kuleso siphequluli esifanayo ukuze uhlole ukuthi ithrafikhi iphuma ngempela nge-proxy.
Imibuzo evame ukubuzwa
Kungani amakhasi e-http:// esebenza kanti amakhasi e-https:// ayehluleka?
Izicelo ezijwayelekile ze-HTTP zidluliselwa ngqo futhi azidingi i-CONNECT. I-HTTPS kuphela ecela umhubhe, ngakho-ke iphutha lomhubhe lingenzeka kuphela emakhasini e-HTTPS.
Yini ebangela i-ERR_TUNNEL_CONNECTION_FAILED ku-Android?
Ngokuvamile uhlelo lokusebenza olungakwazi ukuthumela i-username nephasiwedi ku-proxy ye-Wi-Fi. Vula lelo khasi elifanayo ku-Chrome ye-Android: uma i-Chrome ikucela imininingwane bese ililayisha, uhlelo lokusebenza yilo oluhlulekayo.
Ingabe imininingwane yokungena ingafakwa ngaphakathi kwe---proxy-server?
Cha. I-Chrome iyayilahla, i-proxy iphendule ngo-407 bese uthola iphutha lomhubhe. Qinisekisa usebenzisa i-Puppeteer, i-Playwright noma isandiso esikhundleni salokho.
Yiluphi uhlobo lwe-proxy okufanele ngilukhethe ukugwema lokhu?
Qondanisa uhlobo ne-oda lakho: khetha i-HTTP ethuluzini lakho nge-oda le-HTTP noma le-dual-mode (iphutha lomhubhe livela kuphela nge-HTTP), noma i-SOCKS5 nge-oda le-SOCKS5, bese unikezela ngokungena ngezilungiselelo zokuqinisekisa zethuluzi.
Yenzelwe izikripthi zokuzisebenzela
Ama-proxy e-ProxyV4 asebenzisa ukuqinisekiswa okuvamile kwe-user:pass okwamukelwa yi-Puppeteer ne-Playwright ngaphandle kwezindlela zokugwema.
Bona amanani abukhoma