+- Proxy Community (https://proxycommunity.com/forum)
+-- Forum: Technical Community Support (https://proxycommunity.com/forum/forum-technical-community-support)
+--- Forum: API and Development (https://proxycommunity.com/forum/forum-api-and-development)
+--- Thread: How to Set Up and Use a Proxy with wget? Need Help with wget Proxy Configuration! Alternatively, for a more (/thread-how-to-set-up-and-use-a-proxy-with-wget-need-help-with-wget-proxy-configuration-alternatively-for-a-more--6878)
How to Set Up and Use a Proxy with wget? Need Help with wget Proxy Configuration! Alternatively, for a more - ghostDrift77 - 27-04-2024
"Best Way to Configure wget Proxy? Running Into Issues!"
Hey folks!
Trying to set up a wget proxy but hitting a wall. I added `http_proxy` and `https_proxy` in my `.bashrc`, but wget still ignores it?
Also tried `--proxy=on` and `--proxy-user`, but no luck. Am I missing something obvious?
Running:
`wget --proxy=user:pass@proxy:port http://example.com`
Getting timeouts or auth errors. Proxy works fine with curl, so it's gotta be my wget proxy setup.
Any tips? Maybe a config file tweak?
Thanks in advance!
“” - webDrifterX - 03-01-2025
Hey! Had the same issue last week. Turns out wget proxy settings can be finicky.
Try adding this to `/etc/wgetrc` or `~/.wgetrc`:
```
use_proxy=yes
http_proxy=http://user:pass@proxy:port
https_proxy=http://user:pass@proxy:port
```
Restart your terminal and test. Also, double-check your proxy URL format—sometimes `http://` is needed even for HTTPS.
“” - cloakPioneer77 - 06-01-2025
Dude, wget proxy auth is a pain. If you’re getting timeouts, maybe your proxy’s blocking the request?
Try `--proxy-user` and `--proxy-password` separately instead of cramming it all in one flag. Like:
```
wget --proxy=on --proxy-user=user --proxy-password=pass http://example.com
```
If that fails, maybe check `strace wget` to see where it’s choking.
“” - maskedCircuitX - 21-01-2025
For wget proxy issues, I always fall back to `env` vars. Run:
```
env http_proxy=http://user:pass@proxy:port https_proxy=http://user:pass@proxy:port wget http://example.com
```
If that works, your `.bashrc` isn’t being sourced right. Maybe `source ~/.bashrc` or reboot?
“” - darkStormX - 04-02-2025
Weirdly, wget ignores env vars sometimes. Try `--no-check-certificate` if it’s an HTTPS thing.
Also, this tool helped me debug proxy stuff: [ProxyChecker](https://example.com/proxychecker). Just sayin’.
“” - darkTorX - 13-02-2025
Yo! Had this exact wget proxy headache. Your command looks right, but maybe the proxy’s picky about auth.
Try `--proxy-type=http` or `--proxy-type=https` explicitly. Some proxies freak out if you don’t specify.
“” - ghostDrift77 - 25-02-2025
OP here. Whoa, thanks for all the tips!
Tried the `/etc/wgetrc` tweak and `--proxy-type=http`—still timing out. But `strace wget` showed it’s not even hitting the proxy?
Weird, ‘cause curl flies through. Gonna test with `nc` like someone suggested. Maybe the port’s blocked.
Also, that ProxyChecker site was clutch. Thanks y’all!
“” - stealthRushX88 - 28-02-2025
If curl works but wget proxy fails, it’s probably a config clash. Check if you have a `~/.wgetrc` overriding things.
Run `wget --debug` to see where it’s failing. Might reveal if it’s even trying the proxy.
“” - secureCipherX - 11-03-2025
Pro tip: Test with a simple proxy first, like `http_proxy=http://localhost:8080`. If that works, your corp proxy’s the issue.
Also, `nc -vz proxy port` to verify the proxy’s even reachable.
“” - darkCipher99 - 30-03-2025
Wget proxy settings can be weird with auth. Try URL-encoding your password if it has special chars.
Like, `user:pass%40@proxy` instead of `user:pass@proxy`.