-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zope.interface error #2872
Comments
What is the output of |
/root/.local/share/letsencrypt/bin/pip freeze | grep -i interface |
/root/.local/share/letsencrypt/bin/pip list |
It appears I recommend:
If you get the same behavior, you can try installing
|
[root@letsencrypt]# ./letsencrypt-auto --help --debug Linux ip-10-11-180-115 3.14.20-20.44.amzn1.x86_64 #1 SMP Mon Oct 6 22:52:46 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux I had already been these alternatives. unsuccessfully |
And after doing |
Yes. still doesn't work. |
Looks like dupe of #2823. There are some known issues with AMIs which have not yet been resolved. Some people have had success with this comment. |
shit :P I dosen't find this post. But , it works. pip install pip --upgradepip install virtualenv --upgradevirtualenv -p /usr/bin/python27 venv27. venv27/bin/activategit clone https://github.com/letsencrypt/letsencryptcd letsencrypt./letsencrypt-auto certonly --debug --standalone -dthanks. |
Great! I'm glad it works. |
For me This cmd resolved the problem : |
@rmed19 that worked for me too, thanks! |
|
I just had to update stuff as @nohona pointed out. Question is, is there anyway to prevent this from happening? I have been successful for a while on this server until today, which required me to run these update commands. |
None of the above working for me… $ pip install --upgrade pip
Requirement already up-to-date: pip in /usr/local/lib/python2.7/site-packages
$ pip install virtualenv --upgrade
Requirement already up-to-date: virtualenv in ./.local/lib/python2.7/site-packages
$ cd letsencrypt/
$ ./certbot-auto renew
Error: couldn't get currently installed version for /home/ec2-user/.local/share/letsencrypt/bin/letsencrypt:
Traceback (most recent call last):
File "/home/ec2-user/.local/share/letsencrypt/bin/letsencrypt", line 7, in <module>
from certbot.main import main
File "/home/ec2-user/.local/share/letsencrypt/local/lib/python2.7/dist-packages/certbot/main.py", line 11, in <module>
import zope.component
File "/home/ec2-user/.local/share/letsencrypt/local/lib/python2.7/dist-packages/zope/component/__init__.py", line 16, in <module>
from zope.interface import Interface
ImportError: No module named interface |
I'm running into this same problem:
|
Same problem on Digital Ocean: None of the solutions so far work for me to renew my cert. However, using a Docker solution worked like a charm though. About 15 seconds of down-time. Thanks Dockerhub user gzm55 Install docker, then: Bring your server down temporarily to free up port 443 (apache stop or pm2 stop, etc), then run this (change "YOUR_DOMAIN.COM"): Then start your server back up. |
I was able to work around my issue by starting over with the certbot installation and renewal process following current instructions on the website from the beginning. I think the problem arose somewhere after updates to the underlying tools and since it had been so long since installing initially. |
I am having this problem now. I have removed & reinstalled letsencrypt & certbot but consistently get the message...
I have tried.... Any advice much appreciated, my Cert expires in 24Hrs. |
I ran into the same issue on Amazon Linux today. Executing certbot-auto with sudo fixed it for me. |
I'm running as root on Amazon Linux. This is a renewal; original cert installation was fine on this same machine. I'm not sure what would have changed. I tried the above steps of updating pip and virtualenv... no luck. :-( Cert expires in 9 days. |
I had lots of hassle, but found the following better than the CLI for my purposes. |
This sequence of commands seems to have fixed the issue on my AWS instance:
Some of the installed packages might be redundant. I also executed:
but it seems to have had no effect. |
The following gist worked for me:
e.g. I had to "upgrade" |
For anyone still having issues with AWS ami you can use following commands: To create new Certificates: To renew your certificates.
|
Part of the issue for me was related to some strange default behavior around 64 bit packages.
Actually fixed the problem |
Just to add some colour to the solution @lifeofguenter posted - solution for me on AWS linux when my update script fails seems to be different every time! This time, logged in as root The solution last tried, which worked, was:
No sudo-ing (using as root) But then At some stage, I saw a reference to pip v 6.1.6 popping up, so its in there somewhere, but I removed and reinstalled all relevant stuff. AWS + root / sudo / letsencrypt maybe storing a dependency somewhere along the chain which is not updated when pip is updating? |
thank you @ilamp ! worked like a charm |
I'm using AWS Linux and had the same issue: "No module named interface error". I did the what @ilamp proposed, but it didn't work. After I did the following, the issue was resolved:
|
Another update, since the install locations are different, again my issue was around the install location of the 64 bit packages on AWS by PIP. This was fixed by installing once and then running
The location may need to change as the location of the installation files move with updates, but the general fix remained the same. This was on an AWS AMI instance. |
So I think I've figured out what the problem is: Anything that has C source or headers gets built 64-bit and placed in /lib64 dist-packages, anything that doesn't lands in /lib. That means cffi, cryptography, and zope.interface, and they have to be rebuilt as 32-bit to work, or else run as 64-bit as Namingwaysway's method does (since it copies over 64-bit Python entirely). |
I was regularly doing the certbot-auto renew on an amazon ami.
|
Still seems to be an issue when renewing - even with
and/or
As I've only got 24 hrs to renew this cert I think I'll just manually install the cert using a trusted CA instead as it seems to be a smoother process for AMI instances, it would be good to get this working smoothly though. EDIT: just as a final attempt after posting this I tried
As per 0xnm's comment, this seemed to work ! Thanks |
This works for me. |
Traceback (most recent call last):
File "./letsencrypt", line 7, in
from letsencrypt.main import main
File "/root/.local/share/letsencrypt/local/lib/python2.7/dist-packages/letsencrypt/main.py", line 11, in
import zope.component
File "/root/.local/share/letsencrypt/local/lib/python2.7/dist-packages/zope/component/init.py", line 16, in
from zope.interface import Interface
ImportError: No module named interface
The text was updated successfully, but these errors were encountered: