Manage Proxies Print

  • proxy, manage
  • 0

Medusa Panel › Proxy › Manage Proxies

Manage Proxies lists every source proxy in the deployment in a single searchable table, together with the latest result of the engine online check for each one. From here you can review proxy health, open a proxy to edit it, delete proxies, and import a batch of proxies from a file.

The proxy table

Each row is one proxy. The columns are:

  • ID — the internal identifier of the proxy record.
  • Name — the label you gave the proxy.
  • Type — the protocol in upper case (HTTP, HTTPS, SOCKS4 or SOCKS5).
  • Country — the country the proxy exit address was geolocated to during the last check.
  • Host and Port — the proxy address.
  • Username — the login name, if one was set.
  • Password — this column is present for parity but the stored secret is never printed to the page; the value stays hidden.
  • Last Check — how long ago the online check last ran, shown as a relative time such as 5 minutes ago, or Never if it has not been checked yet.
  • Status — ONLINE or OFFLINE. When a check failed, the error text is available as a tooltip on the status.
  • Streams — how many streams currently use this proxy.

The table supports per-column search and sorting, and remembers your column preferences. In a multi-server deployment the check result shown is the one from the local server when it exists, otherwise the result from the lowest-numbered server that has checked the proxy.

Sort by Status to bring every OFFLINE proxy to the top, then hover the status to read why a check failed before you decide whether to fix or remove the proxy.

Row actions

  • Settings — opens the proxy in the Add Proxy form in edit mode, where you can change any field. Leaving the password blank there keeps the current secret.
  • Delete — removes the proxy. Deleting also detaches it from every stream that referenced it, so those streams revert to connecting without it.

Mass actions

Use the selection checkboxes and the toolbar above the table to act on several proxies at once. The mass menu offers Mass Delete for the selected rows and Import Proxies, which opens the import dialog described below.

Importing proxies

The Import Proxies dialog accepts a TXT or JSON file, up to 2 MiB and up to 10,000 proxies. Two buttons control what happens: Dry Run parses and validates the file and reports how many proxies are valid without saving anything, and Import creates the records. If any record fails to save, the newly created ones are rolled back so the import is all-or-nothing.

A TXT file holds one proxy per line. Each line may be a full URL, a host:port pair, or host:port:user:password. A comment line that begins with # names the proxy on the next line; a comment placed after a proxy on the same line names that proxy. Lines without a name are named after their host:port.

# New York SOCKS
socks5://user:password@ny.example.com:1080
http://edge.example.com:8080
# Backup HTTP
proxy.example.com:3128

A JSON file holds an array of proxies, or an object with a proxies array. Each entry uses either a single url field or separate type, host, port, username and password fields, but not both. The name field is optional; when it is absent the proxy is named after its host:port. Supported types are http, https, socks4 and socks5.

{
  "proxies": [
    {"name": "NY SOCKS", "url": "socks5://user:password@ny.example.com:1080"},
    {"name": "Backup", "type": "http", "host": "edge.example.com", "port": 8080}
  ]
}
Run a Dry Run first on any unfamiliar file. It tells you exactly how many entries parsed cleanly, so a malformed line is caught before anything is written.

Related


Was this answer helpful?

« Back