Keep the mapping one-to-one
Record which profile uses which endpoint before starting. One endpoint per profile keeps session history consistent across restarts and handoffs.
Guzzle proxy setup
How to set up a proxy in Guzzle
Configure a NobleProxy dedicated static residential proxy in Guzzle with the exact fields the app asks for, then run its connection check before real tasks.
Quick answer
Add your NobleProxy host, port, username, and password to Guzzle's proxy settings, choose HTTP or SOCKS5, save, and run the built-in proxy check before starting tasks.
Exact field-by-field setup
HTTP and SOCKS5 supported
One proxy per profile
Connection check before tasks
When this is the right fit
- Exact field-by-field setup
- HTTP and SOCKS5 supported
- One proxy per profile
Who this page is for
Configure a NobleProxy dedicated static residential proxy in Guzzle with the exact fields the app asks for, then run its connection check before real tasks.
Add your NobleProxy host, port, username, and password to Guzzle's proxy settings, choose HTTP or SOCKS5, save, and run the built-in proxy check before starting tasks.
Guzzle proxy fields
| Proxy type / protocol | HTTP or SOCKS5 - both supported on every NobleProxy endpoint |
|---|---|
| Host / endpoint | The host exactly as issued in your NobleProxy dashboard |
| Port | The port paired with your endpoint in the dashboard |
| Username | Your NobleProxy credential (case sensitive) |
| Password | Your NobleProxy credential (case sensitive) |
| Static or rotating | Static - the same exit IP every session by design |
Field labels vary slightly between versions; the NobleProxy values never change.
Step-by-step: connect Guzzle to NobleProxy
- 1
Set the proxy option
'proxy' => 'http://username:password@host:port' in the request or client config.
- 2
One client per profile
Keep one Guzzle client per endpoint.
- 3
Verify the exit IP
Request an IP echo endpoint and inspect the body.
- 4
Log failures
Catch ConnectException to separate proxy errors from target errors.
Connection check
- 1Run the tool's check after saving the proxy
- 2Confirm the reported IP is the endpoint, not your home IP
- 3Load one real target page and confirm it renders
Working connection
The tool reports the endpoint IP or country and target pages load normally.
Broken connection
Refused connections, timeouts, or repeated credential prompts mean the host, port, username, or password does not match the dashboard exactly.
Sources
- NobleProxy product factsConnection model, protocols, and credentials(checked 2026-09-01)
- Guzzle official documentationGuzzle request options: proxy(checked 2026-09-01)
Facts last reviewed 2026-09-01.
195+ countries
99.9% uptime guarantee
Unlimited bandwidth
4.9/5 from 127 ratings
Frequently asked questions
Which proxy protocols does Guzzle support?
NobleProxy endpoints support HTTP and SOCKS5; use whichever the tool asks for. Both use the same host, port, username, and password.
Should each Guzzle profile have its own proxy?
Yes. One dedicated static residential proxy per profile keeps session history consistent and unlinks unrelated profiles.
Choose one stable proxy for every active profile
Buy self-serve now, or talk with us about a larger agency inventory.