Xallinta ERR_TUNNEL_CONNECTION_FAILED marka la isticmaalayo borogisi
Updated:
Si aad bog https:// ah ugu furto borogisi, biraawsarku wuxuu diraa codsi CONNECT wuxuuna sugayaa in borogisigu u furo tunnel xagga bogga ah. ERR_TUNNEL_CONNECTION_FAILED waxay soo baxdaa marka borogisigu kaga jawaabo codsigaas qalad halkii uu ka aqbali lahaa. Dhibaatadu waxay tahay in Chrome uusan kuu sheegin qaladka uu yahay, marka howsha ugu horreysa waa helidda koodka dhabta ah.
Laba xaaladood oo aan tijaabinnay
Labaduba waxay ku shaqeeyeen borogisi tijaabo ah, oo halkan loogu qoray ciwaanka dukumeentiga ah ee 203.0.113.10:8080 iyo user123:pass456. Daaqad caadi ah oo Chrome ah, xaaladda 407 ma noqoto qalad tunnel; beddelkeeda Chrome wuxuu furayaa sanduuq lagu galo magaca isticmaalaha iyo furaha sirta ah ee borogisiga. Qaladaadka tunnel-ka ee ka dhasha 407 sidaas darteed waxay u badan yihiin aaladaha shaqada tooska u qabta (automation) iyo abriyada aan codsan karin furaha sirta ah.
| Borogisigu wuxuu CONNECT kaga jawaabayaa | Chrome wuxuu muujinayaa | curl wuxuu muujinayaa |
|---|---|---|
407 iyadoo aysan jirin hab loo geliyo furaha sirta ah (headless Chrome) | ERR_TUNNEL_CONNECTION_FAILED | curl: (56) CONNECT tunnel failed, response 407 |
502 sababtoo ah borogisigu ma gaari karo bogga | ERR_TUNNEL_CONNECTION_FAILED | curl: (56) CONNECT tunnel failed, response 502 |
Sababaha, laga bilaabo kuwa ugu badan
- Qoraal shaqo toos ah (automation script) oo aan dirin xogta gelitaanka. Calaamadda
--proxy-serveree Chrome waxay aqbashaa kaliya host iyo port, ma aqbasho user:pass. Puppeteer ama Selenium oo ah headless waxay helayaan 407 waxayna soo sheegayaan fashilka tunnel-ka. - App taleefan oo ku dhex jira borogisi Wi-Fi oo furaha sirta ah laga rabo. App-ku ma laha sanduuq gelitaan, sidaas darteed HTTPS way go'aysaa iyadoo biraawsarku wali shaqeynayo.
- Borogisigu ma gaari karo bartilmaameedka. Wuxuu kaga jawaabayaa 502 codsiga CONNECT; bogga 502 Bad Gateway ayaa arrintan si qoto dheer uga hadlaya.
- Kaliya qaar ka mid ah boggaga ayaa shaqeyn waayay. Meesha la rabo ayaa xannibaysa ama hawada ka maqan iyadoo boggaga kale ay ka shaqeynayaan isla borogisiga.
Ku hel koodka dhabta ah hal amar oo curl ah
Ku socodsii curl -v -x http://user123:[email protected]:8080 https://example.com xogtaada gaarka ah. Fiiri xariiqda ku xigta > CONNECT example.com:443 HTTP/1.1: 407 waxay la macno tahay inaad raacdo tilmaamaha 407; 502 waxay farta ku fiiqaysaa meesha la rabo ama dariiqa ka dambeeya borogisiga. Haddii aadan rabin inaad isticmaasho terminal, xariiqda ku dheji hubiyaha borogisiga, kaasoo soo sheegaya auth failed (407) ama HTTP 502 isla xaaladahaas oo kale.
Xalka sida ay deegaannadu u kala duwan yihiin
- Puppeteer: ku hay
--proxy-server=http://host:portmarka la bilaabayo oo wacpage.authenticate({ username, password })ka hor inta aanad bogga furin. Tusaale buuxa wuxuu ku jiraa tilmaamaha borogisiga Puppeteer. - Playwright: sii
proxy: { server, username, password }marka aad bilaabayso biraawsarka, Playwright ayaana 407 kaaga jawaabaya; eeg Playwright. - Selenium: Chrome ma aqbalo user:pass xagga khadka amarka (command line); tilmaamaha Selenium ayaa muujinaya xulashooyin shaqeynaya.
- Chrome ee Windows: haddii sanduuqa gelitaanku uusan waligiis soo bixin, hubi haddii kordhinta borogisiga (proxy extension) ay xannibayso, ka dibna dib isku day adigoo isticmaalaya daaqad aan lahayn kordhinno.
- Taleefannada: abriyada u baahan borogisi leh xaqiijin (authenticated), isticmaal app borogisi oo taageera user:pass sida ku cad tilmaamaha habaynta Android.
Tallaabo-tallaabo
- 1
Aqoonso jawaabta CONNECT
Ku socodsii
curl -v -xxariiqda borogisigaaga, ama ku dheji hubiyaha, si aad u ogaato haddii borogisigu soo celiyo 407 ama 502. - 2
Wixii ku saabsan 407: geli xogta gelitaanka si sax ah
Qoraallada (scripts), isticmaal habka xaqiijinta ee laybreeriga halkii aad user:pass gelin lahayd
--proxy-server. - 3
Wixii ku saabsan 502: tijaabi bog kale
Ka fur bog weyn sida example.com isla borogisigaas. Haddii uu shaqeeyo, dhibaatadu waxay ka jirtaa bartilmaameedkii hore.
- 4
Dib u socodsii oo xaqiiji IP-ga bixitaanka
Marka tunnel-ku furmo, booqo IP-gayga isla biraawsarkaas si aad u xaqiijiso in taraafikadu marto borogisiga.
Su'aalaha inta badan la isweydiiyo
Maxay boggaga http u furmaan halka boggaga https ay shaqeyn waayaan?
http caadiga ah uma baahna CONNECT; borogisigu si toos ah ayuu codsiga u gudbiyaa. Kaliya https ayaa fura tunnel, sidaas darteed qaladaadka tunnel-ku halkaas kaliya ayay ka muuqdaan.
Maxaa keena ERR_TUNNEL_CONNECTION_FAILED xagga Android?
Badanaa waa app aan gudbin karin magaca isticmaalaha iyo furaha sirta ah ee borogisiga Wi-Fi-ga. Isla boggaas ku tijaabi Chrome ee Android; haddii Chrome uu codsan karo oo uu furi karo, dhibaatadu waxay ka jirtaa app-ka.
Ma gelin karaa user:pass gudaha --proxy-server?
Maya. Chrome wuxuu iska indhatiraa xogta gelitaanka ee ku dhex jirta calaamaddaas, taasoo keenta 407 iyo qaladka tunnel-ka. Beddelkeeda ku xaqiiji Puppeteer, Playwright ama kordhin (extension).
U wareejinta SOCKS5 ma meesha ka saaraysaa qaladka tunnel-ka?
Kaliya haddii dalabkaagu yahay SOCKS5. VinaProxy wuxuu bixiyaa labadaba HTTP(S) iyo SOCKS5; dooro borotokoalka uu dalabkaagu ku muujinayo dashboard-ka, maadaama is-waafajin la'aantu ay keento qaladaad kale.
Borogisiyo la shaqeeya Puppeteer iyo Playwright
Borogisiyada VinaProxy waxay isticmaalaan gelitaan caadi ah oo user:pass ah kaas oo laybreeriyada caanka ah ee shaqada tooska ah si toos ah u maareeyaan.
Fiiri qiimaha