Multilogin

Use NyxonProxies as a custom proxy in Multilogin X profiles: protocol, the host:port:login:password line, the proxy check, quick profiles and sticky sessions.

Multilogin X gives each browser profile its own fingerprint and proxy. Add NyxonProxies as a custom proxy, with a separate session for every profile.

What you need

  • Host and port of your product. For Residential: geo.gw.nyxon.sh, port 8080 for HTTP or 1080 for SOCKS5. Other products are listed in Endpoints and ports.
  • Username and password from the plan page in the dashboard, or ready-made lines from the proxy generator in the ip:port:user:pass format.

Add the proxy to a profile

  1. Create a profile, or open the settings of an existing one, and find the Proxy section.
  2. Select Custom.
  3. Choose HTTP as the protocol, or SOCKS5 for port 1080.
  4. Enter the proxy as one line in the IP:port:login:password format, with the gateway hostname in place of the IP:
text
geo.gw.nyxon.sh:8080:USERNAME-country-us-session-mlx0001-time-120:PASSWORD
  1. Wait for the automatic check. Proxy check passed means Multilogin reached the gateway and read the IP details.
  2. Save the profile and start it.

Many profiles at once

Quick on the main screen creates profiles fast. In its Proxy section, choose Custom, then Proxy list under Format, and paste up to 25 lines. Give every line its own session ID, so each profile gets its own IP.

One IP per profile

A session keeps its IP for up to 120 minutes, and a residential device can go offline sooner. The profile then continues on a new IP. For accounts that must keep one IP for weeks, use Dedicated ISP: every IP is static and yours alone. Its lines use HTTP, with the host and port shown on the plan page. See Rotating and sticky sessions.

Check the IP

Start the profile and open https://ipinfo.io/json. It should show a NyxonProxies IP in the country you targeted.

Troubleshooting

What you seeWhat to check
Proxy check failedThe protocol matches the port, the host and port belong to your product, and the username and password are correct.
The wrong countryThe country code in the username, for example -country-de.
The IP changes while you workAdd a session ID, or raise its time.

More in Troubleshooting.

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.