Skip to content

Updated

Hidemyacc Proxy Error:
Can't Connect to Proxy Server Fix

  1. When Check Proxy in Hidemyacc ends with Can't connect to proxy server, the cause is usually one of three things: the Connection type does not match the port (HTTP on 2222, SOCKS5 on 3333), the line in Quick add is wrong (Hidemyacc reads ip:port:username:password, in that order), or the IP or your own network is the problem.
  2. Run the same details through curl: if curl fails, the profile is not at fault; if curl works, the settings are.
  3. Hidemyacc's documentation names only this one failure message, so this page works from what you can test.

Check it right after buyingExample output

curl -x http://USER:PASS@HOST:PORT https://ipinfo.io/json

ip
203.0.113.24
country
US
Matches the country you picked
Day 15
203.0.113.24
Same address for the whole term
Example addresses (203.0.113.0/24), not real exits
01 / 09The 3 most common causes

Three causes cover most failures. Test the same details with curl first, then fix the profile.

The 3 most common causes

Cause 1: the Connection type and the port do not match. Under Your Proxy the Connection type list offers HTTP, Socks4 and Socks5 (the documentation also lists Tinsoftproxy and TMproxy). A Proxy302 entry on port 2222 is HTTP; on port 3333 it is SOCKS5. Choose the type that matches the tag in My assets.

Cause 2: the line in Quick add is wrong. Hidemyacc gives the format as ip:port:username:password. A missing part, a swapped pair, a space at the end or a hand-typed password with special characters is enough. Copy the host:port:user:pass line from My assets instead of typing it.

Cause 3: the IP or your network. The lease may have ended, a VPN or system-wide proxy may be in the way, or a firewall may block the port. Hidemyacc's own proxy guide links a Refused message to a firewall or network blocking the port and a timeout to a proxy that stopped responding or is very slow. A curl test separates this cause from the first two.

Check it in 6 steps

  1. Step 1: test outside Hidemyacc

    Open My assets, copy host, port, username and password, and run the curl command in the next block on the same computer. It should print the proxy's IP and country.

    Expected result JSON with the exit IP of the proxy.

    Before continuing If curl fails, stop here: the problem is the details, the lease or your network, not the profile.

  2. Step 2: set the Connection type

    On the Proxy tab choose Your Proxy and set Connection type to the protocol on the connection card in My assets: HTTP for port 2222, Socks5 for port 3333. If you are unsure, use HTTP on 2222.

  3. Step 3: paste the whole line again

    Clear the Quick add box and paste the host:port:user:pass line from My assets. You can also fill IP address/Host, Port, Username and Password one by one and compare each box with My assets.

  4. Step 4: look at the lease

    In My assets, check that the IP has not reached its end date. Auto-renew is optional and set per IP, so an IP with it off ends on its date.

  5. Step 5: remove what sits in between

    Turn off any VPN and any system-wide proxy on the computer while you test, and allow Hidemyacc through the firewall. On a restricted network, open Proxy302 Fast Connect before you use the proxy.

  6. Step 6: check the location

    Once Check Proxy passes, look at the flag and city next to the button and compare them with the country of the IP you bought. If they differ, open https://ipinfo.io/json in a profile window.

    Expected result The IP and country of the proxy.

Test the proxy outside Hidemyacc

# 1) HTTP proxy (port 2222)
curl -x "http://LOGIN:PASSWORD@HOST:2222" https://ipinfo.io/json

# 2) SOCKS5 proxy (port 3333); socks5h lets the proxy resolve the host name
curl -x "socks5h://LOGIN:PASSWORD@HOST:3333" https://ipinfo.io/json

Example only: replace LOGIN, PASSWORD and HOST with the values from My assets; percent-encode special characters in the login.

Which protocol works where

Which protocol works where
ItemPortIf the Connection type in Hidemyacc does not match
Static ISP, rented per IPHTTP 2222, SOCKS5 3333Both protocols connected in our test of 4 November 2026
Static ISP billed per GBHTTP 2222, SOCKS5 3333Works only over the protocol it was bought with
Rotating residentialHTTP 2222, SOCKS5 3333The same username and password work over both HTTP and SOCKS5
Datacenter, rented per IPHTTP 2222, SOCKS5 3333Each IP has one protocol, chosen at purchase

Source: Proxy302 product facts file (protocol tests of 4 November 2026, one account, ipinfo.io through proxy.proxy302.com). The console marks the few per-GB assets that have only one protocol as HTTP only or SOCKS5 only.

Symptoms and what to do

Check Proxy shows Can't connect to proxy server right away

Check Does curl with the same details work? Is Connection type the HTTP or Socks5 shown for that IP?

Fix Fix the type and port first, then paste the whole line again.

Stop when If curl fails too, do not keep editing the profile; look at the lease and your network.

It worked yesterday and fails today

Check Did the IP reach its end date, or did your computer's VPN or system proxy change?

Fix Check the end date in My assets; renew if needed, then run Check Proxy again.

curl works, Hidemyacc does not

Check Is there a space at the start or end of a box, or an old value left in another field?

Fix Clear every proxy field, paste the line again, and choose HTTP on 2222 if Socks5 keeps failing.

The check passes but the city is not the one you expected

Check Is this the IP you bought for this profile? A location lookup can also differ by a city or two between databases.

Fix Compare the country with My assets and with https://ipinfo.io/json opened in the profile.

What the Hidemyacc pages say and do not say

The profile guide documents one failure result, Can't connect to proxy server, and no troubleshooting steps. The proxy guide lists general causes for Refused, timeout and 407 and does not describe Check Proxy. So this page quotes only that one message and uses the checks that apply to any proxy.

A passing Check Proxy shows that the proxy connects. Platform rules are separate: use each account as the platform allows, from an IP in the account's country.

Which Proxy302 IP for Hidemyacc

For an account that stays signed in to the same profile, a static ISP IP does not rotate during the lease: US$0.50 for 1 day or US$7.99 for 30 days (about US$0.27 a day). Give each profile its own IP and keep its timezone and language in line with the IP's country.

There is no free trial; the smallest purchase is one IP for one day. If an IP stops working, write to Support with the order number and it is reissued.

FAQ

Why does Hidemyacc say Can't connect to proxy server?

Usually the Connection type does not match the port, the Quick add line is wrong, or the IP or your network is the problem. Run the same details through curl to tell which.

What format does Quick add expect?

Hidemyacc documents ip:port:username:password. The host:port:user:pass button in My assets copies the four values in that order.

Should I choose HTTP or Socks5 in Hidemyacc?

The one on the connection card in My assets. If you are unsure, HTTP on port 2222 is the safer choice, because a credential generated as SOCKS5 also worked over HTTP in our test.

My IP stopped working. What now?

Check its end date in My assets, then write to Support with the order number; a failed IP is reissued.

Further reading

Setup guides Proxy302 publishes on GitHub on the same topic:

View all partners →

Reference links

5
  1. Hidemyacc docs: create a new profile

    Official documentation · Confirmed on:

    Read on 20 November 2026: under Your Proxy the connection types are HTTP, Socks4, Socks5, Tinsoftproxy and TMproxy; the entry format is ip:port:username:password; Check Proxy shows a success caption or the failure caption "Can't connect to proxy server". No other failure message or troubleshooting step is on the page.

    Most of the page is screenshots with short captions.

  2. Hidemyacc: proxy error guide

    Official documentation · Confirmed on:

    Read on 20 November 2026: the page ties a Refused message to a firewall or network blocking the connection port, a timeout to a proxy that stopped responding or is very slow, and 407 to wrong login details or a device IP that is not on the provider's allowed list. It gives no format for the Hidemyacc fields and does not describe Check Proxy.

  3. Proxy302 Hidemyacc setup page

    Product observation · Confirmed on:

    The setup page of this site (/integrations/hidemyacc), read on 20 November 2026: copy the host:port:user:pass line from My assets, set the type to the protocol tag of the IP, then run the check.

  4. Proxy302 protocol tests, 4 November 2026

    Product observation · Confirmed on:

    Product facts file, tests of 4 November 2026 through proxy.proxy302.com with ipinfo.io: a rotating residential credential generated as SOCKS5 also worked over HTTP on 2222, one generated as HTTP failed over SOCKS5 on 3333; per-IP static leases connected over both protocols; per-GB static tokens connected only over the protocol they were bought with.

    Results are from one account on one day; the console marks per-GB tokens as HTTP only or SOCKS5 only.

  5. Proxy302 product facts and price list

    Product observation · Confirmed on:

    Product facts file of the site (values checked on 10 November 2026): protocols and ports, prices in US$ (1 PTC = US$1), lease terms, quantity limits, no free trial.

Ready to try it?

Create an account, top up once, then pick rotating residential, static ISP or datacenter IPs and have one running in your browser within minutes.