Gyara matsalar ERR_TUNNEL_CONNECTION_FAILED tare da proxy

Yanayi biyu da muka sake gwadawa

Dukansu an gwada su ne akan proxy na gwaji, wanda aka sake rubutawa anan da adireshin bayani 203.0.113.10:8080 da user123:pass456. A cikin taga na al'ada na Chrome, yanayin 407 ba ya zama kuskuren rami; a maimakon haka Chrome tana bude akwatin shiga don neman sunan mai amfani da kalmar sirri na proxy. Don haka, kuskuren rami da 407 ke haifarwa yana bayyana ne musamman a kayan aikin sarrafa kansa da kuma manhajojin da ba za su iya neman kalmar sirri ba.

Dalilai, daga wanda aka fi tsammani

• Rubutun sarrafa kansa bai tura bayanan shiga ba. Tutar --proxy-server ta Chrome tana karbar host da port ne kawai, ba user:pass ba. Puppeteer ko Selenium maras fuska (headless) na samun 407 kuma su bayar da rahoton gazawar rami.
• Manhajar waya a bayan proxy na Wi-Fi mai kariya da kalmar sirri. Manhajar ba ta da akwatin shiga, don haka HTTPS tana daina aiki alhali burawza na ci gaba da aiki.
• Proxy ba za ta iya isa ga abin da ake nema ba. Tana mayar da 502 ga CONNECT; shafin 502 Bad Gateway ya yi cikakken bayani a kan wannan.
• Wasu shafukan ne kawai ke faduwa. Wurin da ake son zuwa yana toshewa ko kuma ya fadi, yayin da sauran shafuka ke aiki ta hanyar wannan proxy din.

Gano ainihin lambar da umarnin curl guda daya

Gudanar da curl -v -x http://user123:[email protected]:8080 https://example.com tare da bayananka na kanka. Duba layin da ke daidai bayan > CONNECT example.com:443 HTTP/1.1: 407 na nufin bin jagorar 407; 502 kuma na nuna cewa matsalar tana wajen da ake son zuwa ne ko kuma hanyar da ke bayan proxy. Idan ka fi son kada ka yi amfani da terminal, manna layin a cikin proxy checker, wanda ke bayar da rahoton auth failed (407) ko HTTP 502 don irin wadannan yanayi.

Hanyoyin gyara dangane da muhallin aiki

• Puppeteer: a ci gaba da amfani da --proxy-server=http://host:port yayin farawa sannan a kira page.authenticate({ username, password }) kafin shiga shafi. Cikakken misali yana cikin jagorar proxy ta Puppeteer.
• Playwright: shigar da proxy: { server, username, password } lokacin kaddamar da burawza kuma Playwright zai amsa 407 a madadinka; duba Playwright.
• Selenium: Chrome ba ya karbar user:pass a layin umarni; jagorar Selenium tana nuna hanyoyin da za su yi aiki.
• Chrome on Windows: idan akwatin shiga bai taba bayyana ba, duba ko akwai kari (extension) na proxy da ke hana shi bayyana, sannan ka sake gwadawa a taga mara kari.
• Wayoyi: ga manhajojin da ke bukatar proxy mai tantancewa, yi amfani da manhajar proxy mai goyon bayan user:pass kamar yadda yake a cikin jagorar saitin Android.

Mataki-mataki

1. 1

   Gano amsar CONNECT

   Gudanar da curl -v -x tare da layin proxy dinka, ko kuma ka manna shi a cikin na'urar dubawa, domin sanin ko proxy ta mayar da 407 ko 502.

2. 2

   Ga 407: shigar da bayanan shiga yadda ya dace

   A cikin scripts, yi amfani da hanyar tantancewa ta library maimakon sanya user:pass a cikin --proxy-server.

3. 3

   Ga 502: gwada wani shafin daban

   Loda babban shafi kamar example.com ta hanyar wannan proxy din. Idan ya yi aiki, ainihin shafin da aka nufa ne ke da matsala.

4. 4

   Sake gwadawa da tabbatar da IP na fita

   Da zarar ramin ya bude, ziyarci my IP a cikin wannan burawzar domin tabbatar da cewa hanyar sadarwa na bi ta proxy.

Tambayoyin da aka fi yi