Proxmint troubleshooting
Diagnose failing Proxmint proxy connections. Use when a request through Proxmint returns 407, 403, 500, 502 or 503, a CONNECT tunnel fails, SOCKS5 refuses a connection, the exit IP is in the wrong country, a sticky session changes IP, a browser leaks its real IP through DNS or WebRTC, or a site loads directly but not through the proxy.
Proxmint troubleshooting
Find the cause from evidence, then give the smallest fix. Explicit instructions from the user take priority over this skill.
Inputs to gather
Ask only for what is missing:
- The exact error text or status line, such as
HTTP/1.1 503 NO_RAYorTunnel connection failed: 407. - The tool or library, and HTTP (port 823 or a sticky port) or SOCKS5 (port 824).
- The username with the real login replaced by
LOGIN, for exampleLOGIN__cr.us;city.newyork. - The target host and port.
- Whether every site fails or only some.
Never ask for the password. If the user pastes one, don't repeat it.
When the plugin's account tools are connected, look before asking: get_account shows each product's status and
bandwidth left (a used-up product answers 407 TRAFFIC_EXHAUSTED), and check_connection sends one test request
through a product, optionally from a chosen country.
Workflow
- Read the gateway's reason. The proxy puts it in the status line. Look it up in
references/errors.md. Most clients print it inside their own error, for example curl'sCONNECT tunnel failed, response 403. - SOCKS5 gives no reason text. Map the symptom with the SOCKS5 section of
references/errors.md, or ask the user to repeat the request over HTTP on port 823, where the status line names the reason. - No status at all (timeout, connection refused, DNS failure for
gw.proxmint.com): check the host and port, then a local firewall or a corporate network blocking outbound port 823 or 824, thenhttps://proxmint.com/status. - The destination port. The network reaches only ports 80, 443, 8080, 8443, 8888, 8090, 53, 853, 5060 and
5228. Any other port fails with
403 PORT_BLOCKED(SOCKS5 reply0x02). - Blocked sites. Banks, payment providers, government websites (
.gov,.gov.uk,.miland the like) and a short named list fail with403 SITE_PERMANENTLY_BLOCKEDon every plan. The site checker onhttps://proxmint.com/docs/blocked-websitesshows whether a host is listed. Some sites can be opened for one product after review, through Request an unblock in the dashboard; approval isn't guaranteed. Don't suggest workarounds. - The site itself refuses the traffic (its own 403 page, a CAPTCHA, a block page) while the gateway shows no error: the site decides who it serves. Say so, and suggest the site's official API or the owner's permission. Don't offer ways to defeat bot protection, CAPTCHAs or rate limits.
Common symptoms
- Wrong country. A location key in the username replaces the product's saved Targeting entirely. A username without one uses the saved Targeting. Geolocation databases also disagree about residential and mobile IPs: compare at least two before concluding the exit is wrong.
- IP changes during a sticky session. The IP went offline, or
sessttlran out (1 to 120 minutes). Catch the error and continue with a newsessid. - IP doesn't change on the rotating port. The client is reusing one connection (
requests.Session,httpx.Client, a browser). Each new connection gets a new IP. - Targeting is ignored. The tool cut the username at a semicolon or a length limit. Check the field kept the whole username.
- Works in curl, fails in a browser automation tool. Chromium can't read credentials embedded in a proxy URL:
pass the username and password as separate fields (Playwright) or with
page.authenticate(Puppeteer). - HTTP/3 or other UDP traffic fails over SOCKS5. SOCKS5 here carries TCP only.
DNS and WebRTC leaks
- DNS: use
socks5h://rather thansocks5://so hostnames resolve through the proxy. Over HTTP, CONNECT already sends the hostname to the proxy. - WebRTC in browsers can reveal the machine's own IP over UDP outside the proxy. In Chromium, launch with
--force-webrtc-ip-handling-policy=disable_non_proxied_udp. In Firefox, setmedia.peerconnection.ice.proxy_onlytotrue. Antidetect browsers have their own WebRTC setting per profile. - Check the result on a WebRTC leak test page: the only public IP shown should be the proxy's.
Output
- The most likely cause, and how confident you are.
- The fix as a concrete change: a username, port, code or setting.
- How to confirm it worked.
- If it's outside the user's control (a blocked site, an outage), say who can act on it: Proxmint support at
https://proxmint.com/support, or the site's owner.
Links
- Docs: proxmint.com/docs
- Pricing: proxmint.com/pricing
- Status: proxmint.com/status
Related skills
- Downloads
- 90All time
- Security audit
- Pass
- Last updated
- 2w ago
- Current version
- v1.0.0
- License
- MIT-0
