<p>After a bit of mocking about with this problem, I figured the certificate files were in a wrong folder. As I was running Bitcoin on testnet, the directory in which it looks for certificates is different, than on the main net. On the other hand, it loads the Bitcoin.conf from the same place...</p>

<p>The folder bitcoin looks for the certificate in is the folder containing wallet.dat, which for testnet is in .bitcoin/testnet/ folder</p>

CC BY-SA 3.0
2012-12-16T01:21:52.087Z
Interesting edit... I thought @Community was a process not a real human user
makerofthings7
CC BY-SA 3.0
2012-01-24T19:13:31.353Z
2012-07-18T11:18:18.323Z
2012-07-18T11:18:18.323Z
ThePiachu
<p>I recently tried running Bitcoin-QT as a server with SSL enabled, but when I was testing the connection, with this <a href="https://en.bitcoin.it/wiki/Enabling_SSL_on_original_client_daemon" rel="nofollow">command</a>:</p>

<pre><code>openssl s_client -connect 111.11.111.111:8332
</code></pre>

<p>I got this error:</p>

<pre><code>CONNECTED(00000003)
4308:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:/SourceCache/OpenSSL098/OpenSSL098-35.1/src/ssl/s23_lib.c:182:
</code></pre>

<p>Does anyone have an idea what is causing this problem and how should I go about fixing it?</p>

<bitcoin-core><bitcoind><json-rpc>
Bitcoin RPC SSL error
ThePiachu
# Bitcoin RPC SSL error

(Asked by: username_0 on 2012-01-24)

I recently tried running Bitcoin-QT as a server with SSL enabled, but when I was testing the connection, with this [command](https://en.bitcoin.it/wiki/Enabling_SSL_on_original_client_daemon):

```
openssl s_client -connect 111.11.111.111:8332

```

I got this error:

```
CONNECTED(00000003)
4308:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:/SourceCache/OpenSSL098/OpenSSL098-35.1/src/ssl/s23_lib.c:182:

```

Does anyone have an idea what is causing this problem and how should I go about fixing it?

**Tags:** bitcoin-core, bitcoind, json-rpc


---

## 1 answers

### Answer by username_0 on 2012-01-24. Score: 4 | Accepted answer

After a bit of mocking about with this problem, I figured the certificate files were in a wrong folder. As I was running Bitcoin on testnet, the directory in which it looks for certificates is different, than on the main net. On the other hand, it loads the Bitcoin.conf from the same place...

The folder bitcoin looks for the certificate in is the folder containing wallet.dat, which for testnet is in .bitcoin/testnet/ folder

> **Comments:**
> **username_1**: Interesting edit... I thought @Community was a process not a real human user  

---

