Fix a profile that won’t start with a proxy

Before opening a browser with an assigned proxy, MaskPilot uses the actual route for that launch to confirm the current exit information and time zone. This keeps the browser environment aligned with the real exit.

If a valid result cannot be obtained, MaskPilot stops that launch instead of falling back to a previously saved exit or time zone. This prevents the browser from continuing with mismatched environment settings after a proxy changes.

Why can launch fail after a successful connection check?

The normal connection check and the pre-launch exit check happen at different times and validate different results. Any of these changes can cause a later launch to fail:

• The node stopped working, expired, or changed credentials after the earlier check.
• The proxy can connect but cannot reach the HTTPS service needed to determine the exit.
• DNS, VPN, firewall, or corporate network policy changed between the two actions.
• One hop in a multi-hop route failed or began restricting the next hop.
• The exit service returned incomplete information without a usable time zone.

Troubleshoot in order

1. Return to Proxies and run “Check connection” on the assigned entry proxy.
2. If it has an upstream proxy, also run “Check full connection.”
3. Confirm that the proxy has not expired and that its credentials and source IP allowlist remain valid.
4. Confirm that the device can resolve domains and that the proxy permits HTTPS access.
5. Pause other VPN, accelerator, or security software that rewrites routes or DNS, then retest.
6. If the launch still fails, assign another known-good proxy and try again to distinguish a node problem from the current device network.

If an advanced proxy reports an invalid configuration, import the latest configuration from the provider. Advanced connection fields cannot be edited in place.

Additional checks for a multi-hop route

The profile is assigned to the entry proxy, but launch uses its complete upstream route. Even when the entry node can connect, any unavailable later hop prevents launch.

Do not rely only on separate standard checks for each node. Run “Check full connection” from the entry proxy, address the first failing hop shown on the page, and then check the entire route again.

Temporarily switch to direct connection

You can switch the profile to “Direct connection” to determine whether the route causes the failure, but this changes the profile’s network exit. Do not continue to the target website when the exit is not the one you intended. After troubleshooting, assign the correct proxy again and verify its exit.

Prepare before contacting support

Record these details to reduce back-and-forth troubleshooting:

• The error message shown on the page.
• The approximate time of the failure.
• Results from both the connection and full-route checks.
• Whether the proxy is standard or advanced, and the number of hops.
• Whether the device also uses a VPN, firewall, or corporate proxy.

Redact usernames, passwords, and keys in advanced configurations. Do not send complete credentials.