A step-by-step walkthrough for connecting a PROXIES.SX 4G/5G mobile proxy to a MuLogin browser profile - add a profile, open proxy settings, pick HTTP or SOCKS5, enter your credentials, test the connection, and save.
We do not have permission to embed real MuLogin screenshots here, so every mockup below is a labeled, schematic illustration built to match the flow documented by MuLogin - not an actual screen capture. Field names, tabs, and buttons follow MuLogin's own documentation, but your actual interface may look slightly different depending on version.
A MuLogin account with the client downloaded and at least one browser profile ready to configure.
Host, port, username and password from your client.proxies.sx dashboard. See how to buy proxies if you haven't bought GB yet.
That's roughly how long the six steps below take once you have your credentials in hand.
Your PROXIES.SX endpoint has four separate values. In MuLogin's example format, they look like this (values below are masked examples - use your real endpoint from the dashboard):
| Field | Example value |
|---|---|
| Host / IP address | gw.proxies.sx |
| Port | 10001 |
| Login user | user-xxxxx |
| Login password | •••••••• |
MuLogin also accepts a combined paste format, which can be faster than typing each field separately:
(select the proxy type first, then paste the four values above)
(or prefix the string with the protocol, e.g. http:// or socks5://)
Both HTTP and SOCKS5 are supported by PROXIES.SX - pick whichever protocol your dashboard endpoint shows, and use that same protocol in MuLogin.
Open the MuLogin client and click Add Browser, then select the operating system for the profile. MuLogin randomly matches a fingerprint according to the OS you choose - you don't need to change anything here just to add a proxy later.
Select operating system
Add Browser dialog - Illustration, your actual screen may differ
In the profile's Basic Configuration, open the Proxy settings tab. This is the same panel whether you're creating a new profile or editing an existing one.
Basic Configuration panel - Illustration, your actual screen may differ
Select the proxy type from the dropdown. MuLogin lists HTTP, HTTPS, SOCKS4 and SOCKS5. PROXIES.SX issues both HTTP and SOCKS5 endpoints, so pick whichever protocol your dashboard shows for the endpoint you're using.
Proxy type dropdown - Illustration, your actual screen may differ
Fill in the IP address (host), Port, Login user, and Login password from your PROXIES.SX dashboard endpoint. IP address and port are required; since PROXIES.SX endpoints are authenticated, fill in the username and password too.
Proxy fields form - Illustration, your actual screen may differ
Click Test proxy information. If MuLogin displays detailed IP information, the test passed and the profile is ready to open. If it fails, see the troubleshooting section below before saving.
Test result panel - Illustration, your actual screen may differ
Click Save to store the settings, then open the profile normally. Every MuLogin profile can carry its own proxy, so repeat steps 2 through 6 for each additional profile you want to assign a PROXIES.SX endpoint to.
Saved profile row - Illustration, your actual screen may differ
Re-check the host and port for typos, and confirm the username and password match your dashboard exactly - copy-paste rather than retype.
Confirm the endpoint you copied is the one you intended (some accounts have several endpoints in different countries) and that you have remaining GB on your PROXIES.SX plan.
A SOCKS5 endpoint set to HTTP in MuLogin (or vice versa) will fail the test. Match the proxy type dropdown to whatever protocol your dashboard endpoint uses.
Proxy settings are per profile in MuLogin - double check you entered the credentials in the profile you're actually testing, not a different one.
Verify the endpoint is active in your client.proxies.sx dashboard, then reach out via /contact if the credentials still won't connect.
Yes. MuLogin's proxy settings support HTTP, HTTPS, SOCKS4 and SOCKS5 for each browser profile, and PROXIES.SX issues both HTTP and SOCKS5 endpoints - so you pick whichever protocol matches the endpoint shown in your dashboard.
Log in to your client.proxies.sx dashboard after buying GB (see our how-to-buy-proxies guide). Each endpoint you create shows its own host, port, username and password - copy them exactly into MuLogin's proxy fields, character for character.
Yes. Proxy settings in MuLogin are stored per browser profile, not globally, so you can assign a separate PROXIES.SX endpoint - a different country, city or carrier - to each profile you run.
Re-check the host and port for typos, confirm the username and password match your dashboard exactly, make sure the protocol you selected (HTTP or SOCKS5) matches the endpoint type, and confirm the endpoint is still active with remaining GB in your account.
Yes. MuLogin accepts a combined paste format: host:port:username:password after picking the proxy type, or protocol://host:port:username:password, for example socks5://gw.proxies.sx:10001:user-xxxxx:yourpassword.
Real 4G/5G mobile and residential IPs across 90+ countries, HTTP and SOCKS5 supported, from $4/GB down to $2.40/GB at volume. Endpoints, connections and IP rotation are free.