Get your connection details
Open your Residential or Datacenter access in the dashboard, then its configuration tab. Select the protocol shown here, your country and session settings.
- 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
Open a terminal. Use curl.exe on Windows if curl is an alias for another shell tool.
Replace HOST, PORT, LOGIN and PASSWORD with the dashboard's HTTP connection details.
Run the command. For SOCKS5 use socks5h:// and the SOCKS5 port from the dashboard.
curl --proxy "http://HOST:PORT" --proxy-user "LOGIN:PASSWORD" --connect-timeout 15 --max-time 30 "https://api.ipify.org?format=json"The example contains placeholders. Do not publish a command containing your password; store credentials in private configuration for recurring scripts.
Test the connection
The response should contain the proxy's public IP. A 407 indicates an HTTP authentication issue; for a timeout check the host, port and protocol.
Turn the proxy off
Remove --proxy and --proxy-user from the next request.
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