➡️ How to Use the SOCKS Protocol

All of Rayobyte’s Static Proxy Services, including Dedicated, Semi-Dedicated, ISP, and Semi-ISP Proxies, support the SOCKS protocol in addition to standard HTTP/HTTPS.

The SOCKS protocol is especially useful for tools requiring direct TCP-level routing, advanced scraping frameworks, or non-browser traffic.


➡️ When to Use SOCKS

You may need SOCKS when:

  • ✔ A script or tool requires SOCKS5 instead of HTTP/HTTPS.
  • ✔ A website blocks HTTP requests but allows SOCKS traffic.
  • ✔ You need low-level TCP transport rather than HTTP-based requests.

SOCKS supports both IP Authorization and Username/Password Authorization.


➡️ IP Authorization (SOCKS)

  1. Find your device’s IP by searching “What is my IP”.
  2. Log in to your IPv4 Proxy Dashboard.
  3. Select Authorization Type → Via IP → SOCKS.
  4. Add your device’s IP under Authorized IPs.

⏱ Allow 5–10 minutes for your IP to authorize.


➡️ Username/Password Authorization (SOCKS)

  1. Log in to your IPv4 Proxy Dashboard.
  2. Select Authorization Type → Username/Password → SOCKS.
  3. Locate your assigned username and password.

⚠ Important: Browsers do not support SOCKS with username/password authentication through their built-in proxy settings. An extension such as FoxyProxy is required.


➡️ Configuring SOCKS in Your Browser

Browser support varies between HTTP/HTTPS and SOCKS, and some SOCKS options require an extension (e.g., FoxyProxy).

For complete step-by-step instructions for:

  • ✔ Microsoft Edge (Windows)
  • ✔ Google Chrome (Windows & macOS)
  • ✔ Mozilla Firefox (Windows & macOS)
  • ✔ Safari (macOS)

Visit our full guide here:

➡ Browser Proxy Configuration Guide (HTTP & SOCKS)

This guide covers both IP Authorization and Username/Password setups.


➡️ SOCKS Connection Details

  • SOCKS via IP Authorization: Port 1080
  • SOCKS via Username/Password: Port 1081

➡️ SOCKS Limitations and Restrictions

  • SOCKS is not encrypted. Always use HTTPS websites.
  • Not ideal for dynamic IP setups.
  • Some websites block SOCKS traffic.
  • DNS may resolve locally unless configured through the browser/tool.

➡️ Troubleshooting SOCKS Connectivity

  • ✔ Verify the correct port (1080 or 1081).
  • ✔ Wait 5–10 minutes after updating IP authorization.
  • ✔ Test using another app or browser.
  • ✔ Ensure your software supports SOCKS5.

If issues persist, please create a support ticket and include your proxy username, port, and specific steps to reproduce the issue.


➡️ Need Help?

Our support team is happy to assist with SOCKS configuration or determine whether SOCKS is the right choice for your tools.

Email Support
Create a Support Ticket