> ## 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.

# Wi-Fi proxy setup on iPhone, Android, Windows, and Mac

> Configure manual or PAC proxy settings on iOS, Android, Windows, and macOS, then verify browser routing, authentication, and the actual exit IP.

Connect to a working network before setting the proxy. Mobile Wi-Fi settings usually belong to the selected network. Windows uses system proxy settings, while macOS uses the selected network service. Applications must honor those settings to use the proxy. [Source: MiyaIP Wi-Fi proxy guide](https://miyaip.com/blog/proxy-on-wifi).

## Prepare the connection details

Copy the host, port, protocol, and required username and password from your dashboard. **Manual** mode takes a proxy host and port. **Automatic/PAC** mode takes the supplied PAC URL. A PAC script chooses a proxy or direct route for a destination; a gateway hostname is not a PAC URL.

Protocol and authentication support vary by platform. If there are no credential fields, use an application or client supporting the required authentication. Do not put credentials in the **Server** field. PAC does not automatically authenticate every application.

## iPhone and iPad

<Steps>
  <Step title="Open the connected Wi-Fi network">
    Go to **Settings → Wi-Fi** and tap **ⓘ** next to the connected network. Find **HTTP Proxy → Configure Proxy**.
  </Step>

  <Step title="Select the configuration mode">
    For **Manual**, enter **Server** and **Port** separately. If **Authentication** is available and required, enable it and enter the proxy username and password.

    For **Automatic**, enter the supplied PAC URL. This screen configures an HTTP proxy. Use a SOCKS5-capable client for SOCKS5 access.
  </Step>

  <Step title="Save and test">
    Save, then test the browser and your actual application on this Wi-Fi network. Check each new Wi-Fi network separately. Recheck routing after switching to cellular data.
  </Step>
</Steps>

See [Apple's iPhone Wi-Fi guide](https://support.apple.com/en-gb/guide/iphone/iphw5gjwl8k2/ios). An organization-managed global proxy has a different scope.

## Android

<Steps>
  <Step title="Open advanced network settings">
    On Pixel, open **Settings → Network & internet → Internet → the Wi-Fi network → Edit → Advanced options**. Other manufacturers may use different network labels.
  </Step>

  <Step title="Select the proxy type">
    Open **Proxy** and choose the available **Manual** or **Automatic/PAC** mode. Enter the host and port for manual setup, or the PAC URL for automatic setup.

    If this screen has no authentication fields and your proxy requires credentials, use a supporting application or client. Do not embed the password in the hostname or enter SOCKS5 details as HTTP settings.
  </Step>

  <Step title="Save and verify">
    Tap **Save**. Confirm that the edited Wi-Fi network is still active, then test the browser and actual application. Recheck after changing Wi-Fi networks or switching to cellular data.
  </Step>
</Steps>

See [Google's Pixel network settings](https://support.google.com/pixelphone/answer/9655181?hl=en) for the path and device differences.

## Windows 10 and 11

<Steps>
  <Step title="Open system proxy settings">
    Go to **Settings → Network & internet → Proxy**. Applications honoring these settings can use them over Wi-Fi or Ethernet.
  </Step>

  <Step title="Configure the server or script">
    Manual setup: under **Manual proxy setup → Use a proxy server → Set up**, enable the setting, enter **Proxy IP address** and **Port**, review exceptions, and select **Save**.

    PAC setup: under **Automatic proxy setup → Use setup script → Set up**, enable the script, enter **Script address**, and **Save**. Use **Automatically detect settings** only when your network supplies discovery configuration.
  </Step>

  <Step title="Check protocol and authentication support">
    The manual server field is not a general SOCKS5 client. Use the supplied HTTP configuration; configure SOCKS5 or application-specific authentication in a supporting client.

    If the application displays proxy authentication, enter the proxy account rather than your Windows account. If no authentication interface exists, check that application's proxy support.
  </Step>
</Steps>

See [Microsoft's Windows proxy guide](https://support.microsoft.com/en-us/windows/experience/connectivity-networking/use-a-proxy-server-in-windows). A VPN connection can have separate proxy settings.

## macOS

<Steps>
  <Step title="Select the active network service">
    Open **Apple menu → System Settings → Network**. Select the active **Wi-Fi** or other network service, then **Details → Proxies**.
  </Step>

  <Step title="Configure the required mode">
    Select **Web proxy (HTTP)**, **Secure web proxy (HTTPS)**, or **SOCKS proxy** as required by the service and client. Enter the server and port. If required, enable **Proxy server requires password** and enter the credentials.

    For PAC, enable **Automatic proxy configuration** and enter its URL. Discovery and manual addressing are separate modes. An HTTPS destination alone does not determine the gateway's connection protocol.
  </Step>

  <Step title="Review exceptions and save">
    Check bypassed hosts and domains, then save. When changing network services, inspect the proxy options for the new service.
  </Step>
</Steps>

See [Apple's Mac proxy settings](https://support.apple.com/en-kw/guide/mac-help/mchlp2591/mac) for field definitions.

## Verify and troubleshoot

<Steps>
  <Step title="Check the saved settings">
    Confirm the active network, host, port, mode, authentication, and PAC URL. Check whether an exception sends the test destination directly.
  </Step>

  <Step title="Test browsing and the exit">
    Open an ordinary HTTPS page, then inspect the exit using [whoer.net](https://whoer.net/) or another IP-reporting service. For dynamic proxies, check the selected location. For static proxies, compare the purchased static IP and location in your dashboard. The entry hostname and exit IP can differ; see [backconnect gateways](/guides/backconnect).
  </Step>

  <Step title="Test the actual application">
    Use the same network to test your intended application. Browser success does not establish that other applications follow system settings. Use the [latency test](/guides/latency) when you need request timings.
  </Step>

  <Step title="Isolate connection failures">
    If enabling the proxy stops access, temporarily disable this proxy setting and test ordinary browsing. If direct access returns, check the endpoint, authentication, protocol, and PAC. If the public IP stays unchanged, inspect the active network, application support, and bypass rules.
  </Step>
</Steps>


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