# cert\_issuer.errors.InsufficientFundsError:

**URL:** <https://community.blockcerts.org/t/cert-issuer-errors-insufficientfundserror/2122>\
**Category:** Technical\
**Created:** [October 5, 2019, 7:12pm UTC](https://community.blockcerts.org/t/cert-issuer-errors-insufficientfundserror/2122 "2019-10-05T19:12:07Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![ramprasad](https://avatars.discourse-cdn.com/v4/letter/r/0ea827/32.png) [@ramprasad](https://community.blockcerts.org/u/ramprasad)\
**Post date:** [October 5, 2019, 7:12pm UTC](https://community.blockcerts.org/t/cert-issuer-errors-insufficientfundserror/2122/1 "2019-10-05T19:12:07Z")

</div>

I am using Ropsten testnet, my issuer address containes more than 4 ETH, but still I got insufficient fund error.How to resolve this issue?

0|Blockcert\_Product | mv:  
0|Blockcert\_Product | cannot stat ‘/root/product/cert-tools/sample\_data/unsigned\_certificates/_.json’  
0|Blockcert\_Product | : No such file or directory  
0|Blockcert\_Product | WARNING - Your app is configured to skip the wifi check when the USB is plugged in. Read the documentation to ensure this is what you want, since this is less secure  
0|Blockcert\_Product | INFO - This run will try to issue on the ethereum\_ropsten chain  
0|Blockcert\_Product | /usr/local/lib/python3.6/dist-packages/merkletools/ **init**.py:7: UserWarning: sha3 is not working!  
0|Blockcert\_Product | warn(“sha3 is not working!”)  
0|Blockcert\_Product | INFO - Set cost constants to recommended\_gas\_price=20000000000.000000, recommended\_gas\_limit=25000.000000  
0|Blockcert\_Product | INFO - Processing 13 certificates  
0|Blockcert\_Product | INFO - Processing 13 certificates under work path=/root/product/data/work  
0|Blockcert\_Product | WARNING -   
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product | Access denied | [ropsten.etherscan.io](http://ropsten.etherscan.io) used Cloudflare to restrict access  
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product | body{margin:0;padding:0}  
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product |_

   
_0|Blockcert\_Product | 
Please enable cookies._
   
_0|Blockcert\_Product |_ 
  
_0|Blockcert\_Product |_ 
  
_0|Blockcert\_Product | 
# 0|Blockcert\_Product | Error 0|Blockcert\_Product | 1020 0|Blockcert\_Product | Ray ID: 5211ad876867d695 • 2019-10-05 19:07:19 UTC 0|Blockcert\_Product |_
  
_0|Blockcert\_Product | 
## Access denied_
  
_0|Blockcert\_Product |_ 
  
_0|Blockcert\_Product |   
0|Blockcert\_Product |_ 
  
_0|Blockcert\_Product |_ 
  
_0|Blockcert\_Product |_ 
  
_0|Blockcert\_Product | 
## What happened?_
  
_0|Blockcert\_Product |_ 

_This website is using a security service to protect itself from online attacks._

  
_0|Blockcert\_Product |_ 
  
_0|Blockcert\_Product |  
0|Blockcert\_Product |_ 
  
_0|Blockcert\_Product |_ 
  
_0|Blockcert\_Product |_ 
  
_0|Blockcert\_Product |_ 

_0|Blockcert\_Product | Cloudflare Ray ID: **5211ad876867d695**  
0|Blockcert\_Product | •  
0|Blockcert\_Product | Your IP: 51.62.193.50  
0|Blockcert\_Product | •  
0|Blockcert\_Product | Performance & security by [Cloudflare](https://www.cloudflare.com/5xx-error-landing?utm_source=error_footer)  
0|Blockcert\_Product |  
0|Blockcert\_Product |_

  
_0|Blockcert\_Product |_ 
  
_0|Blockcert\_Product |_ 
   
_0|Blockcert\_Product |_ 
   
_0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product | INFO - Total cost will be 500000000000000 wei  
0|Blockcert\_Product | ERROR - Please add 500000000000000 wei to the address 0x71bc257fda57998e6715ee0b3370ab3b054f3111  
0|Blockcert\_Product | Traceback (most recent call last):  
0|Blockcert\_Product | File “/usr/local/bin/cert-issuer”, line 11, in   
0|Blockcert\_Product | load\_entry\_point(‘cert-issuer==2.0.15’, ‘console\_scripts’, ‘cert-issuer’)()  
0|Blockcert\_Product | File “/usr/local/lib/python3.6/dist-packages/cert\_issuer-2.0.15-py3.6.egg/cert\_issuer/ **main**.py”, line 17, in cert\_issuer\_main  
0|Blockcert\_Product | issue\_certificates.main(parsed\_config)  
0|Blockcert\_Product | File “/usr/local/lib/python3.6/dist-packages/cert\_issuer-2.0.15-py3.6.egg/cert\_issuer/issue\_certificates.py”, line 36, in main  
0|Blockcert\_Product | return issue(app\_config, certificate\_batch\_handler, transaction\_handler)  
0|Blockcert\_Product | File “/usr/local/lib/python3.6/dist-packages/cert\_issuer-2.0.15-py3.6.egg/cert\_issuer/issue\_certificates.py”, line 16, in issue  
0|Blockcert\_Product | transaction\_handler.ensure\_balance()  
0|Blockcert\_Product | File “/usr/local/lib/python3.6/dist-packages/cert\_issuer-2.0.15-py3.6.egg/cert\_issuer/blockchain\_handlers/ethereum/transaction\_handlers.py”, line 55, in ensure\_balance  
0|Blockcert\_Product | raise InsufficientFundsError(error\_message)  
0|Blockcert\_Product | cert\_issuer.errors.InsufficientFundsError: Please add 500000000000000 wei to the address 0x71bc257fda57998e6715ee0b3370ab3b054f3111  
0|Blockcert\_Product | mv: cannot stat '/root/product/cert-tools/sample\_data/unsigned\_certificates/_.json’: No such file or directory  
0|Blockcert\_Product | WARNING - Your app is configured to skip the wifi check when the USB is plugged in. Read the documentation to ensure this is what you want, since this is less secure  
0|Blockcert\_Product | INFO - This run will try to issue on the ethereum\_ropsten chain  
0|Blockcert\_Product | /usr/local/lib/python3.6/dist-packages/merkletools/ **init**.py:7: UserWarning: sha3 is not working!  
0|Blockcert\_Product | warn(“sha3 is not working!”)  
0|Blockcert\_Product | INFO - Set cost constants to recommended\_gas\_price=20000000000.000000, recommended\_gas\_limit=25000.000000  
0|Blockcert\_Product | INFO - Processing 13 certificates  
0|Blockcert\_Product | INFO - Processing 13 certificates under work path=/root/product/data/work  
0|Blockcert\_Product | WARNING -   
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product | Access denied | [ropsten.etherscan.io](http://ropsten.etherscan.io) used Cloudflare to restrict access  
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product | body{margin:0;padding:0}  
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product | 

  
0|Blockcert\_Product | 
Please enable cookies.
  
0|Blockcert\_Product | 
  
0|Blockcert\_Product | 
  
0|Blockcert\_Product | 
# 0|Blockcert\_Product | Error 0|Blockcert\_Product | 1020 0|Blockcert\_Product | Ray ID: 5211ad876867d695 • 2019-10-05 19:07:19 UTC 0|Blockcert\_Product |
  
0|Blockcert\_Product | 
## Access denied
  
0|Blockcert\_Product | 
  
0|Blockcert\_Product |   
0|Blockcert\_Product | 
  
0|Blockcert\_Product | 
  
0|Blockcert\_Product | 
  
0|Blockcert\_Product | 
## What happened?
  
0|Blockcert\_Product | 

This website is using a security service to protect itself from online attacks.

  
0|Blockcert\_Product | 
  
0|Blockcert\_Product |  
0|Blockcert\_Product | 
  
0|Blockcert\_Product | 
  
0|Blockcert\_Product | 
  
0|Blockcert\_Product | 

0|Blockcert\_Product | Cloudflare Ray ID: **5211ad876867d695**  
0|Blockcert\_Product | •  
0|Blockcert\_Product | Your IP: 52.63.194.56  
0|Blockcert\_Product | •  
0|Blockcert\_Product | Performance & security by [Cloudflare](https://www.cloudflare.com/5xx-error-landing?utm_source=error_footer)  
0|Blockcert\_Product |  
0|Blockcert\_Product |

  
0|Blockcert\_Product | 
  
0|Blockcert\_Product | 
  
0|Blockcert\_Product | 
  
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product |   
0|Blockcert\_Product | INFO - Total cost will be 500000000000000 wei  
0|Blockcert\_Product | ERROR - Please add 500000000000000 wei to the address 0x71bc257fda57998e6715ee0b3370ab3b054f3111  
0|Blockcert\_Product | Traceback (most recent call last):  
0|Blockcert\_Product | File “/usr/local/bin/cert-issuer”, line 11, in   
0|Blockcert\_Product | load\_entry\_point(‘cert-issuer==2.0.15’, ‘console\_scripts’, ‘cert-issuer’)()  
0|Blockcert\_Product | File “/usr/local/lib/python3.6/dist-packages/cert\_issuer-2.0.15-py3.6.egg/cert\_issuer/ **main**.py”, line 17, in cert\_issuer\_main  
0|Blockcert\_Product | issue\_certificates.main(parsed\_config)  
0|Blockcert\_Product | File “/usr/local/lib/python3.6/dist-packages/cert\_issuer-2.0.15-py3.6.egg/cert\_issuer/issue\_certificates.py”, line 36, in main  
0|Blockcert\_Product | return issue(app\_config, certificate\_batch\_handler, transaction\_handler)  
0|Blockcert\_Product | File “/usr/local/lib/python3.6/dist-packages/cert\_issuer-2.0.15-py3.6.egg/cert\_issuer/issue\_certificates.py”, line 16, in issue  
0|Blockcert\_Product | transaction\_handler.ensure\_balance()  
0|Blockcert\_Product | File “/usr/local/lib/python3.6/dist-packages/cert\_issuer-2.0.15-py3.6.egg/cert\_issuer/blockchain\_handlers/ethereum/transaction\_handlers.py”, line 55, in ensure\_balance  
0|Blockcert\_Product | raise InsufficientFundsError(error\_message)  
0|Blockcert\_Product | cert\_issuer.errors.InsufficientFundsError: Please add 500000000000000 wei to the address 0x71bc257fda57998e6715ee0b3370ab3b054f3111

---

<div class="post-metadata">

**Author:** ![aronning](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@aronning](https://community.blockcerts.org/u/aronning)\
**Post date:** [October 7, 2019, 10:40am UTC](https://community.blockcerts.org/t/cert-issuer-errors-insufficientfundserror/2122/2 "2019-10-07T10:40:32Z")

</div>

Looks similar to [Access Denied - Ethereum Ropsten](https://community.blockcerts.org/t/access-denied-ethereum-ropsten/2107/2)

Confirmed this is happening to me on ropsten but mainnet works. I tried adding an API key but it is still blocked on ropsten.

I’ll open up a ticket on this and can hopefully get around to adding another ethereum API this week.

---

<div class="post-metadata">

**Author:** ![aronning](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@aronning](https://community.blockcerts.org/u/aronning)\
**Post date:** [October 7, 2019, 3:06pm UTC](https://community.blockcerts.org/t/cert-issuer-errors-insufficientfundserror/2122/3 "2019-10-07T15:06:28Z")

</div>

Added a new ethereum api, myetherwallet, to the mix. Should be resolved. In version 2.0.20 if you’re using pypi.

---

<div class="post-metadata">

**Author:** ![yoman](https://avatars.discourse-cdn.com/v4/letter/y/7bcc69/32.png) [@yoman](https://community.blockcerts.org/u/yoman)\
**Post date:** [January 7, 2020, 2:31pm UTC](https://community.blockcerts.org/t/cert-issuer-errors-insufficientfundserror/2122/4 "2020-01-07T14:31:50Z")

</div>

Hello,

I’m having the same issue with insufficient funds asking me for 500 trillion wei.  
Is there any way to fix this?

Thanks in advance

---

<div class="post-metadata">

**Author:** ![yoman](https://avatars.discourse-cdn.com/v4/letter/y/7bcc69/32.png) [@yoman](https://community.blockcerts.org/u/yoman)\
**Post date:** [January 17, 2020, 12:46pm UTC](https://community.blockcerts.org/t/cert-issuer-errors-insufficientfundserror/2122/5 "2020-01-17T12:46:30Z")

</div>

Any help guys?  
I really need to solve this

---

<div class="post-metadata">

**Author:** ![aronning](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@aronning](https://community.blockcerts.org/u/aronning)\
**Post date:** [January 17, 2020, 2:55pm UTC](https://community.blockcerts.org/t/cert-issuer-errors-insufficientfundserror/2122/6 "2020-01-17T14:55:31Z")

</div>

500 trillion wei is only 0.0005 ether. What’s the problem?

---

<div class="post-metadata">

**Author:** ![yoman](https://avatars.discourse-cdn.com/v4/letter/y/7bcc69/32.png) [@yoman](https://community.blockcerts.org/u/yoman)\
**Post date:** [January 18, 2020, 9:15am UTC](https://community.blockcerts.org/t/cert-issuer-errors-insufficientfundserror/2122/7 "2020-01-18T09:15:57Z")

</div>

I have more than enough ether but i still get the insufficient funds error.

What could be the case?

---

<div class="post-metadata">

**Author:** ![aronning](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@aronning](https://community.blockcerts.org/u/aronning)\
**Post date:** [January 21, 2020, 2:07pm UTC](https://community.blockcerts.org/t/cert-issuer-errors-insufficientfundserror/2122/8 "2020-01-21T14:07:17Z")

</div>

Not sure, not seeing that problem myself. Typically it comes from either incorrect settings or the inability to access ethereum API’s.

Could you post your config & logs?

---

<div class="post-metadata">

**Author:** ![yoman](https://avatars.discourse-cdn.com/v4/letter/y/7bcc69/32.png) [@yoman](https://community.blockcerts.org/u/yoman)\
**Post date:** [January 27, 2020, 7:20pm UTC](https://community.blockcerts.org/t/cert-issuer-errors-insufficientfundserror/2122/9 "2020-01-27T19:20:16Z")

</div>

Well here is my conf.ini and the log. Hope it helps!

**Conf.ini:**

issuing\_address = 0x5749E785a610BfbD5f1257F080d92aD79E5D0Da6

chain = ethereum\_ropsten

usb\_name= /home/user/cert-issuer  
key\_file= pk.txt

unsigned\_certificates\_dir= /home/user/cert-issuer/data/unsigned\_certificates

blockchain\_certificates\_dir= /home/user/cert-issuer/data/blockchain\_certificates

work\_dir= /home/user/cert-issuer/data/work

no\_safe\_mode

**Log:**

WARNING - Your app is configured to skip the wifi check when the USB is plugged in. Read the documentation to ensure this is what you want, since this is less secure  
INFO - This run will try to issue on the ethereum\_ropsten chain  
INFO - Set cost constants to recommended\_gas\_price=20000000000.000000, recommended\_gas\_limit=25000.000000  
INFO - Processing 6 certificates  
INFO - Processing 6 certificates under work path=/home/user/cert-issuer/data/work  
WARNING -

 Access denied | ropsten.etherscan.io used Cloudflare to restrict access body{margin:0;padding:0} 

Please enable cookies.

# Error1020Ray ID: 55bd0bb3da94a68d • 2020-01-27 19:13:45 UTC

## Access denied

```
  <section></section><!-- spacer -->

  <div class="cf-section cf-wrapper">
    <div class="cf-columns two">
      <div class="cf-column">
        <h2 data-translate="what_happened">What happened?</h2>
        <p>This website is using a security service to protect itself from online attacks.</p>
      </div>

      
    </div>
  </div><!-- /.section -->

  <div class="cf-error-footer cf-wrapper">

```

Cloudflare Ray ID: **55bd0bb3da94a68d** •Your IP: 94.64.114.25•Performance & security by [Cloudflare](https://www.cloudflare.com/5xx-error-landing?utm_source=error_footer)

```
</div><!-- /#cf-error-details -->

```

INFO - Total cost will be 500000000000000 wei  
ERROR - Please add 500000000000000 wei to the address 0x5749E785a610BfbD5f1257F080d92aD79E5D0Da6  
Traceback (most recent call last):  
File “/usr/local/bin/cert-issuer”, line 11, in   
sys.exit(cert\_issuer\_main())  
File “/usr/local/lib/python3.6/dist-packages/cert\_issuer/ **main**.py”, line 17, in cert\_issuer\_main  
issue\_certificates.main(parsed\_config)  
File “/usr/local/lib/python3.6/dist-packages/cert\_issuer/issue\_certificates.py”, line 36, in main  
return issue(app\_config, certificate\_batch\_handler, transaction\_handler)  
File “/usr/local/lib/python3.6/dist-packages/cert\_issuer/issue\_certificates.py”, line 16, in issue  
transaction\_handler.ensure\_balance()  
File “/usr/local/lib/python3.6/dist-packages/cert\_issuer/blockchain\_handlers/ethereum/transaction\_handlers.py”, line 55, in ensure\_balance  
raise InsufficientFundsError(error\_message)  
cert\_issuer.errors.InsufficientFundsError: Please add 500000000000000 wei to the address 0x5749E785a610BfbD5f1257F080d92aD79E5D0Da6

---

<div class="post-metadata">

**Author:** ![aronning](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@aronning](https://community.blockcerts.org/u/aronning)\
**Post date:** [January 27, 2020, 11:22pm UTC](https://community.blockcerts.org/t/cert-issuer-errors-insufficientfundserror/2122/10 "2020-01-27T23:22:18Z")

</div>

Looks pretty similar to this: [Access Denied - Ethereum Ropsten](https://community.blockcerts.org/t/access-denied-ethereum-ropsten/2107/2)

Do you have version 2.0.20+ of the blockcerts issuer?

---

<div class="post-metadata">

**Author:** ![yoman](https://avatars.discourse-cdn.com/v4/letter/y/7bcc69/32.png) [@yoman](https://community.blockcerts.org/u/yoman)\
**Post date:** [January 28, 2020, 12:02pm UTC](https://community.blockcerts.org/t/cert-issuer-errors-insufficientfundserror/2122/11 "2020-01-28T12:02:09Z")

</div>

Yes, first thing i did was to get the latest version but i still get the error.

---

<div class="post-metadata">

**Author:** ![aronning](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@aronning](https://community.blockcerts.org/u/aronning)\
**Post date:** [January 28, 2020, 2:57pm UTC](https://community.blockcerts.org/t/cert-issuer-errors-insufficientfundserror/2122/12 "2020-01-28T14:57:02Z")

</div>

Could you double check that the latest is actually running? Distinct in the logs should be something like

```auto
INFO - Balance check response: {'jsonrpc': '2.0', 'id': 1, 'result': '0xda8fa4202ab0000'}
INFO - Balance check succeeded: {'jsonrpc': '2.0', 'id': 1, 'result': '0xda8fa4202ab0000'}
INFO - Total cost will be 500000000000000 wei
INFO - Starting finalizable signer

```

after the cloud front error. MyEtherWallet should be checked as a fallback when Etherscan fails. Otherwise `Error getting balance through MyEtherWallet. Error msg:` would display if it was having a hard time connecting to MEW as well.

---

<div class="post-metadata">

**Author:** ![yoman](https://avatars.discourse-cdn.com/v4/letter/y/7bcc69/32.png) [@yoman](https://community.blockcerts.org/u/yoman)\
**Post date:** [January 28, 2020, 10:32pm UTC](https://community.blockcerts.org/t/cert-issuer-errors-insufficientfundserror/2122/13 "2020-01-28T22:32:26Z")

</div>

I can’t see any of this in the logs. Can you elaborate more on how to check if the latest is running?
