Yadda za a gyara 407 Proxy Authentication Required

Updated: 2026-11-05

Kuskuren 407 labari ne mai kyau fiye da yadda yake gani: na'urarka ta isa ga proxy kuma hanyar sadarwa a bude take. Abin da proxy ke fada kawai shi ne bai sami sunan mai amfani da kalmar sirri masu inganci ba. Shi ya sa kusan kowane kuskuren 407 ake magance shi daga bangaren bayanan shiga, ba a cikin na'urar router ko firewall dinka ba.

Private proxies masu cikakkun bayanan shiga

Duba farashin proxy Free Proxy Checker

Dalilan kuskuren 407, tun daga wanda aka fi samu

Sunan mai amfani/kalmar sirri da ba daidai ba ko kuma babu. Haruffa daya da aka kuskure rubutawa, ko kuma sarari (space) a karshe da aka kwafa tare da kalmar sirri. Wannan ne ke haddasa mafi yawan rahotannin 407.
Manna bayanai a akwatunan da ba su dace ba. Dukkan layin ip:port:user:pass yana karewa a akwatin Host, ko kuma sunan mai amfani ya fada cikin akwatin kalmar sirri. Wasu kayan aiki suna raba wadannan bangarori hudu da kansu, wasu kuma ba sa yi.
Manhajar ba ta taba aika bayanan shiga ba. Tsarin proxy na manhajar aiki (OS) yana adana adireshi da tashar port ne kawai. Manhajojin da ba sa iya neman kalmar sirri suna haduwa ne ba tare da bayanin auth header ba kuma suna samun kuskuren 407 a mayar musu.
Haruffa na musamman a cikin URL na proxy. A cikin tsarin http://user:pass@host:port, dole ne a canza haruffa kamar @, : ko # da ke cikin kalmar sirri zuwa lambobin kashi (percent-encoded inda @ ke zama %40), in ba haka ba za a raba rubutun a wurin da ba daidai ba.

Yadda kuskuren 407 yake a zahiri

Mun sake gwada kuskuren a wata na'urar gwaji ta proxy, wadda aka nuna a nan da adireshin takardu 203.0.113.10:8080 da kuma gangan aka sanya user123:pass456 da ba daidai ba. Idan aka gwada da shafin HTTPS, curl -x http://user123:[email protected]:8080 https://example.com yana fitar da curl: (56) CONNECT tunnel failed, response 407. Idan aka gwada da shafin HTTP na yau da kullum tare da -w %{http_code}, curl yana nuna 407 ne kawai.

Sanya -v don ganin ko an taba aika bayanan shiga ko a'a. Binciken yana nuna > CONNECT example.com:443 HTTP/1.1, sannan > Proxy-Authorization: Basic ..., sannan ne kawai 407 ke biyo baya. Idan babu layin Proxy-Authorization, to manhajarka ba ta taba aika bayanan shiga ba ko kadan.

Na'urar VinaProxy proxy checker tana ba da rahoton wannan yanayin a matsayin auth failed (407). Headless Chrome, wanda ba shi da akwatin tambayar shiga, yana nuna shi a matsayin ERR_TUNNEL_CONNECTION_FAILED; duba shafin kuskuren tunnel.

Hanyoyin gyara dangane da manhaja da na'ura

Windows da Chrome: Chrome yana bin tsarin proxy na Windows (Settings > Network & Internet > Proxy), wanda ke dauke da adireshi da port kawai. A lokacin da aka bude shafi na farko, Chrome yana bude akwatin shiga domin neman sunan mai amfani da kalmar sirri na proxy. Idan ka rubuta shi ba daidai ba kuma akwatin bai sake dawowa ba, rufe dukkan tagogin Chrome sannan ka sake budewa.
Browsers masu hana ganowa (AdsPower, GoLogin, GenLogin): ajiye Host, Port, Username da Password a cikin akwatuna daban-daban. Goge dukkan abin da ke cikin akwatin kalmar sirri gaba daya sannan ka sake manna shi maimakon gyara shi. Ana samun jagorar kowane akwati a cikin jagorar saita GoLogin.
Wayoyi: iPhone tana da madannin Authentication a karkashin Settings > Wi-Fi > (i) > Configure Proxy; barin shi a kashe yana haifar da 407. Android yawanci tana karbar host da port ne kawai, don haka manhajojin da ke bukatar shiga na iya nuna kuskuren haɗi na gama-gari a maimakon haka.
curl: shigar da -U "user:pass" daban maimakon hada shi a cikin URL, wanda hakan ke magance matsalolin haruffa na musamman.
Python requests: saita http://user:pass@host:port ga duka maballan http da https a cikin proxies dict, kuma ka canza kalmomin sirri masu wahala da urllib.parse.quote.

Bayanan shiga daidai ne amma 407 ya ki tafiya

Kwatanta ka'idojin sadarwa (protocols) na gaba. VinaProxy yana sayar da HTTP(S) proxies masu shiga ta user:pass da kuma SOCKS5, don haka zabi protocol din da aka nuna akan odarka a cikin dashboard. Idan mai binciken ya amsa da not socks5, wannan tashar tana amfani da HTTP ne kuma bai kamata a saita ta a matsayin SOCKS5 ba.

Mataki-mataki

1
Kwafi layin proxy daga dashboard
Bude odar a cikin dashboard dinka na VinaProxy sannan ka kwafi cikakken layin maimakon rubuta shi da hannu.
2
Gudanar da shi ta hanyar proxy checker
Manna shi a cikin proxy checker. Sakamakon auth failed (407) yana tabbatar da matsalar bayanan shiga ce ba matsalar hanyar sadarwa ba.
3
Sake shigar da sunan mai amfani da kalmar sirri a tsanake
Share dukkan akwatunan biyu a cikin software dinka sannan ka sake manna su ba tare da barin sarari a farko ko a karshe ba.
4
Daidaita protocol da bayanin oda
Saita nau'in proxy zuwa HTTP ko SOCKS5 daidai da yadda aka bayyana a odar, sannan ka ajiye.
5
Bincika da curl -v idan matsalar ta ci gaba
Gudanar da curl -v tare da ainihin bayanan ka sannan ka duba idan akwai layin Proxy-Authorization kafin 407.

Tambayoyin da aka fi yi

Shin kuskuren 407 yana faruwa ne saboda ISP dina ya toshe proxy?

A'a. Ita kanta na'urar proxy ce ke aiko da 407, don haka haɗin ya wuce. Hanyar da aka toshe tana bayyana ne a matsayin bata lokaci ko kin yarda da haɗi; duba proxy timeout.

Me ya sa Chrome ke ci gaba da neman shigar da bayanan proxy?

Kowane shigarwa da ba daidai ba yana samun wani 407 kuma Chrome zai sake tambaya. Bincika Caps Lock kuma ka tabbata wata hanyar rubutu ta Vietnamese ko wata daban ba ta kara wasula ko alamomi a kalmar sirrin ba.

Yaya zan saka kalmar sirri mai dauke da @ a cikin URL na proxy?

Canza shi: @ a matsayin %40, : a matsayin %3A, # a matsayin %23. Idan ana amfani da curl, alamar -U tana kauce wa bukatar yin encode gaba daya.

Selenium ko Puppeteer na nuna kuskuren tunnel maimakon 407. Matsala daya ce?

Yawanci haka ne. Headless Chrome ba zai iya nuna akwatin shiga ba, saboda haka 407 ke bayyana a matsayin ERR_TUNNEL_CONNECTION_FAILED. Shigar da bayanan shiga ta hanyar tsarin auth na library din, kamar yadda aka nuna a cikin Selenium guide.