> ## Documentation Index
> Fetch the complete documentation index at: https://help.miyaip.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Find your proxy server address, port, and settings

> Find proxy server settings on Windows, macOS, iOS, Android, Linux, and browsers, then check the host, port, protocol, authentication, and PAC URL.

A proxy address identifies the client's entry point. Check its port, protocol, and authentication together. An IP-reporting service returns the observed exit, which may be a different address. [Source: MiyaIP proxy address guide](https://miyaip.com/blog/proxy-server-address).

## Enter each field separately

These are placeholders. Use your dashboard's actual generated values.

| Field | Example | How to enter it |
| - | - | - |
| Host | `PROXY_HOST` | Hostname or IP only in a separate host field |
| Port | `PROXY_PORT` | The supplied number; do not infer it |
| Protocol | `http://` or `socks5h://` | A mode supported by both service and client |
| Username | `PROXY_USERNAME` | The complete generated value, including generated targeting or session parameters |
| Password | `PROXY_PASSWORD` | The proxy password |
| PAC URL | `https://example.com/proxy.pac` | The supplied URL, only in an automatic configuration field |

Do not combine separate **Server** and **Port** fields into a URL. Assemble a URI only when the client explicitly requests one. The PAC example is not a MiyaIP configuration URL.

An HTTP proxy can use CONNECT for HTTPS destinations. An HTTPS target does not require an `https://` proxy entry, and a port number does not establish the protocol. See [protocols](/guides/protocols) for SOCKS5 hostname-resolution modes.

## Find the active configuration

<Steps>
  <Step title="Identify what controls the connection">
    Check whether the application uses system settings, a dedicated client, browser settings, environment variables, or managed policy. If it selects **Use system proxy settings**, inspect the operating system.

    Dashboard output describes how to connect. Existing system settings describe what is currently saved. They can differ.
  </Step>

  <Step title="Inspect the matching settings">
    Use the platform paths below to identify **Manual**, **Automatic/PAC**, or **Auto-detect** mode. Manual mode exposes a host and port. PAC exposes a configuration URL. Discovery may not expose one fixed address.

    Check exceptions and application-specific overrides as well.
  </Step>

  <Step title="Compare with dashboard output">
    Compare the host, port, protocol, username, and password. Preserve the complete generated username for dynamic proxies and reuse the same fields when checking a session.

    Test ordinary browsing, the observed exit, and your actual application. Follow [rotation and sessions](/guides/rotation-sessions) and [latency testing](/guides/latency).
  </Step>
</Steps>

### Windows

Open **Settings → Network & internet → Proxy**. Inspect **Manual proxy setup**, **Use setup script**, **Automatically detect settings**, and exceptions. VPN connections can have separate settings. See [Microsoft's guide](https://support.microsoft.com/en-us/windows/experience/connectivity-networking/use-a-proxy-server-in-windows).

### macOS

Open **Apple menu → System Settings → Network → the active service → Details → Proxies**. Inspect HTTP, HTTPS, SOCKS, automatic configuration, and bypass lists. PAC mode shows a URL; manual mode shows a server and port. See [Apple's guide](https://support.apple.com/en-kw/guide/mac-help/mchlp2591/mac).

### iOS and Android

iOS: **Settings → Wi-Fi → ⓘ next to the current network → Configure Proxy**. Android/Pixel: **Settings → Network & internet → Internet → the network → Edit → Advanced options → Proxy**. Manufacturer labels vary. See [Wi-Fi setup](/guides/wifi) for operations and authentication scope.

### Firefox

Open **Settings** and find the path available in your version:

* **General → Network Settings/Proxy settings → Settings/Configure proxy**.
* **Privacy & Security → Connection and software security → Advanced settings → Proxy settings → Configure proxy**.

Inspect **No proxy**, **Auto-detect**, **Use system proxy settings**, **Manual proxy configuration**, or **Automatic proxy configuration URL**. The dialog also identifies extensions controlling the connection. See [Mozilla's guide](https://support.mozilla.org/en-US/kb/connection-settings-firefox).

### Edge and Chromium browsers

Edge uses system network settings by default. Inspect the system settings first, then any startup arguments, managed policy, or extensions overriding them. See [Microsoft's Edge proxy documentation](https://learn.microsoft.com/en-us/deployedge/edge-learnmore-cmdline-options-proxy-settings).

### Linux and command-line applications

In GNOME, open **Network → Network Proxy** and inspect **None**, **Manual**, or **Automatic**. Manual mode stores addresses and ports by protocol. Automatic mode stores a configuration URL. See [GNOME's guide](https://help.gnome.org/gnome-help/net-proxy.html).

Command-line applications may read `http_proxy`, `HTTPS_PROXY`, `ALL_PROXY`, and `NO_PROXY`. Inspect the application's launch environment as well as desktop settings. Empty variables do not establish that browsers or dedicated clients have no proxy. Keep credential-bearing values out of shared records. See the [curl manual](https://curl.se/docs/manpage.html).

## Keep the entry and exit separate

Record the configured host and observed public IP separately. A gateway can select different exits; see [backconnect gateways](/guides/backconnect). For static proxies, compare the purchased static IP and intended location in your dashboard. Do not substitute the gateway's resolved address for exit verification.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.