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

Expected a numeric value for http01_port #2468

Closed
schoen opened this issue Feb 13, 2016 · 5 comments · Fixed by #2579
Closed

Expected a numeric value for http01_port #2468

schoen opened this issue Feb 13, 2016 · 5 comments · Fixed by #2579

Comments

@schoen
Copy link
Contributor

schoen commented Feb 13, 2016

Forum user Randall describes this problem when using letsencrypt renew:

...The error was Expected a numeric value for http01_port. ...
Editing the file /etc/letsencrypt/renewal/[my.domain].conf file solved this problem. I changed http01_port = None to http01_port = 80

https://community.letsencrypt.org/t/help-us-test-renewal-with-letsencrypt-renew/10562/5

@bmw said that this would have been fixed (in terms of renewal config files correctly specifying http01_port) back in November, but people who have older lineages than that may have this problem when renewing with standalone. That could conceivably be a pretty large number of users!

@bmw
Copy link
Member

bmw commented Feb 16, 2016

For reference, this was the commit that changed the behavior: bb6736f

@bmw
Copy link
Member

bmw commented Feb 19, 2016

Looks like we had a similar problem before when renewer.py tried to cast the value to an int.

@schoen
Copy link
Contributor Author

schoen commented Mar 1, 2016

A number of people are still having trouble with this (we just had another report on the forum).

@schoen schoen added this to the 0.5.0 milestone Mar 1, 2016
@bmw bmw mentioned this issue Mar 1, 2016
@schoen
Copy link
Contributor Author

schoen commented Mar 2, 2016

Hopefully nobody will be troubled by this bug anymore thanks to @bmw's PR. I'll try to let some people know on the forums and confirm that it works for them.

@bmw
Copy link
Member

bmw commented Mar 2, 2016

Note: No one (including letsencrypt-auto users) will get these changes before the next release unless they're installing directly from this repo.

@bmw bmw modified the milestones: 0.4.2, 0.5.0 Mar 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants