# Running Cert-issuer without cert-issuer command

**URL:** <https://community.blockcerts.org/t/running-cert-issuer-without-cert-issuer-command/3093>\
**Category:** Technical\
**Created:** [February 17, 2022, 12:41pm UTC](https://community.blockcerts.org/t/running-cert-issuer-without-cert-issuer-command/3093 "2022-02-17T12:41:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nitinb](https://avatars.discourse-cdn.com/v4/letter/n/82dd89/32.png) [@nitinb](https://community.blockcerts.org/u/nitinb)\
**Post date:** [February 17, 2022, 12:41pm UTC](https://community.blockcerts.org/t/running-cert-issuer-without-cert-issuer-command/3093/1 "2022-02-17T12:41:29Z")

</div>

I am trying to run cert-issuer by running a python file. I am inside a virtual env with default chain as ethereum (python setup.py experimental --blockchain=ethereum)

If I try to issue certificate via command **cert-issuer -c conf\_ethtest.ini**  
I am able to generate the certificate.

But if I try to issue certificate by command **python3 cert\_issuer/main.py**  
I get error - No module named chainpoint.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/blockcerts/original/1X/1ea9dfd440f661bddccae74b34ba5aaf4df0c715.png)

I am not sure why this error is coming and that to **ModuleNotFound**.

**How can I issue Ethereum certificate by directly running a python (.py) file**

I tried **main**.py as I believe this file is the entry point for issuing certificate.

---

<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:** [February 28, 2022, 10:30pm UTC](https://community.blockcerts.org/t/running-cert-issuer-without-cert-issuer-command/3093/2 "2022-02-28T22:30:01Z")

</div>

Hello! I get the impression here that you have two instances of cert-issuer going. One is somewhere on your path - maybe a global install? Another is the one that you’re trying to run out of the local repo.

To gather info, you might want to run `which cert-issuer` to see where that’s coming from. You might want to try to remove it to avoid confusion, though that can certainly wait.

As for ` __main.py__ `: the chainpoint library and related dependencies have given us headaches in the past. Recently, changes made it in that help to work around this. If you are trying to issue a v2 Blockcert, you might want to `git checkout v2`, to make sure you’re using the correct code, and `git pull` to see if anything updates.

If that doesn’t work on its own, you can try to uninstall the existing set of dependencies, and then reinstall them, forcing pip to avoid using cache. Something like this (make sure you’re in the virtualenv!):

```auto
pip freeze | xargs pip uninstall -y
pip install -r ethereum_requirements.txt --no-cache
pip install -r requirements.txt --no-cache

```

That should leave you in a state sufficient to run ` __main.py__ `. It seems to work for me, so if the above doesn’t work for you, please let me know and we’ll gather more info.

Thanks,  
Lucas