Skip to content

Polygate 0.6.3

Choose a tag to compare

@B3hnamR B3hnamR released this 13 Nov 16:57

Polygate 0.6.3

New: Psiphon as a route

Tick the regions you want under Routing → Psiphon and press Connect. Polygate runs Psiphon's own client once for each region, each on its own local SOCKS port, and together they work as one route named Psiphon. Only the gateway's own requests use it; nothing on the machine changes.

  • Take turns or stay on one region. Each request uses the next connected region (round robin), or every request stays on the region you pick.
  • Used-up exits are skipped. When OpenCode Free says a region's exit has used up its daily allowance, or Kilo says it has reached its per-address limit, the request goes on through the next region. The exit is skipped for that provider only; other providers keep using it.
  • New addresses, checked first. A used-up region reconnects for a new address, and Polygate checks it with the same provider before it carries that provider's requests again. On by default; at most three new addresses an hour per region.
  • Test checks every region. Test on the Psiphon route checks each connected region through its own exit and lists them, marking only the used-up ones.
  • Update servers connects once to fetch Psiphon's current servers and regions.
  • Switching it on and off. Disable and Enable on the route card disconnect and connect Psiphon. While Psiphon is the route in use it reconnects when Polygate starts, and when it stops, requests go back to the route used before it.

Polygate ships only what Psiphon needs: Psiphon Inc.'s official, unmodified client for Windows and Linux x86-64 (GPL-3.0), its client settings and the signed starting server list. No remote server-list addresses are included. Psiphon publishes no Linux arm64 client, so Psiphon is not available in the arm64 package.

Upgrading

Windows: in 0.4.2 or later, open Settings → Updates → Update & restart. Otherwise download Polygate-0.6.3-Windows-x64.exe below and use it in place of the old one. Your settings and keys are kept. The app remains unsigned.

Linux service users: connect to your server and run:

sudo polygate update

Verify checksums before installation; each file has a .sha256 beside it.