Ta yaya za ka gano ainihin lambar kuskure da ke bayan ERR_TUNNEL_CONNECTION_FAILED?
Gudanar da: curl -v -x http://IP:PORT -U user:pass https://trang-bi-loi.com. Nemo layin da ya fara da "< HTTP/1.1" daidai bayan layin CONNECT. Lambar da ke wurin tana nuna abin da proxy ta mayar.
| Lamba bayan CONNECT | Ma'ana | Mafita |
|---|---|---|
| 200 Connection established | An yi nasarar buɗe tunnel | Matsalar tana cikin burauza: ƙarin kayan aiki (extensions), saiti, riga-kafin cutar kwamfuta (antivirus) |
| 407 | Sunan mai amfani ko kalmar sirri ba daidai ba ko babu su | Duba jagorar kuskuren 407 |
| 403 | Proxy ta ƙi amincewa da wannan makomar | An toshe tashar (port) ko sabis ɗin a ƙarƙashin ƙa'idar amfani |
| 502, 503 | Proxy ta kasa haɗawa da shafin | Duba shafin da ake son shiga, gwada wani shafin daban |
Me ya sa kuskuren ERR_TUNNEL_CONNECTION_FAILED ke faruwa?
Wannan kuskuren yana faruwa ne lokacin da proxy ya gaza kafa hanyar sadarwa (tunnel) zuwa shafin da aka nufa, yawanci saboda kuskuren bayanan sirri, zaɓar nau'in proxy da bai dace ba, ko kuma rashin samun damar shiga shafin da aka nufa.
- Bayanai na shiga ba daidai ba, amma burauzar ba ta nuna wurin shigar da bayanan ba sai ta nuna kuskuren tunnel a maimakon haka. Wannan kan faru ne idan an saita proxy ta hanyar layin umarni (command-line) ko a cikin manhajar sarrafa ayyuka kai tsaye (automation).
- Zaɓar ƙa'idar proxy da ba ta dace da yanayin proxy ɗin da ke aiki ba, kamar zaɓar SOCKS5 alhali proxy na aiki da HTTP, ko zaɓar HTTPS (TLS zuwa proxy) maimakon HTTP.
- Shafin da ake nema babu shi, an yi kuskuren rubuta sunan shafin (domain), ko kuma shafin ya daina aiki, don haka proxy ba za ta iya gano shi ko haɗawa da shi ba.
- Haɗawa da tashar (port) da aka toshe bisa ƙa'ida, kamar tashoshin imel na SMTP waɗanda aka saba toshewa don hana spam.
- Binciken HTTPS na manhajar riga-kafin cutar kwamfuta (antivirus) yana kawo cikas tsakanin burauza da proxy.
Yadda za a gyara
- Gudanar da umarnin curl na sama don gano ainihin lambar kuskuren.
- Lambar 407: sake shigar da sunan mai amfani da kalmar sirri daidai kamar yadda aka nuna a shafin sarrafawa, ba tare da ƙarin sarari ba.
- Gwada babban shafi kamar https://www.google.com ta hanyar proxy. Idan babban shafin ya buɗe amma shafin da kake nema bai buɗe ba, matsalar tana daga shafin da kake son shiga ne.
- Tabbatar cewa ƙa'idar proxy a cikin manhajarka ta dace da yanayin proxy ɗin da ke aiki a ƙarƙashin Orders (HTTP, SOCKS5, ko HTTP + SOCKS5).
- Kashe fasalin binciken HTTPS na ɗan lokaci (Web Shield, binciken SSL) a cikin manhajarka ta riga-kafin cutar kwamfuta don gwadawa.
- Rufe burauzar gaba ɗaya sannan ka sake buɗe ta; share tsofaffin sockets a chrome://net-internals/#sockets.
Ba ka da proxy? Sayi keɓaɓɓun proxies masu aiki nan take
Keɓaɓɓun proxies na IPv4 a ƙasashe 9 daga 20.000₫/IP/wata idan ana saye daga 2.000 IPs (39.000₫ ga IP 1) da tsayayyun proxies na ISP a Vietnam, US. HTTP(S) da SOCKS5 tare da sunan mai amfani da kalmar sirri, bandwidth mara iyaka, aiki nan take bayan biya. Lura cewa a halin yanzu proxies na Vietnam suna amfani da ƙa'idar HTTP(S), babu SOCKS5 tukunna.
Sayi proxies yanzu