<p>Although <code>bitcoind</code> itself only supports socks5, you can make any dynamically linked binary <code>http-proxy</code> capable with a <code>LD_PRELOAD</code>ing tool like <a href="https://github.com/haad/proxychains" rel="nofollow noreferrer">proxychains</a>:</p>
<p>The prerequisite here is that your proxy server itself
supports the <code>HTTP CONNECT</code> method to non-standard ports.</p>
<p>In my VM lab setup I  use <a href="https://mitmproxy.org/" rel="nofollow noreferrer">mitmproxy</a> on <code>192.168.100.1 8888</code>  to analyze the network traffic using this <code>/etc/proxychains.conf</code>:</p>
<pre><code>strict_chain
proxy_dns
remote_dns_subnet 224
tcp_read_time_out 15000
tcp_connect_time_out 8000
localnet 192.168.100.0/255.255.255.0
localnet 127.0.0.0/255.0.0.0
localnet ::1/128
[ProxyList]
http    192.168.100.1 8888
</code></pre>
<p>and <code>bitcoind</code> using <code>proxychains</code>:</p>
<pre class="lang-bash prettyprint-override"><code>proxychains bitcoind -testnet
</code></pre>

CC BY-SA 4.0
2022-11-25T16:06:30.663Z
2022-11-25T16:06:30.663Z
Jürgen Hötzel
<p>Bitcoin doesn't use HTTP for its communications - it has its own specific protocol that runs directly on top of TCP.  So an HTTP proxy like squid won't help.  </p>

<p>If you aren't able to make outgoing TCP connections through your firewall (mainly to destination port 8333) then you'll have to contact your corporate IT people about adding appropriate firewall rules.  The same if you want to be able to enable listening.</p>

CC BY-SA 3.0
2018-02-06T15:40:52.223Z
2018-02-06T15:40:52.223Z
Nate Eldredge
<p>I'm want to run Bitcoin Core client on TestNet and I need to config it for using under corporate proxy.
Since I'm using Squid to set proxy for my system I should set "localhost:3128" somewhere... but <strong>bitcoin-qt</strong> options seems to have only SOCK5 proxy field.</p>

<p>I also tried to set the proxy using the command line:</p>

<p><code>./bitcoin-qt --testnet -proxy=localhost:3298</code></p>

<p><a href="https://i.sstatic.net/JK3Pp.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/JK3Pp.png" alt="enter image description here"></a></p>

<p>...but it doesn't work.</p>

<p>How can I solve? Can I run Bitcoin Core using setting a http proxy?</p>

CC BY-SA 3.0
2018-02-06T22:55:50.607Z
Obvious question: is said corporation happy with you running this software on their computers and/or network? If they are, they should be happy to punch the relevant holes through the firewall for you; if they're not, you shouldn't be trying to work around that.
David Richerby
<bitcoin-core><testnet><bitcoin-qt-setup><proxy>
How to run Bitcoin Core behind corporate proxy?
smartmouse
# How to run Bitcoin Core behind corporate proxy?

(Asked by: username_0 on 2018-02-06)

I'm want to run Bitcoin Core client on TestNet and I need to config it for using under corporate proxy.
Since I'm using Squid to set proxy for my system I should set "localhost:3128" somewhere... but **bitcoin-qt** options seems to have only SOCK5 proxy field.

I also tried to set the proxy using the command line:

`./bitcoin-qt --testnet -proxy=localhost:3298`

[![enter image description here](https://i.sstatic.net/JK3Pp.png)](https://i.sstatic.net/JK3Pp.png)

...but it doesn't work.

How can I solve? Can I run Bitcoin Core using setting a http proxy?

**Tags:** bitcoin-core, testnet, bitcoin-qt-setup, proxy

> **Comments:**
> **username_1**: Obvious question: is said corporation happy with you running this software on their computers and/or network? If they are, they should be happy to punch the relevant holes through the firewall for you; if they're not, you shouldn't be trying to work around that.  

---

## 2 answers

### Answer by username_3 on 2018-02-06. Score: 10 | Accepted answer

Bitcoin doesn't use HTTP for its communications - it has its own specific protocol that runs directly on top of TCP. So an HTTP proxy like squid won't help.

If you aren't able to make outgoing TCP connections through your firewall (mainly to destination port 8333) then you'll have to contact your corporate IT people about adding appropriate firewall rules. The same if you want to be able to enable listening.


---

### Answer by username_2 on 2022-11-25. Score: 0

Although `bitcoind` itself only supports socks5, you can make any dynamically linked binary `http-proxy` capable with a `LD_PRELOAD`ing tool like [proxychains](https://github.com/haad/proxychains):

The prerequisite here is that your proxy server itself
supports the `HTTP CONNECT` method to non-standard ports.

In my VM lab setup I use [mitmproxy](https://mitmproxy.org/) on `192.168.100.1 8888` to analyze the network traffic using this `/etc/proxychains.conf`:

```
strict_chain
proxy_dns
remote_dns_subnet 224
tcp_read_time_out 15000
tcp_connect_time_out 8000
localnet 192.168.100.0/255.255.255.0
localnet 127.0.0.0/255.0.0.0
localnet ::1/128
[ProxyList]
http    192.168.100.1 8888

```

and `bitcoind` using `proxychains`:

```bash
proxychains bitcoind -testnet

```


---

