Skip to content
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

TTPError: 404 Client Error: Not Found for url: https://www.piwheels.hostedpi.com/simple/zope-component/ #5138

Closed
tomofu74 opened this issue Sep 26, 2017 · 20 comments

Comments

Projects
None yet
@tomofu74
Copy link

commented Sep 26, 2017

My operating system is (include version):

Rasberrypi3 raspbian

I installed Certbot with (certbot-auto, OS package manager, pip, etc):

letsencrypt-auto

I ran this command and it produced this output:

letsencrypt-auto

File "/opt/eff.org/certbot/venv/share/python-wheels/requests-2.12.4-py2.py3-none-any.whl/requests/models.py", line 893, in raise_for_status
raise HTTPError(http_error_msg, response=self)

Certbot's behavior differed from what I expected because:

Here is a Certbot log showing the issue (if available):

Logs are stored in /var/log/letsencrypt by default. Feel free to redact domains, e-mail and IP addresses as you see fit.

Here is the relevant nginx server block or Apache virtualhost for the domain I am configuring:

@nachoparker

This comment has been minimized.

Copy link

commented Sep 28, 2017

same here

@LaLaGuy

This comment has been minimized.

Copy link

commented Sep 28, 2017

Same problem.

The problem is that the given url is wrong :
https://www.piwheels.hostedpi.com/simple/zope-component/

It should be :
https://www.piwheels.hostedpi.com/simple/zope.component/

Don't know how to correct it myself.
Waiting for an update.
log.txt

@bmw

This comment has been minimized.

Copy link
Member

commented Sep 28, 2017

Are you still seeing this problem? Is everyone that can reproduce running Raspbian?

@erikrose, any thoughts?

@LaLaGuy

This comment has been minimized.

Copy link

commented Sep 28, 2017

I'm on Raspbian (the latest version).
The problem is still here.
Personally, I followed those instructions : https://certbot.eff.org/#pip-nginx.
After your comment, I tried again from the start but got the same result.
Like I said on my last post, it tries to access a wrong url.
The problem is the same for other software (Apache for example).

@sadreck

This comment has been minimized.

Copy link

commented Sep 28, 2017

Can confirm as well, running Raspbian (stretch) and am getting the same error:

HTTPError: 404 Client Error: Not Found for url: https://www.piwheels.hostedpi.com/simple/zope-component/

Command line is:

sudo ./certbot-auto certonly --standalone -d mydomain

@nachoparker

This comment has been minimized.

Copy link

commented Sep 29, 2017

Exactly the same here. I create Raspbian based images in an automated way for NextCloudPi and I can reproduce 100% of the times.

@erikrose

This comment has been minimized.

Copy link
Collaborator

commented Sep 29, 2017

@bmw This is an upstream bug in piwheels itself and should go away when it gets fixed.

@erikrose erikrose closed this Sep 29, 2017

@ShashankJain123

This comment has been minimized.

Copy link

commented Oct 1, 2017

I managed to solve this by giving the auto script an additional repository to look for files; in this case zope.component rather than zope-component

To do this modify /etc/pip.conf and add the below line item
extra-index-url=https://www.piwheels.hostedpi.com/simple/zope.components

Worked like charm and certificate has been generated.

PS: I am not a programmer or a coder and don't know anything about pip or python. This may be a temporary solution and worked for me; so should for you.

@tball78

This comment has been minimized.

Copy link

commented Oct 1, 2017

@ShashankJain123 Thanks. Workaround worked like a charm. I appreciate you sharing this since this has been a recent frustration while attempting to get Let's Encrypt cert created.

@nachoparker

This comment has been minimized.

Copy link

commented Oct 1, 2017

It works, thank you so much!!

@fanconic

This comment has been minimized.

Copy link

commented Oct 8, 2017

Unfortunately, if I try the workaround by entering "/etc/pip.conf" I'm denied the access.
What am I doing wrong, or how could I access it?

@ShashankJain123

This comment has been minimized.

Copy link

commented Oct 8, 2017

@fanconic I worked on that with WinSCP. Helps perform all root actions. Try that

@fanconic

This comment has been minimized.

Copy link

commented Oct 8, 2017

@ShashankJain123
I’ve tried now with WinSCP, however I‘m still getting a permission error (error 3: permission denied)

Any answer to that?
Or maybe a link to another forum, as I wasn‘t able to find any solution so far.

Thank you already in advanced

@erikrose

This comment has been minimized.

Copy link
Collaborator

commented Oct 9, 2017

There are about a zillion different places pip looks for configuration. If you can't work out the permission problems for one, try creating another: https://pip.pypa.io/en/stable/user_guide/#configuration. Cheers!

@fanconic

This comment has been minimized.

Copy link

commented Oct 9, 2017

@erikrose Thank you, I shall try!

@wpmjones

This comment has been minimized.

Copy link

commented Oct 27, 2017

I'm on Raspbian and tried to set up certbot using ./certbot-auto certonly --standalone --standalone-supported-challenges http-01 --email your@email.address -d hass-example.duckdns.org and got the same error with the incorrect url. I used the solution that @ShashankJain123 proposed and it worked fine.

@nachoparker

This comment has been minimized.

Copy link

commented Oct 29, 2017

The issue has been fixed

piwheels/piwheels#20 (comment)

No workarounds are required now

@tomofu74

This comment has been minimized.

Copy link
Author

commented Nov 3, 2017

Thanks!

@Halloran

This comment has been minimized.

Copy link

commented Dec 21, 2017

In my case, adding lines to:
/etc/pip.conf
as recommended above did not work. What did work was commenting all lines out of the file. I believe that removing the file altogether would have worked as well.

@maxverstappen

This comment has been minimized.

Copy link

commented Jan 13, 2018

"What did work was commenting all lines out of the file"
Worked also for me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.