A bayan ERR_TUNNEL_CONNECTION_FAILED: karanta amsar CONNECT ta proxy
Updated:
ERR_TUNNEL_CONNECTION_FAILED yana bayyana ne lokacin da Chrome ta nemi proxy ya buɗe rami (tunnel) don shafin https:// amma proxy ɗin ya ƙi. Chrome na tura buƙatar CONNECT, tana tsammanin izini, amma sai ta sami lambar kuskure a maimakon haka. Matsalar ita ce Chrome na ɓoye wannan lambar, don haka babban aikinka na farko shi ne gano ainihin lambar kuskuren.
Mafi yawan abubuwan da ke haddasa matsalar, a jere
- Wani rubutun aiki (script) ya buɗe Chrome ba tare da bayanan shiga ba. Alamar
--proxy-servertana ɗaukar host da port kaɗai; duk wani user:pass da ka saka a ciki ana watsar da shi ne. Sannan Puppeteer ko Selenium a yanayin headless yana karɓar 407 kuma ya bayar da rahotonsa a matsayin matsalar tunnel. - Wata manhaja a bayan proxy na Wi-Fi da ke buƙatar kalmar sirri. Manhajoji ba su da wurin shigar da bayanan shiga, don haka buƙatunsu na HTTPS kan fuskanci matsala duk da cewa mashigar intanet ta wayar tana aiki.
- Proxy ɗin ba zai iya isa ga shafin da ake nema ba. Yana amsa CONNECT da 502. Shafin 502 Bad Gateway ya ƙunshi ƙarin bayani kan wannan matsalar.
- Wasu takamaiman shafuka ne kawai ke fuskantar matsala. Shafin da ake nema ba ya aiki ko kuma ya ƙi karɓar buƙatar, alhali kuwa wannan proxy ɗin yana buɗe sauran shafuka ba tare da wata matsala ba.
Abin da muka gani a yayin gwaji
Mun gwada duka yanayin guda biyu da aka saba gani a kan proxy na gwaji, wanda aka rubuta a ƙasa a matsayin 203.0.113.10:8080 tare da bayanan shiga na user123:pass456. A kowane layi Chrome ta nuna saƙo iri ɗaya, shi ya sa ba ta nuna cikakken bayani da kanta ba.
| Amsar da proxy ya bayar ga CONNECT | Chrome | curl |
|---|---|---|
407, kuma babu damar shigar da kalmar sirri (headless Chrome) | ERR_TUNNEL_CONNECTION_FAILED | curl: (56) CONNECT tunnel failed, response 407 |
502, proxy ɗin ya kasa isa ga shafin | ERR_TUNNEL_CONNECTION_FAILED | curl: (56) CONNECT tunnel failed, response 502 |
Gano ɓoyayyar lambar kuskuren
Yi amfani da curl -v -x http://user123:[email protected]:8080 https://example.com tare da bayanan proxy ɗinka sannan ka karanta amsar da ke biyo bayan > CONNECT example.com:443 HTTP/1.1. Lambar 407 tana tura ka zuwa jagorar 407. Lambar 502 kuwa tana nuni ne ga shafin da ake nema ko kuma hanyar da ke gaba da proxy.
Ba ka son buɗe terminal? Kayan aikin proxy checker yana bayar da rahoton yanayi biyun a matsayin auth failed (407) da HTTP 502.
Lura cewa Chrome na yau da kullum mai bayyana a fili tana kula da 407 daban: tana nuna akwatin shigar da sunan mai amfani da kalmar sirri ta proxy maimakon kuskuren tunnel. Wannan ne ya sa kuskuren tunnel mai nasaba da 407 ya fi fitowa a aikin automation da kuma a manhajojin da ba za su iya nuna akwatin shiga ba.
Hanyoyin magance matsala ga kowane muhalli
- Puppeteer: buɗe tare da
--proxy-server=http://host:port, sannan ka kirapage.authenticate({ username, password })kafin buɗe shafi na farko. Cikakken misali yana cikin jagorar proxy ta Puppeteer. - Playwright: saka
proxy: { server, username, password }a cikin zaɓuɓɓukan buɗewa; Playwright da kanta take amsa 407. Duba tsarin Playwright. - Selenium: Chrome ba za ta karɓi user:pass a layin umarninta ba. Jagorar Selenium tana lissafa hanyoyin da ke aiki.
- Desktop Chrome a kan Windows: idan akwatin shiga bai taɓa bayyana ba, wata manhaja ta ƙarin aiki (extension) na iya zama tana toshe shi. Sake gwadawa a tagar da aka kashe extensions a cikinta.
- Wayoyin salula: manhajojin da ke buƙatar proxy mai tabbatar da asali suna aiki mafi kyau ta hanyar manhajar proxy da ke goyon bayan user:pass, kamar yadda aka bayyana a jagorar tsarin Android.
Mataki bayan mataki
- 1
Gano abin da proxy ya amsa
Yi amfani da
curl -v -xtare da layin proxy ɗinka, ko mai duba proxy, don ganin ko amsar CONNECT 407 ce ko 502. - 2
407: shigar da bayanan shiga daidai
A tsarin automation, yi amfani da fasalin tabbatar da asali na dakin karatu (library) maimakon saka user:pass a cikin
--proxy-server. - 3
502: gwada wani shafin daban
Buɗe babban shafi mai karko kamar example.com ta wannan proxy ɗin. Idan ya buɗe, shafin farko ne ke da matsalar.
- 4
Tabbatar da IP na fita
Lokacin da tunnel ya buɗe, buɗe IP dina a wannan mashigar intanet ɗin don duba ko zirga-zirgar bayanan tana fita ta hanyar proxy da gaske.
Tambayoyi da aka fi yi
Me ya sa shafukan http:// ke aiki alhali shafukan https:// suna fuskantar matsala?
Ana tura buƙatun HTTP na asali kai tsaye ba tare da buƙatar CONNECT ba. HTTPS kaɗai ke neman buɗe tunnel, don haka kuskuren tunnel zai iya faruwa ne kawai a shafukan HTTPS.
Me ke haifar da ERR_TUNNEL_CONNECTION_FAILED a Android?
Yawanci wata manhaja ce da ba za ta iya tura sunan mai amfani da kalmar sirri zuwa ga proxy na Wi-Fi ba. Buɗe wannan shafin a Chrome don Android: idan Chrome ta nuna akwatin shigarwa kuma ta buɗe shi, manhajar ce ke da matsala.
Shin za a iya saka bayanan shiga a cikin --proxy-server?
A'a. Chrome tana watsar da su ne, sai proxy ya amsa da 407 kuma ka sami kuskuren tunnel. Maimakon haka, tabbatar da asali ta hanyar Puppeteer, Playwright ko extension.
Wanne nau'in proxy ya kamata in zaɓa don kauce wa wannan?
Daidaita nau'in da oda da ka yi: zaɓi HTTP a kayan aikinka don odar HTTP ko dual-mode (kuskuren tunnel yana fitowa ne kawai da HTTP), ko SOCKS5 don odar SOCKS5, sannan ka shigar da bayanan shiga ta saitunan tabbatar da asali na kayan aikin.
An kera shi don rubutun aiki na automation
ProxyV4 proxies suna amfani da sauƙaƙan tabbatar da asali na user:pass wanda Puppeteer da Playwright ke karɓa ba tare da dabarun gyara ba.
Duba farashin yanzu