Endpoints and ports

Each product has its own gateway host. Your plan's username and password work on that product's host only, on either of its two ports: one for HTTP proxying and one for SOCKS5. The dashboard shows the right values on the plan page and fills them in for you in the proxy generator.

Hosts and ports#

Residential and Mobile share a host and ports. Which pool a connection uses is decided by the plan the credentials belong to, so you never have to pick it yourself.

Unlimited Residential takes HTTP and SOCKS5 on the same port, 10507. The protocol in the proxy URL tells the gateway which one you speak.

On geo.gw.nyxon.sh the two ports are strict: 8080 only speaks HTTP and 1080 only speaks SOCKS5. A socks5:// URL on port 8080 fails, so match the port to the protocol.

Dedicated ISP plans use the host, port and credentials shown on the plan page, because the IPs are assigned to you individually.

Which port to use#

• HTTP port: for websites and APIs, over both http:// and https://. HTTPS goes through an encrypted tunnel, so the gateway never sees the content.
• SOCKS5 port: for anything that speaks SOCKS5, including tools that are not web clients, such as Telegram or some game and mail clients.

If a tool offers both, either works. The details are in HTTP, HTTPS and SOCKS5.

A full line for each product#

These are rotating lines with no targeting, the shortest form that works. Replace USERNAME and PASSWORD with the values from the plan.

http://USERNAME:[email protected]:8080
http://USERNAME:[email protected]:6969
http://USERNAME:[email protected]:777
http://USERNAME:[email protected]:30
http://USERNAME:[email protected]:30
http://USERNAME:[email protected]:50
http://USERNAME:[email protected]:10507
socks5://USERNAME:[email protected]:1080

Firewalls and outbound ports#

Your machine connects out to the gateway on the port of the product. Some office networks, schools, hotel Wi-Fi and cloud firewalls only allow common ports such as 80 and 443, so ports like 30, 50, 666 or 777 can be blocked on the way out. The usual symptom is a timeout, not an error page.

To check whether the port is reachable at all, run this from the machine that will use the proxy:

nc -vz dc.gw.nyxon.sh 777

Test-NetConnection dc.gw.nyxon.sh -Port 777

A successful TCP connection means the path is open and any remaining problem is in the credentials or the client settings. If it fails, allow the port in the firewall or try from another network.

DNS and IP version#

The gateway hostnames resolve to IPv4 addresses, so your machine reaches them over IPv4. On the IPv6 products only the exit side uses IPv6: you do not need IPv6 on your own connection. See IPv6 Residential and IPv6 Datacenter.

Use the hostnames, not the IP addresses they resolve to today. The addresses behind a hostname can change.