BlogGuide8 min read

What to check when a proxy will not connect

When the browser says the proxy refused the connection, start with the password paste, then HTTP versus SOCKS, then any IP change still running. The modem is often fine.

A red cable unplugged from a 4G modem on a dark desk
A refused connection is usually the password, the port, or a network that blocks proxies.

Work through this list in order

Do not skip around. A wrong password with the right port still fails. The right password on SOCKS5 in Chrome still fails. An IP change that has not finished yet can make a good setup look dead for a couple of minutes.

  1. Paste the username, password, host, and port again from the dashboard. Clear any proxy password the browser has saved.
  2. Match the protocol. Browsers get the HTTP host and port. An app with a SOCKS5 field gets the SOCKS5 host and port.
  3. If you just requested a new IP, wait until the dashboard says that request finished. Then try once.
  4. If it still fails, repeat the same browser settings on a phone hotspot. That tells you whether the office or cafe network is blocking the port.

What the error is telling you

The wording points at the cause. “Proxy refused the connection” or an instant failure usually means the wrong port or protocol — often a SOCKS address pasted into a browser. A repeated username-and-password prompt with the right port usually means the password is wrong, not the connection.

A page that hangs and then times out, on a network you do not control, usually means something is filtering the port rather than the credential. And a connection that worked yesterday and fails today, with nothing changed on your side, is worth one retry before you touch anything — it is often the vendor moving an address or finishing an IP change.

The password and the paste

Do not edit the password by eye. A single extra space at the end is enough to make every login fail. If the browser offers a saved proxy password, delete that saved login so it cannot keep sending the broken one.

The browser prompt is asking for the proxy username and password. It is not asking for the password of the website you are trying to open.

HTTP versus SOCKS5

Browsers need the HTTP endpoint. Apps that say SOCKS5 need the SOCKS endpoint. Swapping them produces an instant failure that looks like an outage. Changing the password will not fix a crossed port. The two endpoints are explained in HTTP or SOCKS5.

An IP change, or a network that blocks the port

If you just asked for a new IP, wait. On a mobile line that often takes a couple of minutes. A second click while the first request is still running often leaves the session stuck. Check the IP once, after the dashboard says the request finished — not every thirty seconds.

Some office and public Wi-Fi networks block outbound connections to proxy ports. Try the same browser settings on a phone hotspot. If it works on the hotspot and fails on the office network, the proxy is up. That network is filtering the port. Use a network that allows it, or ask whoever runs the office firewall.

If it fails the same way on both networks, go back to the password, the protocol, and any IP change that is still in progress. If those are clean, write to the provider. Once it connects, run how to test a proxy before you rely on it before a real account uses the line.

Send the exact error text, whether you used HTTP or SOCKS5, the host and port (not the password), and whether a phone hotspot failed too. That is enough to separate a bad paste from a down modem. On our line the browser uses HTTP, apps that ask for it use SOCKS5, and a new IP happens only when you request it. Field names are in the documentation. If the checks above are clean and it still will not connect, write to support@proxygateway.si with the error text and the endpoint you used.

What to include when you ask for help

A short, complete message gets a faster answer than a screenshot with no text. Include the exact error string, whether you used HTTP or SOCKS5, the host and port, and whether the same settings worked on a phone hotspot. Never send the password; no support agent needs it to check a connection.

If you can, add the one fact people leave out: what changed just before it stopped. A new country on your machine, a company VPN switched on, a fresh modem driver, or a router reboot all matter. Most “stopped working” reports trace back to something outside the proxy, and that one line saves a round of guessing.

Why does the browser keep asking for the proxy password?

The saved login is usually wrong, or a space got into the paste. Clear the saved proxy password, copy the fields again from the dashboard, and confirm you used the HTTP endpoint.

How long does a new IP take on a mobile line?

Often a couple of minutes. Wait until the dashboard says the request finished, then check the address once. A second request during that wait is a common reason the session looks dead.

It works on a phone hotspot and fails on the office network. Is the proxy down?

No. The line is up. The office network is blocking the proxy port. Use a network that allows that outbound port.

What should I send support if it still will not connect?

The exact error text, whether you used HTTP or SOCKS5, the host and port (never the password), and whether a phone hotspot failed the same way. Add what changed just before it stopped — a new network, a VPN, or a router reboot.