Can I switch my proxy between HTTP and SOCKS5?
In short: Yes. Every static ISP proxy runs HTTP, which carries HTTPS, or SOCKS5, and you switch the order you already hold. Use Change protocol in your dashboard or the protocol call of the API. The order then shows the port and credentials to use after the switch, so copy them again, and expect a brief pause while it switches.
Protocol is a setting of the order, not a separate product. You do not buy HTTP proxies and SOCKS5 proxies apart: the one you hold can be switched to either, and changing the client alone is not enough, because the proxy itself has to listen in the other protocol. Which of the two fits a given tool is explained on the SOCKS5 proxies page.
How to switch
- Open My Proxies in your dashboard.
- Choose Change protocol on the proxy and pick HTTP or SOCKS5.
- Wait for the row to update, then copy the host, port, login and password again.
- Put the new values into every client that uses this order.
From code, the call is POST /orders/{order_id}/protocol with new_type set to HTTP or
SOCKS5, documented on the
Change proxy protocol page. The response
carries the updated host, port and credentials, and the Python SDK exposes the same call.
What changes and what does not
The documentation says the record is updated with the new protocol, port and credentials returned after the switch, and that the proxy may briefly be unavailable while it switches. Plan it for a quiet moment, and do not run a long job across it.
The address is the one issued for the order. Section 2.5 of the Terms of Service says the IP is not replaced during the period you paid for, and a switch does not start a new order.
If it stops working after the switch
Most failures come from a mismatch: the order is on one protocol and the client is set to the other, or the client still holds the old port. Compare the row with the client’s settings, as proxy not working describes. To see which protocol the proxy answers on now, paste the new details into our proxy checker with the protocol on Auto: the result names the one that worked. A client that keeps asking for a password may have been set to a protocol that cannot send one; the post on proxy authentication lists which clients can do what over SOCKS5, and error 407 covers a refused sign-in.
For two worked setups, see SOCKS5 in Telegram and a proxy on iPhone. The Telegram guide starts with this switch; the iPhone guide needs it only for an app that takes SOCKS5.
