A static residential proxy gives your browser or application a stable ISP-associated exit IP. This tutorial shows how to choose a location, collect the connection fields, configure a browser or script, verify the exit IP, and troubleshoot common failures.
Before you start
You need an active static residential proxy, its protocol, host, port, username, password, and intended location. MIYAIP's current documentation uses the common host:port:username:password field order and supports HTTP and SOCKS5. Your client may ask for the four fields separately.
Do not paste real proxy credentials into screenshots, tickets, source control, or shared chat. For scripts, load them from environment variables or a secret manager.
Step-by-step setup
1. Choose the IP location and subscription period
Select the country or state that matches your authorized workload. Static residential proxies are intended to keep the same exit identity for a longer period; MIYAIP currently presents 30-, 60-, and 360-day cycles. Confirm live inventory, final price, and expiry in the dashboard before buying.
2. Copy the connection fields
Open the purchased static-proxy list and copy the protocol, host, port, username, and password. If the dashboard exports one colon-separated line, interpret it in this order:
PROXY_HOST:PROXY_PORT:PROXY_USER:PROXY_PASSWORDKeep the value private. If the password contains characters such as @ or :, prefer a client with separate credential fields or follow that client's escaping rules.
3. Configure a browser or proxy-aware client
Create a new browser profile or environment, select the protocol shown in the dashboard, and enter host, port, username, and password into their matching fields. MIYAIP's desktop example uses SOCKS5 in a fingerprint-browser profile and recommends running the built-in proxy check before opening the environment.
If your local network requires a relay gateway, select the provider-recommended gateway. Disable other system-wide proxy or VPN tools while testing so routes do not conflict.
4. Test the proxy with curl
Test an HTTP proxy with separate proxy authentication fields:
curl --proxy "http://PROXY_HOST:PROXY_PORT" \ --proxy-user "PROXY_USER:PROXY_PASSWORD" \ https://api.ipify.orgFor SOCKS5 with target hostname resolution through the proxy:
curl --proxy "socks5h://PROXY_HOST:PROXY_PORT" \ --proxy-user "PROXY_USER:PROXY_PASSWORD" \ https://api.ipify.orgOn Windows, use curl.exe if PowerShell maps curl to another command. Do not leave real credentials in terminal history on a shared computer.
5. Connect from Python
Store credentials in environment variables and pass the proxy URL to requests:
import os import requests from urllib.parse import quote user = quote(os.environ["PROXY_USER"], safe="") password = quote(os.environ["PROXY_PASSWORD"], safe="") host = os.environ["PROXY_HOST"] port = os.environ["PROXY_PORT"] proxy_url = f"http://{user}:{password}@{host}:{port}" proxies = {"http": proxy_url, "https": proxy_url} response = requests.get( "https://api.ipify.org?format=json", proxies=proxies, timeout=20, ) response.raise_for_status() print(response.json())For SOCKS5 in Python, use a library build that supports SOCKS and follow its documented proxy URL format.
6. Verify IP, location, and stability
Compare the returned exit IP with the purchased proxy record, then verify the country or state using an approved IP-check service. Repeat the check from the same profile after reconnecting: the assigned exit IP should remain stable during the active subscription unless the provider replaces or refreshes it.
Do not judge success only by a page loading. Also confirm the expected IP, protocol, DNS behavior, and target-site permissions.
7. Monitor expiry and troubleshoot
If the proxy stops working, confirm that it has not expired; recheck protocol, host, port, credentials, and field order; rerun the client test or curl command; disable conflicting VPN or forwarding rules; and try the provider-recommended gateway.
A 407 Proxy Authentication Required response usually points to credentials or an IP allowlist. Contact support with a timestamp and sanitized error message, never the full password. MIYAIP notes that expired proxies stop working and that a long-expired IP may be better replaced than renewed.
Frequently asked questions
Should I choose HTTP or SOCKS5?
Choose the protocol your application supports and the provider exposes for that endpoint. HTTP works well for browser and web-request traffic. SOCKS5 is more general, and socks5h in curl can resolve the target hostname through the proxy.
Why does the exit IP not match the purchased IP?
Common causes are a wrong gateway, incorrect protocol or credential format, another VPN or proxy taking precedence, or a local forwarding-port conflict. Test with one client and one route before adding more layers.
Will a static residential IP stay unchanged forever?
No. It should remain stable during the active plan, but it can expire, be replaced for operational reasons, or be refreshed under a provider policy. Monitor the dashboard and plan renewals before expiry.
Can I share one proxy across many environments?
Check the provider's concurrency and usage rules. Even when technically possible, reusing one identity across unrelated accounts can create security and operational risk. Keep environments isolated and follow both service and target-site policies.
Start with one verified static IP
Configure one endpoint, verify its exit IP and location, and run a small authorized workload before scaling to more profiles or applications.
