# Linode/Ubuntu 16.04 LTS/nginx certonly error

**URL:** <https://community.letsencrypt.org/t/linode-ubuntu-16-04-lts-nginx-certonly-error/29971>\
**Category:** Help\
**Created:** [March 15, 2017, 10:17pm UTC](https://community.letsencrypt.org/t/linode-ubuntu-16-04-lts-nginx-certonly-error/29971 "2017-03-15T22:17:47Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![karitoy](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/karitoy/32/11972_2.png) [@karitoy](https://community.letsencrypt.org/u/karitoy)\
**Post date:** [March 15, 2017, 10:17pm UTC](https://community.letsencrypt.org/t/linode-ubuntu-16-04-lts-nginx-certonly-error/29971/1 "2017-03-15T22:17:47Z")

</div>

I tried to issue this in my Linode box:

> letsencrypt certonly --webroot -w /var/www/findmytutor -d [findmytutor.co](http://findmytutor.co) -d [www.findmytutor.co](http://www.findmytutor.co)

and I get the following error:

> Traceback (most recent call last):  
> File "/usr/bin/letsencrypt", line 9, in   
> load\_entry\_point('letsencrypt==0.4.1', 'console\_scripts', 'letsencrypt')()  
> File "/usr/lib/python2.7/dist-packages/pkg\_resources/ **init**.py", line 542, in load\_entry\_point  
> return get\_distribution(dist).load\_entry\_point(group, name)  
> File "/usr/lib/python2.7/dist-packages/pkg\_resources/ **init**.py", line 2569, in load\_entry\_point  
> return ep.load()  
> File "/usr/lib/python2.7/dist-packages/pkg\_resources/ **init**.py", line 2229, in load  
> return self.resolve()  
> File "/usr/lib/python2.7/dist-packages/pkg\_resources/ **init**.py", line 2235, in resolve  
> module = **import** (self.module\_name, fromlist=[' **name**'], level=0)  
> ImportError: No module named letsencrypt.cli

Can anyone please tell me what the problem is and what I should do to resolve this? Thanks!

---

<div class="post-metadata">

**Author:** ![ahaw021](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/ahaw021/32/14882_2.png) [@ahaw021](https://community.letsencrypt.org/u/ahaw021)\
**Post date:** [March 21, 2017, 10:02am UTC](https://community.letsencrypt.org/t/linode-ubuntu-16-04-lts-nginx-certonly-error/29971/2 "2017-03-21T10:02:55Z")

</div>

how was the client installed

---

<div class="post-metadata">

**Author:** ![chech](https://avatars.discourse-cdn.com/v4/letter/c/ac91a4/32.png) [@chech](https://community.letsencrypt.org/u/chech)\
**Post date:** [March 23, 2017, 7:49pm UTC](https://community.letsencrypt.org/t/linode-ubuntu-16-04-lts-nginx-certonly-error/29971/3 "2017-03-23T19:49:21Z")

</div>

I have the same issue.

Client was installed using [digitalocean's instructions](https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-16-04) for ubuntu 16.04 and nginx:

> sudo apt-get update  
> sudo apt-get install letsencrypt

Any clues on what's going on? My full log is:

> letsencrypt renew  
> Traceback (most recent call last):  
> File "/usr/bin/letsencrypt", line 9, in   
> load\_entry\_point('letsencrypt==0.4.1', 'console\_scripts', 'letsencrypt')()  
> File "/usr/lib/python2.7/dist-packages/pkg\_resources/ **init**.py", line 542, in load\_entry\_point  
> return get\_distribution(dist).load\_entry\_point(group, name)  
> File "/usr/lib/python2.7/dist-packages/pkg\_resources/ **init**.py", line 2569, in load\_entry\_point  
> return ep.load()  
> File "/usr/lib/python2.7/dist-packages/pkg\_resources/ **init**.py", line 2229, in load  
> return self.resolve()  
> File "/usr/lib/python2.7/dist-packages/pkg\_resources/ **init**.py", line 2235, in resolve  
> module = **import** (self.module\_name, fromlist=[' **name**'], level=0)  
> File "/usr/lib/python2.7/dist-packages/letsencrypt/cli.py", line 34, in   
> from letsencrypt import client  
> File "/usr/lib/python2.7/dist-packages/letsencrypt/client.py", line 27, in   
> from letsencrypt import storage  
> File "/usr/lib/python2.7/dist-packages/letsencrypt/storage.py", line 7, in   
> import configobj  
> EOFError: EOF read where object expected

---

<div class="post-metadata">

**Author:** ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)\
**Post date:** [March 23, 2017, 8:17pm UTC](https://community.letsencrypt.org/t/linode-ubuntu-16-04-lts-nginx-certonly-error/29971/4 "2017-03-23T20:17:36Z")

</div>

It sounds like your letsencrypt and ConfigObj (a popular Python library for parsing configuration files, used by letsencrypt) installs are damaged.

I might suggest reinstalling those two packages with “`apt install --reinstall python-configobj python-letsencrypt`” – and any other affected packages – but this is above my pay grade.

I’m curious to know if there were any issues when they were installed, if anything happened later (e.g. some sort of botched `pip` upgrade), or if your systems is having other issues, but even if you told me, i don’t know what to do.

---

<div class="post-metadata">

**Author:** ![chech](https://avatars.discourse-cdn.com/v4/letter/c/ac91a4/32.png) [@chech](https://community.letsencrypt.org/u/chech)\
**Post date:** [March 24, 2017, 3:51pm UTC](https://community.letsencrypt.org/t/linode-ubuntu-16-04-lts-nginx-certonly-error/29971/5 "2017-03-24T15:51:48Z")

</div>

> [@mnordhoff](#):
>
> apt install --reinstall python-configobj python-letsencrypt

That definetely solved it, thanks!

I did not have pip installed "pip returned command not found", and I haven't messed intentionally with python libraries. No clue how they got corrupted, but it's back and working 🙂

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [April 23, 2017, 3:51pm UTC](https://community.letsencrypt.org/t/linode-ubuntu-16-04-lts-nginx-certonly-error/29971/6 "2017-04-23T15:51:49Z")

</div>

Closed on April 23, 2017, 3:51pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
