Skip to main content
If HTTP works normally but SOCKS5 does not, this is usually caused by your network or ISP blocking the default SOCKS5 port. This applies to Residential and Mobile proxies.

​
Fix it by changing the port

To resolve this, simply change the port number of your proxy. Switching to an alternative port (for example 1081, 1082, and so on) can bypass network restrictions and restore SOCKS5 functionality.

​
Example

Original:
Updated:
For the full SOCKS5 port range, see What ports can I use with your proxies?.

​
If changing the port doesn’t help

Work through these in order.
1

Try a different gateway

Test each of these in place of gate.nodemaven.com:
  • gate-us.nodemaven.com
  • gate-eu.nodemaven.com
2

Try a different internet connection

Connect to a neighbour’s or friend’s wifi, or create a hotspot with your phone and connect your PC to it. Then test the proxy again.If the proxy works on the other connection, the block is on your own network and your ISP is the one to contact.
3

If you have a desktop and cannot connect to a phone hotspot

Download a proxy management app such as Super Proxy from the Play Store or App Store and connect to the proxy on your phone directly. Make sure you use the SOCKS5 protocol.If the connection works there, contact your ISP.
To confirm whether the proxy itself is responding, see Verify your proxy’s status with the curl command.