Gudaha ERR_TUNNEL_CONNECTION_FAILED: akhrinta jawaabta CONNECT ee proxy-ga
Updated:
ERR_TUNNEL_CONNECTION_FAILED waxay soo baxdaa marka Chrome uu ka codsado proxy inuu furo tunnel bog https:// ah oo proxy-guna uu diido. Chrome wuxuu diraa codsi CONNECT, isagoo filaya oggolaansho, balse taa beddelkeeda wuxuu helaa xaalad qalad ah. Dhibaatadu waxay tahay in Chrome uu qariyo heerkaas qaladka, markaa hawshaada koowaad waa inaad soo ceshato koodhka dhabta ah.
Sababaha ugu macquulsan, sida ay u kala horreeyaan
- Qoraal-fulineed oo fura Chrome bilaa xogta gelitaanka. Calanka
--proxy-serverwuxuu qaadaa oo keliya host iyo port; user:pass kasta oo aad halkaas geliso waa laga tagaa. Puppeteer ama Selenium oo ku jira habka headless ayaa markaas hela 407 una soo tebiya sidii cillad tunnel. - App ka dambeeya Wi-Fi proxy u baahan furaha sirta ah. App-yadu ma laha daaqad login, sidaas darteed codsiyadooda HTTPS way fashilmaan inkasta oo biraawsarka taleefanku shaqeynayo.
- Proxy-gu ma gaari karo meesha loo socdo. Wuxuu CONNECT kaga jawaabayaa 502. Bogga 502 Bad Gateway page ayaa si qoto dheer u sharxaya xaaladdaas.
- Keliya bogag gaar ah ayaa fashilmaya. Meesha loo socdo ayaa maqan ama diidaya, iyadoo isla proxy-gaas uu bogagga kale u furayo dhib la'aan.
Wixii aan aragnay intii lagu jiray tijaabada
Waxaan ku kicinay labada xaaladood ee caadiga ah proxy tijaabo, kaas oo hoos loogu qoray sidii 203.0.113.10:8080 oo wata galitaanka user123:pass456. Saf kasta Chrome wuxuu soo bandhigay isla fariinta, waana sababta ay fariintani wax yar uun kaligeed kuu sheegto.
| Jawaabta proxy-ga ee CONNECT | Chrome | curl |
|---|---|---|
407, iyo hab la'aan lagu qoro furaha sirta ah (headless Chrome) | ERR_TUNNEL_CONNECTION_FAILED | curl: (56) CONNECT tunnel failed, response 407 |
502, proxy-gu ma gaari karin bogga | ERR_TUNNEL_CONNECTION_FAILED | curl: (56) CONNECT tunnel failed, response 502 |
Soo celi koodhka heerka ee qarsoon
Ku socodsii curl -v -x http://user123:[email protected]:8080 https://example.com qiimayaashaada proxy oo akhri jawaabta ka dambaysa > CONNECT example.com:443 HTTP/1.1. 407 waxay kuu wareejinaysaa 407 guide. 502 waxay tilmaamaysaa meesha loo socdo ama dariiqa ka shisheeya proxy-ga.
Ma doonaysid inaad furto terminal? proxy checker wuxuu soo tebinayaa labada xaaladood ee isku midka ah sidii auth failed (407) iyo HTTP 502.
Ogow in daaqadda Chrome ee caadiga ah ee muuqata ay 407 u maarayso si ka duwan: waxay soo bandhigaysaa sanduuqa gelitaanka ee magaca isticmaalaha iyo furaha sirta ah ee proxy-ga halkii ay ka bixin lahayd qaladka tunnel-ka. Taasi waa sababta khaladaadka tunnel-ka ee 407 ay inta badan uga soo baxaan otomaatigga iyo app-yada aan soo bandhigi karin codsiga gelitaanka.
Xalalka deegaan kasta
- Puppeteer: ku fur
--proxy-server=http://host:port, ka dibna wacpage.authenticate({ username, password })ka hor inta aanad gelin bogga koowaad. Tusaale buuxa wuxuu ku jiraa Puppeteer proxy guide. - Playwright: geli
proxy: { server, username, password }xulashooyinka furitaanka; Playwright ayaa kaligii ka jawaabaya 407. Eeg Playwright setup. - Selenium: Chrome ma aqbali doono user:pass xariiqdiisa amarka. Selenium guide wuxuu taxayaa hababka shaqeeya.
- Desktop Chrome ee Windows: marka sanduuqa gelitaanku uusan marnaba soo bixin, kordhin ayaa laga yaabaa inay xannibayso. Mar kale isku day daaqad ay kordhinnadu dansan yihiin.
- Taleefannada: app-yada u baahan proxy la xaqiijiyay waxay si fiican ugu shaqeeyaan app proxy oo taageera user:pass, sida lagu sharraxay Android setup guide.
Tallaabo tallaabo
- 1
Soo ogow waxa proxy-gu ku jawaabay
Isticmaal
curl -v -xoo ay la socoto xariiqdaada proxy, ama hubiyaha, si aad u aragto haddii jawaabta CONNECT ay tahay 407 ama 502. - 2
407: si sax ah u gudbi xogta gelitaanka
Otomaatigga dhexdiisa, isticmaal habka xaqiijinta ee maktabadda halkii aad user:pass gelin lahayd gudaha
--proxy-server. - 3
502: tijaabi meel kale oo loo socdo
Fur bog weyn oo deggan sida example.com adoo adeegsanaya isla proxy-ga. Haddii uu furmo, bogga asalka ah ayaa dhibaatadu tahay.
- 4
Xaqiiji IP-ga bixidda
Marka uu tunnel-ku furmo, ku fur my IP isla biraawsarkaas si aad u hubiso in xogtu ay dhab ahaan u mareyso proxy-ga.
Su'aalaha badanaa la isweydiiyo
Maxay bogagga http:// u shaqeeyaan halka bogagga https:// ay u fashilmaan?
Codsiyada tooska ah ee HTTP si toos ah ayaa loo gudbiyaa umana baahna CONNECT. Keliya HTTPS ayaa codsada tunnel, sidaas darteed qaladka tunnel-ku wuxuu ka dhici karaa oo keliya bogagga HTTPS.
Maxaa keena ERR_TUNNEL_CONNECTION_FAILED gudaha Android?
Caadiyan waa app aan u diri karin magaca isticmaalaha iyo furaha sirta ah Wi-Fi proxy. Isla boggaas ka fur Chrome ee Android: haddii Chrome uu soo bandhigo weydiinta galitaanka oo uu furo bogga, app-ka ayaa ah kan fashilmay.
Xogta gelitaanka ma geli kartaa gudaha --proxy-server?
Maya. Chrome wuu iska tuuraa, proxy-guna wuxuu ku jawaabaa 407 waxaadna helaysaa qaladka tunnel-ka. Taas beddelkeeda ku xaqiiji Puppeteer, Playwright ama kordhin.
Noocee proxy ah ayaan doortaa si aan tan uga fogaado?
Waafaji nooca dalabkaaga: qalabkaaga dhexdiisa ka dooro HTTP dalabka HTTP ama dual-mode ah (qaladka tunnel-ku wuxuu ka soo muuqdaa oo keliya HTTP), ama SOCKS5 dalabka SOCKS5 ah, oo xogta gelitaanka ku bixi qaybta xaqiijinta ee qalabka.
Loo dhisay qoraallada otomaatigga ah
Proxy-yada ProxyV4 waxay isticmaalaan xaqiijin fudud oo user:pass ah taas oo Puppeteer iyo Playwright ay aqbalaan iyadoon habab kale loo marin.
Fiiri qiimaha tooska ah