# Bitcoin-cli getnewaddress - Urgent

**URL:** <https://community.blockcerts.org/t/bitcoin-cli-getnewaddress-urgent/1040>\
**Category:** Support\
**Created:** [May 18, 2018, 4:04am UTC](https://community.blockcerts.org/t/bitcoin-cli-getnewaddress-urgent/1040 "2018-05-18T04:04:59Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![clara](https://avatars.discourse-cdn.com/v4/letter/c/d26b3c/32.png) [@clara](https://community.blockcerts.org/u/clara)\
**Post date:** [May 18, 2018, 4:04am UTC](https://community.blockcerts.org/t/bitcoin-cli-getnewaddress-urgent/1040/1 "2018-05-18T04:04:59Z")

</div>

Can anyone help me on how to run these commands ?

issuer=`bitcoin-cli getnewaddress`  
sed -i.bak “s//$issuer/g” /etc/cert-issuer/conf.ini  
bitcoin-cli dumpprivkey $issuer \> /etc/cert-issuer/pk\_issuer.txt

correct me if I’m wrong. I suppose to run them here right ?  
 ![docker%201](https://us1.discourse-cdn.com/flex016/uploads/blockcerts/original/1X/338c0834893a012e2918535922f5df9a7f2b80e9.PNG)

But when I run those command

![docker%202](https://us1.discourse-cdn.com/flex016/uploads/blockcerts/original/1X/81f9c9726f9d10541d595fd1518a318152a070d7.PNG)

What am I suppose to do ?  
I’m so lost .

---

<div class="post-metadata">

**Author:** ![lparker](https://avatars.discourse-cdn.com/v4/letter/l/3bc359/32.png) [@lparker](https://community.blockcerts.org/u/lparker)\
**Post date:** [May 18, 2018, 2:09pm UTC](https://community.blockcerts.org/t/bitcoin-cli-getnewaddress-urgent/1040/2 "2018-05-18T14:09:35Z")

</div>

You’re getting there! Those three commands did the following:

1. Created a new Bitcoin address and assigned it to the shell variable called `issuer`.
2. Opened the file `/etc/cert-issuer/conf.ini` and replaced the string `<issuing-address>` with the value in the `issuer` shell variable.
3. Emitted the private key associated to the Bitcoin address into a text file called `/etc/cert-issuer/pk_issuer.txt`.

If you look at the contents of the conf.ini file, you should see that it has a Bitcoin address in it, up towards the top. You may do this by running a command like the following:

`cat /etc/cert-issuer/conf.ini`.

From there, if you’re working through the Quick Start, you’ll jump immediately into the next section of that document, titled “Issuing Certificates.” That will take you through the step of copying the example unsigned certificate into the appropriate location in the file system, generating some fake coinage, sending it to your issuing address, and finally, running `cert-issuer`. In regtest mode, this will result in a signed copy of the input certificate being written to output directory (in this case, `/etc/cert-issuer/data/blockchain_certificates`).

When you finish these steps, you will have a signed certificate, though it will not yet be on the Bitcoin blockchain. When you’re ready to try a testnet issuance, you’ll need to make a couple of changes to the `/etc/cert-issuer/conf.ini` file, changing the network to `bitcoin_testnet` and probably commenting out the line that says `bitcoind`, if it exists. The README has more information about testnet and mainnet issuance, if you read it from the “Create a Bitcoin issuing address” subheading onwards.

---

<div class="post-metadata">

**Author:** ![clara](https://avatars.discourse-cdn.com/v4/letter/c/d26b3c/32.png) [@clara](https://community.blockcerts.org/u/clara)\
**Post date:** [May 21, 2018, 1:44am UTC](https://community.blockcerts.org/t/bitcoin-cli-getnewaddress-urgent/1040/3 "2018-05-21T01:44:56Z")

</div>

Hey @lparker thanks for your time in giving such a detailed explanation. But I do stuck at the beginning. I can’t find the directory /etc/cert-issuer/conf.ini . Where did I do the mistake ?

---

<div class="post-metadata">

**Author:** ![skilabz](https://sea2.discourse-cdn.com/flex016/user_avatar/community.blockcerts.org/skilabz/32/411_2.png) [@skilabz](https://community.blockcerts.org/u/skilabz)\
**Post date:** [July 4, 2018, 7:41pm UTC](https://community.blockcerts.org/t/bitcoin-cli-getnewaddress-urgent/1040/4 "2018-07-04T19:41:24Z")

</div>

Have you installed the cert-issuer from docker ? If yes, the directories would’ve been automatically created. If no, then u need to make directories using mkdir command. some of the directories might be hidden so give try by using “ls -a” command. Happy coding…

---

<div class="post-metadata">

**Author:** ![gouravvc](https://avatars.discourse-cdn.com/v4/letter/g/f17d59/32.png) [@gouravvc](https://community.blockcerts.org/u/gouravvc)\
**Post date:** [July 28, 2020, 4:39am UTC](https://community.blockcerts.org/t/bitcoin-cli-getnewaddress-urgent/1040/5 "2020-07-28T04:39:29Z")

</div>

Hello ,  
Can you please elaborate it , what will be the information in conf.ini file in cert-issuer directories . If i will use mkdir command then it will create blank directory .How can i get conf.ini file in cert-issuer directories ?  
OS - Windows
