ProxyV4

Gyara kuskuren 407 daga proxy: jerin duban bayanan shiga

Updated:

Amsar 407 Proxy Authentication Required tana sanar da kai abubuwa biyu a lokaci guda: bayanan yanar gizonka sun isa ga proxy, kuma proxy din ba ta karbi sunan mai amfani da kalmar sirri da aka tura mata ba (ko kuma ba a tura mata komai ba). Matsalar ba ta hanyar sadarwa ba ce. Dauki 407 a matsayin matsalar shiga, kuma yawanci za ka warware ta cikin 'yan mintuna kadan.

Layi daya, a shirye don manna

Menene ma'anar 407 Proxy Authentication Required?

407 na nufin proxy ne ke cewa "Ban san ko kai wanene ba". Bukatarka ta isa gare shi, don haka hanyar sadarwa tana aiki, amma sunan mai amfani da kalmar sirri ba daidai ba ne, sun lalace ko ba a taba tura su ba. Gyara bayanan shiga kuskuren zai bace; canza DNS, firewalls ko kasar proxy ba zai taimaka ba.

Takaitaccen bayani kan dalilan 407

Layuka biyu na farko sune suka fi jawo korafin neman taimako. Kwafin kalmar sirri daga tattaunawa (chat) ko ma'ajiyar lissafi (spreadsheet) sau da yawa yana kwashe sarari na karshe ko layin da ya karye tare da shi.

DaliliAlama ta yau da kullumGyara
Kuskuren rubutu ko sarari marar ganuwa a kalmar sirriYana faduwa a kowace manhaja, na'urar bincike (checker) tana cewa auth failed (407)Share bangarorin biyu sannan ka liqa sababbi daga Orders
Dukan layin ip:port:user:pass an liqa shi a fanni gudaManhajar tana adana shi amma ba ta taba shiga baRaba shi zuwa fannoni hudu, ko ka canza shi da format converter
Manhaja tana adana host da port kadaiProxy na tsarin Windows, macOS ko Android; manhajojin da ba su da tambayar shiga suna faduwaShigar da bayanan shiga a cikin manhajar kanta, ko amfani da shiga ta IP whitelist
@, : ko # a cikin kalmar sirri a cikin URLYana aiki a fom, amma yana faduwa a URL na user:pass@hostYi percent-encode (@ shine %40) ko tura bayanan shiga daban
Shiga ta IP whitelist daga adireshin da ba ya cikin jerinYa yi aiki a ofis, amma ya fadi a gida ko a sabon uwar garke (server)Sanya sabon public IP a karkashin IP Whitelist, ko "Revert to user:pass"
Nau'in proxy bai dace da oda baAn zabi SOCKS5 a kan odar HTTP kadai, ko akasin hakaDaidaita nau'in da yanayin oda, ko sauya odar zuwa duka biyun

Gane 407 a cikin curl, Chrome da checker

Ga yadda ya bayyana a kan proxy na gwajinmu (an nuna shi da adireshin takardu 203.0.113.10:8080 da kuma biyun da aka canza da gangan user123:pass456). Neman shafin HTTPS tare da curl -x http://user123:[email protected]:8080 https://example.com yana karewa da curl: (56) CONNECT tunnel failed, response 407. Neman shafin HTTP na asali tare da -w %{http_code} yana buga 407 kadai.

Sanya -v yana amsa muhimmiyar tambaya: shin mai karba (client) ya tura bayanan shiga? A cikin cikakken bayanin (verbose trace) ya kamata ku ga > CONNECT example.com:443 HTTP/1.1, sannan > Proxy-Authorization: Basic ..., sannan kuma amsar 407. Lokacin da babu layin Proxy-Authorization, client din bai taba tura bayanan shiga ba, don haka duba saitunan manhajar maimakon kalmar sirri kanta.

proxy checker na ProxyV4 yana lakaba wannan yanayin da auth failed (407). Headless Chrome ba shi da akwatin shiga da zai nuna, don haka yana bayar da rahoton kin amincewa iri daya a matsayin ERR_TUNNEL_CONNECTION_FAILED, wanda aka yi bayaninsa a tunnel error page.

Yadda ake gyara 407 Proxy Authentication Required a kowane client

Nemo kayan aikin ku a kasa. A kowane hali makasudin daya ne: dole ne manhajar ta tura ainihin sunan mai amfani da kalmar sirri daga odar ku a kowane hadi.

Browsers (Chrome, Edge, Firefox) da wayoyi

  • Chrome on Windows: Chrome yana amfani da proxy na Windows (Settings > Network & Internet > Proxy), wanda ke daukar adireshi da port kadai. Lokacin da shafi na farko ya bude, Chrome yana fito da akwatin shiga domin sunan mai amfani da kalmar sirri na proxy. Idan kun yi kuskuren rubutu kuma akwatin bai sake fitowa ba, rufe dukkan tagogin Chrome sannan ku sake bude shi.
  • iPhone: a karkashin Settings > Wi-Fi > (i) > Configure Proxy akwai maɓallin Authentication. Idan ya kasance a kashe, proxy zai bada amsar 407. Android gaba daya yana karbar host da port kadai, don haka manhajojin da ke bukatar shiga kan nuna kuskuren hadi mara fayyace a maimakon haka.
  • Firefox yana rike saitunan proxy na kansa kuma yana nuna akwatin shiga nasa; zabi "Manual proxy configuration" maimakon "Use system proxy settings" idan ana son Firefox ya yi amfani da lambobi daban da na Windows.

curl

bayar da bayanan shiga tare da -U "user:pass" sannan ka bar URL na proxy ba tare da bayanan shiga ba. Hakan yana kawar da duk wata matsala ta haruffa na musamman.

curl -v -x http://IP:PORT -U 'USER:PASS' https://proxyv4.com/api/my-ip

Python requests

407 a kan HTTPS URL yana kawo requests.exceptions.ProxyError tare da Tunnel connection failed: 407 Proxy Authentication Required a cikin sakon. sanya http://user:pass@host:port a karkashin maballan http da https na kamus din proxies, sannan a fara tura kalmomin sirri marasa saba ta cikin urllib.parse.quote da farko. Python requests guide yana da cikakken misali.

Selenium da Puppeteer

Headless Chrome ba zai iya nuna akwatin shiga ba, don haka 407 yana bayyana a matsayin ERR_TUNNEL_CONNECTION_FAILED. A cikin Puppeteer, bar --proxy-server=http://IP:PORT sannan a kira page.authenticate({ username, password }) a kowane shafi kafin goto(). A cikin Selenium, ChromeDriver yana watsar da bayanan shiga da aka rubuta a --proxy-server; yi amfani da selenium-wire ko karin auth (auth extension), ko kuma canza odar zuwa shiga ta IP whitelist. Duba jagororin Puppeteer da Selenium.

Browsers na antidetect

AdsPower, GoLogin, GenLogin da makamantan manhajoji suna bukatar Host, Port, Username da Password a matsayin lambobi hudu daban-daban. Maimakon gyara kalmar sirri a wurin, share fannin sannan ka liqa sabon kwafi. GoLogin setup guide yana nuna kowane fanni.

Idan gwajin da ke ciki ya wuce amma shafuka har yanzu suna tambayar shiga, bayanin martaba (profile) na iya kasancewa an saita shi zuwa SOCKS5 a kan odar HTTP, ko akasin haka.

Bayanan shiga daidai ne amma 407 ya ci gaba da wanzuwa

Bincika nau'in proxy na gaba. Proxies na ProxyV4 suna zuwa a matsayin layi guda na ip:port:user:pass tare da sunan mai amfani da kalmar sirri, kuma dole ne nau'in manhajar ya dace da tsarin (protocol) na oda: HTTP don odar HTTP, SOCKS5 don odar SOCKS5. Sannan ka gwada ainihin layin da ka kwafa daga dashboard a cikin checker. Idan checker ya hade amma manhajarka har yanzu tana samun 407, bambancin yana cikin yadda manhajar ke adanawa ko tura bayanan shiga.

Idan kuna amfani da shiga ta IP whitelist, ku tuna cewa yana bin public IP dinku ne. Sabon layin ofis, hotspot na waya ko VPN yana ba ku adireshi daban, kuma proxy zai sake tambayar bayanan shiga. Sanya sabon adireshin a karkashin IP Whitelist (ana ba da izinin har zuwa 3) ko mayar da odar zuwa user:pass.

Mataki bayan mataki

  1. 1

    Kwafi layin kai tsaye daga Orders

    Bude odar a cikin dashboard na ProxyV4 dinka sannan ka kwafi cikakken layin proxy maimakon sake rubuta shi.

  2. 2

    Gwada shi a cikin mai duba proxy

    Manna layin a cikin proxy checker. Sakamakon auth failed (407) yana tabbatar da cewa matsalar tana wajen bayanan shiga ne, ba hanyar sadarwa ba.

  3. 3

    Sake manna sunan mai amfani da kalmar sirri

    Share filayen biyu a cikin manhajarka sannan ka sake manna su sababbi, ba tare da wani abu a gaba ko a bayan rubutun ba.

  4. 4

    Daidaita nau'in proxy da oda

    Zabi HTTP don odar HTTP ko SOCKS5 don odar SOCKS5 (kowannensu yana aiki a kan odar yanayi biyu), ajiye profile din sannan ka sake loda shafin.

  5. 5

    Bincika bayanan da curl -v

    Idan 407 ta ci gaba da kasancewa, kunna curl -v tare da ainihin bayananka sannan ka nemi layin Proxy-Authorization kafin amsar.

Tambayoyi da aka fi yi

Shin 407 na nufin kamfanin intanet dina yana toshe proxy din ne?

A'a. Proxy ne da kansa yake fitar da 407, wanda ke nuna cewa hadin ku ya isa gare shi. Hanyar da aka toshe tana nuna daban: karewar lokaci (timeout) ko kin amincewa da hadi. Duba proxy timeout.

Me ya sa Chrome ke ci gaba da nuna akwatin shiga proxy?

Duk wani yunkurin da aka ki amincewa da shi yana kawo wani 407, kuma Chrome zai sake tambaya. Bincika Caps Lock sannan ka tabbata yanayin rubutu na madannanka (keyboard) ba ya kara alamomi ko sauya haruffa a kalmar sirri.

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

Yi amfani da percent-encode ga alamomin: @ zai zama %40, : zai zama %3A, # zai zama %23. Tare da curl, tura bayanan shiga ta -U na nufin ba kwa bukatar sauya komai.

Puppeteer ko Selenium yana nuna kuskuren tunnel, ba 407 ba. Abu daya ne?

Sau da yawa, eh. Headless Chrome ba zai iya tambayar kalmar sirri ba, don haka ana bayar da rahoton 407 a matsayin ERR_TUNNEL_CONNECTION_FAILED. Tura bayanan shiga ta hanyar tantancewa ta dakin karatu (library) din kanta, kamar yadda aka nuna a Selenium guide.

Shin proxy zai iya dawo da 407 koda kuwa ana shiga ta hanyar IP whitelist?

Eh, idan bukatar ta fito daga wani IP na fili (public IP) wanda ba ya cikin whitelist na oda. Bincika adireshinku na yanzu a What is my IP sannan ku kwatanta shi da jerin.

Layi daya, a shirye don manna

Kowace odar ProxyV4 tana ba ka layin ip:port:user:pass domin keɓaɓɓen IPv4 ko tsayayyen adireshin ISP. Kwafi shi sau daya, yi amfani da shi a kowace manhaja.

Duba farashin yanzu

Related articles

Kura-kuran furoksi
A bayan ERR_TUNNEL_CONNECTION_FAILED: karanta amsar CONNECT ta proxy
ERR_TUNNEL_CONNECTION_FAILED yana ɓoye ainihin amsar proxy ga CONNECT. Gano 407 ko 502 da ke ciki don gyara Chrome, Puppeteer, Playwright ko Android.
Kayan aiki na kyauta
Duba proxies da yawa lokaci guda: matsayi, exit IP da latency
Gwajin proxy kyauta a yanar gizo: manna layukan ip:port:user:pass har 100 don ganin masu aiki, exit IP da latency, tare da ma'anar kowane sakamakon matsala.
Saitin furoksi
Tura Google Chrome Ta Cikin Keɓaɓɓiyar Proxy
Sanya proxy na HTTP(S) a Google Chrome kawai ba duka kwamfuta ba: extension na kowane profile, shortcut na --proxy-server, ko saitunan proxy na na'ura.
Saitin furoksi
Yin amfani da cURL tare da proxy mai tantancewa: dokokin da ke tabbatar da aikinsa
Aika buƙatun cURL ta proxy na HTTP(S) mai tantancewa tare da -x da -U, tabbatar da exit IP, duba CONNECT handshake, kuma auna lokacin kowace buƙata a kowace OS.
Saitin furoksi
Bukatar Python ta hanyar ingantaccen proxy, mataki-mataki
Aika bukatar Python ta hanyar ingantaccen proxy na HTTP(S): gina proxies dict, haɗa shi da Session, sauya kalmomin sirri, juya lissafi, sannan duba IP.
Saitin furoksi
Saita Proxy a Windows 10 da Windows 11
Saita HTTP(S) proxy a Windows 10 ko 11: shafin Proxy a Settings, ajiye bayanan shiga a Credential Manager, da ka'idojin CLI da netsh winhttp.
Saitin furoksi
Saita proxy na GenLogin domin IP da fingerprint su ba da labari guda
Saka proxy na GenLogin a furofayil, cika WebRTC da yankin lokaci daga IP, shigar da layuka ta Proxy Manager, kuma gyara kuskuren 407 ko timeout.
Kura-kuran furoksi
Chrome na nuna ERR_PROXY_CONNECTION_FAILED: share shi a matakai biyar
ERR_PROXY_CONNECTION_FAILED na nufin Chrome ba ta iya isa ga proxy ba. Nemo tsohon saiti, kuskuren tasha ko kari domin gyara matsalar a kowace na'ura.