Get your connection details
Open your Residential, Datacenter, ISP or IPv4 access in the dashboard, then its configuration tab. Select the protocol shown here, your country and session settings.
- Static ISP
- Dedicated residential ISP IP with unlimited bandwidth — from $1.90 / ≈ $1.94 per IP (from 7 days). Best for accounts, profiles and messengers.
- Rotating Residential
- 183 countries, cities and ASNs, rotating or sticky up to 30 min — from $0.60 / ≈ $0.60 per GB. Traffic never expires.
- Rotating Datacenter
- 65 countries, up to 1 Gbps speed, sticky up to 24 h — from $0.40 / ≈ $0.40 per GB. Built for scraping and automation.
- Dedicated IPv4
- Dedicated datacenter IPv4 with one tenant and unlimited bandwidth — from $1.40 / ≈ $1.44 per IP.
- host
- Server address
- port
- Port for this protocol
- login
- Proxy username
- password
- Proxy password
Copy the fields separately. Proxy credentials are different from your Proxly account login. After changing the location, copy the updated proxy username again.
Open your connectionConnect the app
For terminal and CLI tools, export HTTP_PROXY and HTTPS_PROXY using http://LOGIN:PASSWORD@HOST:PORT from your Proxly dashboard.
For GNOME desktop (Ubuntu), open Settings → Network → Network Proxy → Manual and enter the HTTP/HTTPS host and port.
Verify the external IP by running curl https://api.ipify.org.
export HTTP_PROXY="http://LOGIN:PASSWORD@HOST:PORT"
export HTTPS_PROXY="http://LOGIN:PASSWORD@HOST:PORT"
curl -sS "https://api.ipify.org?format=json"If you use IP whitelisting on a Linux server, add your server's public IPv4 in the Whitelist tab of the Proxly dashboard.
Test the connection
Run curl api.ipify.org — the output should return the proxy IP.
Turn the proxy off
Run unset HTTP_PROXY HTTPS_PROXY ALL_PROXY in the terminal or set Network Proxy to Disabled.
If the connection fails
Authentication error
Recopy the proxy credentials. Include the full username with location and session settings. HTTP status 407 means proxy authentication was not accepted.
Connection timeout
Check the dashboard host and the port for the selected protocol. Make sure the access has remaining data. Use HTTP for Chromium with username and password.
The IP did not change
Check the IP inside the configured app or browser profile. Make sure the test site is not excluded from the proxy. Telegram does not change your regular browser IP.
Still having trouble? Contact support