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
Set PROXLY_PROXY_URL from your connection details: http://login:password@host:port. Percent-encode special characters in the credentials.
Run the example in a terminal. The -c option enables the proxy for this command only.
Replace the HTTPS URL with your repository. ls-remote reads references without changing the repository.
git -c http.proxy="$PROXLY_PROXY_URL" ls-remote https://github.com/git/git.git HEADhttp.proxy applies to HTTP/HTTPS. SSH remotes such as git@host require another setup. Keep credentials out of command history.
Test the connection
The command should return the HEAD hash. To check the exit IP, test the same proxy using the cURL guide.
Turn the proxy off
Run the next command without -c http.proxy. Existing proxy environment variables may still apply.
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