Proxy Error 465 or “No Proxies Available”: What It Means and How to Fix It
You copied your session into a browser profile or a script, ran the proxy check, and it failed with “status code 465”, “request failed with status code 465” or “no proxies available”. Your username, password, host and port were accepted. What the network could not do is find a free residential IP in the exact place the session asks for.
Error 465 is about the location, not your login. Clear the city (or the city and the state) in the session’s Edit tab, copy the username again, and try again. Nothing is lost: your bandwidth is not affected.
Why a location can have no IPs
Residential IPs belong to real households and mobile users, so a small town may have only a handful at any moment, and sometimes none free. A whole country draws from a very large pool, a state from a smaller one, and a single small city from the smallest. The same applies to an ISP: one ISP across a country is a smaller pool than the country itself, and an ISP is never combined with a state or city.
Test it without leaving the dashboard
- 1Open My Proxies and expand the session.
- 2On the Credentials tab, choose Test location.
- 3If there are no IPs there right now, the result says so and offers the wider options: keep the state, use the whole country, or drop the ISP. Choose one and it is saved for you.
- 4Copy the session’s username again from the Credentials tab and update it in your tool. The old username still carries the old city.
You can also test a place before you create anything: on the New session form, choose Test location under the country, state and city pickers (it appears once a state or city is chosen). If the place has no IPs, the widen buttons change the form’s own fields. And when you create a session aimed at a state or a city, the same test runs for you right after it is created, and offers the wider location straight away if the place has no IPs.
Test it from your own machine
To confirm the result outside the dashboard, send one request through the session. Use the exact username from the Credentials tab. On Windows PowerShell, type curl.exe instead of curl.
curl -x "http://USERNAME:PASSWORD@proxy.globproxy.com:PORT" https://ipinfo.ioIf this also returns 465, the location is the cause. If it returns an IP in your target country, the proxy is working and the problem is in the tool you were testing from.
Which fix to choose
| What you need | Do this | What to expect |
|---|---|---|
| A particular city | Pick a larger city nearby, or keep the state and drop the city | A bigger pool. Test it again to confirm. |
| A region, not a city | Keep the state, clear the city | The exit can be anywhere in the state. |
| The country only | Clear the state and city | The largest pool. The most reliable choice. |
| A particular ISP | Set the ISP with the country only | An ISP cannot be combined with a state or a city. |
A passing test is a snapshot. A small place can run short later, so for work that must not fail, prefer a state or the whole country.
Still getting 465 after widening?
- →Check that your tool uses the new username. Copy it again from the Credentials tab; an old copy keeps the old city.
- →Try the country only, with no state, city or ISP. If that works, the narrower setting was the cause.
- →Open Support in the dashboard sidebar and send the session’s label and the country, state and city you chose.
Frequently asked
Still stuck?
Email us at support@globproxy.com and include your account email and what you see on screen.
Contact support →