Authentication
Every NyxonProxies plan authenticates with a username and password. Where to find them, how clients send them, how to change the password and what a 407 means.
NyxonProxies authenticates every connection with the username and password of your plan. There is no IP whitelist to maintain: the same credentials work from your laptop, a server, a phone or a cloud function, and on both the HTTP and the SOCKS5 port.
Where to find your credentials
Open My plans in the dashboard and click the plan. The Connection card shows the host, the HTTP port, the SOCKS5 port, the username and the password, plus a ready-to-use user:pass@host:port line. Each plan has its own pair, so two plans never share a login.
The proxy generator builds full lines from the same pair, with targeting and session parameters added to the username.
How clients send them
You almost never build the authentication yourself. Put the credentials in the proxy URL and the client does the rest:
http://USERNAME:[email protected]:8080
socks5://USERNAME:[email protected]:1080On the HTTP port the client sends a Proxy-Authorization: Basic header, which is the Base64 of username:password. On the SOCKS5 port it uses the SOCKS5 username and password method. Both carry exactly the same values.
Apps with a form, such as browsers, antidetect tools and phones, have separate Username and Password fields. Paste the values there and leave the host and port fields without credentials.
Parameters live in the username
Targeting and sessions are added to the username, never to the password:
USERNAME-country-us-session-a1b2c3d4-time-30The gateway reads USERNAME as your login and the rest as instructions for that connection. See Username parameters for the full list. The password always stays exactly as shown on the plan.
Special characters in passwords
A password with characters such as @, :, / or # breaks a proxy URL, because those characters have a meaning there. Either percent-encode them (@ becomes %40, : becomes %3A) or pass the username and password as separate options, which most libraries support. The code guides show both ways, for example Python Requests and Node.js.
The simplest fix is a password made only of letters and digits. You can set one yourself, see the next section.
Change the proxy password
On the plan page, click Change password on the Connection card and enter the new proxy password (at least 4 characters). Dedicated ISP plans keep fixed credentials, so they have no such button. This changes the password of that plan only, not the password you use to sign in to the dashboard. Update every tool that uses the plan after you change it, because the old password stops working.
What a 407 means
407 Proxy Authentication Required is the gateway saying it did not accept the credentials. Check these in order:
- No typo, and no space copied along with the username or password.
- The host matches the plan's product. Each product has its own gateway, see Endpoints and ports.
- Special characters in the password are encoded, or passed as a separate option.
- The tool uses the current password, not a copy from before a change.
- The plan is still active in My plans: it has traffic left and has not expired.
More status codes and what to do about them are in Error codes.
Last updated
Still stuck?
People answer the live chat around the clock. Send the proxy line you used (without the password) and the error you see.