# Chef.io certificate error causing client install error

**URL:** <https://discourse.chef.io/t/chef-io-certificate-error-causing-client-install-error/6439>\
**Category:** Chef Infra (archive)\
**Created:** [March 20, 2015, 8:30pm UTC](https://discourse.chef.io/t/chef-io-certificate-error-causing-client-install-error/6439 "2015-03-20T20:30:03Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Justin\_Franks](https://avatars.discourse-cdn.com/v4/letter/j/f4b2a3/32.png) [@Justin\_Franks](https://discourse.chef.io/u/Justin_Franks)\
**Post date:** [March 20, 2015, 8:30pm UTC](https://discourse.chef.io/t/chef-io-certificate-error-causing-client-install-error/6439/1 "2015-03-20T20:30:03Z")

</div>

Connecting to 10.161.66.83  
10.161.66.83 Installing Chef Client…  
10.161.66.83 --2015-03-20 20:15:34-- [https://www.chef.io/chef/install.sh](https://www.chef.io/chef/install.sh)  
10.161.66.83 Resolving [www.chef.io](http://www.chef.io)… 199.27.79.65  
10.161.66.83 Connecting to www.chef.io|199.27.79.65|:443… connected.  
10.161.66.83 ERROR: certificate common name “[g.ssl.fastly.net](http://g.ssl.fastly.net)” doesn’t match requested host name “[www.chef.io](http://www.chef.io)”.  
10.161.66.83 To connect to [www.chef.io](http://www.chef.io) insecurely, use ‘–no-check-certificate’.  
10.161.66.83 Starting first Chef Client run…  
10.161.66.83 bash: line 96: chef-client: command not found?

Errrr… ummm…

* * *

Justin Franks  
Lead Operations Engineer  
SaaS, Cloud, Data Centers & Infrastructure  
Lithium Technologies, Inc  
225 Bush St., 15th Floor  
San Francisco, CA 94104  
tel: +1 415 757 3100 x3219

---

<div class="post-metadata">

**Author:** ![cwebber](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/cwebber/32/146_2.png) [@cwebber](https://discourse.chef.io/u/cwebber)\
**Post date:** [March 20, 2015, 8:33pm UTC](https://discourse.chef.io/t/chef-io-certificate-error-causing-client-install-error/6439/2 "2015-03-20T20:33:05Z")

</div>

Hey Justin,

Sorry you are having issues with this. While we work on a fix for this the workaround is to call --bootstrap-url [https://www.opscode.com/chef/install.sh](https://www.opscode.com/chef/install.sh) [https://www.opscode.com/chef/install.sh](https://www.opscode.com/chef/install.sh) with your knife bootstrap command.

Please let me know if you have any questions.

— cwebber

> On Mar 20, 2015, at 13:30, Justin Franks [justin.franks@lithium.com](mailto:justin.franks@lithium.com) wrote:
> 
> Connecting to 10.161.66.83  
> 10.161.66.83 Installing Chef Client...  
> 10.161.66.83 --2015-03-20 20:15:34-- [https://www.chef.io/chef/install.sh](https://www.chef.io/chef/install.sh) [https://www.chef.io/chef/install.sh](https://www.chef.io/chef/install.sh)  
> 10.161.66.83 Resolving [www.chef.io](http://www.chef.io) [http://www.chef.io/](http://www.chef.io/)... 199.27.79.65  
> 10.161.66.83 Connecting to [www.chef.io](http://www.chef.io) [http://www.chef.io/](http://www.chef.io/)|199.27.79.65|:443... connected.  
> 10.161.66.83 ERROR: certificate common name “[g.ssl.fastly.net](http://g.ssl.fastly.net) [http://g.ssl.fastly.net/](http://g.ssl.fastly.net/)” doesn’t match requested host name “[www.chef.io](http://www.chef.io) [http://www.chef.io/](http://www.chef.io/)”.  
> 10.161.66.83 To connect to [www.chef.io](http://www.chef.io) [http://www.chef.io/](http://www.chef.io/) insecurely, use ‘--no-check-certificate’.  
> 10.161.66.83 Starting first Chef Client run...  
> 10.161.66.83 bash: line 96: chef-client: command not found​  
> Errrr... ummm...
> 
> * * *
> 
> Justin Franks  
> Lead Operations Engineer  
> SaaS, Cloud, Data Centers & Infrastructure  
> Lithium Technologies, Inc  
> 225 Bush St., 15th Floor  
> San Francisco, CA 94104  
> tel: +1 415 757 3100 x3219

---

<div class="post-metadata">

**Author:** ![Justin\_Franks](https://avatars.discourse-cdn.com/v4/letter/j/f4b2a3/32.png) [@Justin\_Franks](https://discourse.chef.io/u/Justin_Franks)\
**Post date:** [March 20, 2015, 8:43pm UTC](https://discourse.chef.io/t/chef-io-certificate-error-causing-client-install-error/6439/3 "2015-03-20T20:43:46Z")

</div>

?I would like to tell our chef servers to pull the client from out repo and not from a public place. What do I edit on the server?

* * *

Justin Franks  
Lead Operations Engineer  
SaaS, Cloud, Data Centers & Infrastructure  
Lithium Technologies, Inc  
225 Bush St., 15th Floor  
San Francisco, CA 94104  
tel: +1 415 757 3100 x3219

* * *

From: Christopher Webber [cwebber@chef.io](mailto:cwebber@chef.io)  
Sent: Friday, March 20, 2015 1:33 PM  
To: [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
Subject: [chef] Re: [Chef.io](http://Chef.io) certificate error causing client install error

Hey Justin,

Sorry you are having issues with this. While we work on a fix for this the workaround is to call --bootstrap-url [https://www.opscode.com/chef/install.sh](https://www.opscode.com/chef/install.sh) with your knife bootstrap command.

Please let me know if you have any questions.

- cwebber

On Mar 20, 2015, at 13:30, Justin Franks \<[justin.franks@lithium.com](mailto:justin.franks@lithium.com)[mailto:justin.franks@lithium.com](mailto:justin.franks@lithium.com)\> wrote:

Connecting to 10.161.66.83  
10.161.66.83 Installing Chef Client…  
10.161.66.83 --2015-03-20 20:15:34-- [https://www.chef.io/chef/install.sh](https://www.chef.io/chef/install.sh)  
10.161.66.83 Resolving [www.chef.io](http://www.chef.io)[http://www.chef.io/](http://www.chef.io/)… 199.27.79.65  
10.161.66.83 Connecting to [www.chef.io](http://www.chef.io)[http://www.chef.io/](http://www.chef.io/)|199.27.79.65|:443… connected.  
10.161.66.83 ERROR: certificate common name “[g.ssl.fastly.net](http://g.ssl.fastly.net)[http://g.ssl.fastly.net/](http://g.ssl.fastly.net/)” doesn’t match requested host name “[www.chef.io](http://www.chef.io)[http://www.chef.io/](http://www.chef.io/)”.  
10.161.66.83 To connect to [www.chef.io](http://www.chef.io)[http://www.chef.io/](http://www.chef.io/) insecurely, use ‘–no-check-certificate’.  
10.161.66.83 Starting first Chef Client run…  
10.161.66.83 bash: line 96: chef-client: command not found?  
Errrr… ummm…

* * *

Justin Franks  
Lead Operations Engineer  
SaaS, Cloud, Data Centers & Infrastructure  
Lithium Technologies, Inc  
225 Bush St., 15th Floor  
San Francisco, CA 94104  
tel: +1 415 757 3100 x3219

---

<div class="post-metadata">

**Author:** ![AJ\_Christensen2](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/aj_christensen2/32/42_2.png) [@AJ\_Christensen2](https://discourse.chef.io/u/AJ_Christensen2)\
**Post date:** [March 20, 2015, 9:10pm UTC](https://discourse.chef.io/t/chef-io-certificate-error-causing-client-install-error/6439/4 "2015-03-20T21:10:28Z")

</div>

You can get the packages from here:  
[https://packagecloud.io/chef/stable](https://packagecloud.io/chef/stable) then add to a local repository  
with createrepo or reprepro, aptly, type stuff.

You can even add the packagecloud repos to your system with the  
packagecloud\_repo lwrp.

cheers,

--aj

On Sat, Mar 21, 2015 at 9:43 AM, Justin Franks  
[justin.franks@lithium.com](mailto:justin.franks@lithium.com) wrote:

> I would like to tell our chef servers to pull the client from out repo and  
> not from a public place. What do I edit on the server?
> 
> * * *
> 
> Justin Franks  
> Lead Operations Engineer  
> SaaS, Cloud, Data Centers & Infrastructure  
> Lithium Technologies, Inc  
> 225 Bush St., 15th Floor  
> San Francisco, CA 94104  
> tel: +1 415 757 3100 x3219
> 
> * * *
> 
> From: Christopher Webber [cwebber@chef.io](mailto:cwebber@chef.io)  
> Sent: Friday, March 20, 2015 1:33 PM  
> To: [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
> Subject: [chef] Re: [Chef.io](http://Chef.io) certificate error causing client install error
> 
> Hey Justin,
> 
> Sorry you are having issues with this. While we work on a fix for this the  
> workaround is to call --bootstrap-url  
> [https://www.opscode.com/chef/install.sh](https://www.opscode.com/chef/install.sh) with your knife bootstrap command.
> 
> Please let me know if you have any questions.
> 
> — cwebber
> 
> On Mar 20, 2015, at 13:30, Justin Franks [justin.franks@lithium.com](mailto:justin.franks@lithium.com) wrote:
> 
> Connecting to 10.161.66.83  
> 10.161.66.83 Installing Chef Client...  
> 10.161.66.83 --2015-03-20 20:15:34-- [https://www.chef.io/chef/install.sh](https://www.chef.io/chef/install.sh)  
> 10.161.66.83 Resolving [www.chef.io](http://www.chef.io)... 199.27.79.65  
> 10.161.66.83 Connecting to www.chef.io|199.27.79.65|:443... connected.  
> 10.161.66.83 ERROR: certificate common name “[g.ssl.fastly.net](http://g.ssl.fastly.net)” doesn’t match  
> requested host name “[www.chef.io](http://www.chef.io)”.  
> 10.161.66.83 To connect to [www.chef.io](http://www.chef.io) insecurely, use  
> ‘--no-check-certificate’.  
> 10.161.66.83 Starting first Chef Client run...  
> 10.161.66.83 bash: line 96: chef-client: command not found  
> Errrr... ummm...
> 
> * * *
> 
> Justin Franks  
> Lead Operations Engineer  
> SaaS, Cloud, Data Centers & Infrastructure  
> Lithium Technologies, Inc  
> 225 Bush St., 15th Floor  
> San Francisco, CA 94104  
> tel: +1 415 757 3100 x3219

---

<div class="post-metadata">

**Author:** ![Lamont\_Granquist](https://avatars.discourse-cdn.com/v4/letter/l/d26b3c/32.png) [@Lamont\_Granquist](https://discourse.chef.io/u/Lamont_Granquist)\
**Post date:** [March 20, 2015, 9:11pm UTC](https://discourse.chef.io/t/chef-io-certificate-error-causing-client-install-error/6439/5 "2015-03-20T21:11:04Z")

</div>

--bootstrap-install-command on the CLI or  
knife[:bootstrap\_install\_command] in knife.rb can be used to bypass  
install.sh entirely and you can dpkg install or rpm install straight  
from a URL.

On 3/20/15 1:43 PM, Justin Franks wrote:

> ​I would like to tell our chef servers to pull the client from out  
> repo and not from a public place. What do I edit on the server?
> 
> * * *
> 
> ## Justin Franks Lead Operations Engineer SaaS, Cloud, Data Centers & Infrastructure Lithium Technologies, Inc 225 Bush St., 15th Floor San Francisco, CA 94104 tel: +1 415 757 3100 x3219
> 
> _From:_ Christopher Webber [cwebber@chef.io](mailto:cwebber@chef.io)  
> _Sent:_ Friday, March 20, 2015 1:33 PM  
> _To:_ [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
> _Subject:_ [chef] Re: [Chef.io](http://Chef.io) certificate error causing client install  
> error  
> Hey Justin,
> 
> Sorry you are having issues with this. While we work on a fix for this  
> the workaround is to call --bootstrap-url  
> [https://www.opscode.com/chef/install.sh](https://www.opscode.com/chef/install.sh) with your knife bootstrap command.
> 
> Please let me know if you have any questions.
> 
> — cwebber
> 
> > On Mar 20, 2015, at 13:30, Justin Franks \<[justin.franks@lithium.com](mailto:justin.franks@lithium.com)  
> > [mailto:justin.franks@lithium.com](mailto:justin.franks@lithium.com)\> wrote:
> > 
> > Connecting to 10.161.66.83  
> > 10.161.66.83 Installing Chef Client...  
> > 10.161.66.83 --2015-03-20 20:15:34-- [https://www.chef.io/chef/install.sh](https://www.chef.io/chef/install.sh)  
> > 10.161.66.83 [Resolvingwww.chef.io](http://Resolvingwww.chef.io) [http://www.chef.io/](http://www.chef.io/)... 199.27.79.65  
> > 10.161.66.83 Connecting [towww.chef.io](http://towww.chef.io)  
> > [http://www.chef.io/](http://www.chef.io/)|199.27.79.65|:443... connected.  
> > 10.161.66.83 ERROR: certificate common name “[g.ssl.fastly.net](http://g.ssl.fastly.net)  
> > [http://g.ssl.fastly.net/](http://g.ssl.fastly.net/)” doesn’t match requested host name  
> > “[www.chef.io](http://www.chef.io) [http://www.chef.io/](http://www.chef.io/)”.  
> > 10.161.66.83 To connect [towww.chef.io](http://towww.chef.io)  
> > [http://www.chef.io/](http://www.chef.io/)insecurely, use ‘--no-check-certificate’.  
> > 10.161.66.83 Starting first Chef Client run...  
> > 10.161.66.83 bash: line 96: chef-client: command not found​  
> > Errrr... ummm...
> > 
> > * * *
> > 
> > Justin Franks  
> > Lead Operations Engineer  
> > SaaS, Cloud, Data Centers & Infrastructure  
> > Lithium Technologies, Inc  
> > 225 Bush St., 15th Floor  
> > San Francisco, CA 94104  
> > tel: +1 415 757 3100 x3219

---

<div class="post-metadata">

**Author:** ![Chris\_F](https://avatars.discourse-cdn.com/v4/letter/c/fbc32d/32.png) [@Chris\_F](https://discourse.chef.io/u/Chris_F)\
**Post date:** [March 21, 2015, 4:10pm UTC](https://discourse.chef.io/t/chef-io-certificate-error-causing-client-install-error/6439/6 "2015-03-21T16:10:04Z")

</div>

[https://docs.chef.io/config\_rb\_knife.html](https://docs.chef.io/config_rb_knife.html)

Where is this documented? That option is not in the list above.

Chris

From: Lamont Granquist [[mailto:lamont@chef.io](mailto:lamont@chef.io)]  
Sent: Friday, March 20, 2015 5:11 PM  
To: [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
Cc: Justin Franks  
Subject: [chef] Re: Re: Re: [Chef.io](http://Chef.io) certificate error causing client install error

–bootstrap-install-command on the CLI or knife[:bootstrap\_install\_command] in knife.rb can be used to bypass [install.sh](http://install.sh) entirely and you can dpkg install or rpm install straight from a URL.

On 3/20/15 1:43 PM, Justin Franks wrote:

​I would like to tell our chef servers to pull the client from out repo and not from a public place. What do I edit on the server?

* * *

Justin Franks  
Lead Operations Engineer  
SaaS, Cloud, Data Centers & Infrastructure  
Lithium Technologies, Inc  
225 Bush St., 15th Floor  
San Francisco, CA 94104  
tel: +1 415 757 3100 x3219

* * *

From: Christopher Webber [cwebber@chef.io](mailto:cwebber@chef.io)[mailto:cwebber@chef.io](mailto:cwebber@chef.io)  
Sent: Friday, March 20, 2015 1:33 PM  
To: [chef@lists.opscode.com](mailto:chef@lists.opscode.com)[mailto:chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
Subject: [chef] Re: [Chef.io](http://Chef.io) certificate error causing client install error

Hey Justin,

Sorry you are having issues with this. While we work on a fix for this the workaround is to call --bootstrap-url [https://www.opscode.com/chef/install.sh](https://www.opscode.com/chef/install.sh) with your knife bootstrap command.

Please let me know if you have any questions.

— cwebber

On Mar 20, 2015, at 13:30, Justin Franks \<[justin.franks@lithium.com](mailto:justin.franks@lithium.com)[mailto:justin.franks@lithium.com](mailto:justin.franks@lithium.com)\> wrote:

Connecting to 10.161.66.83  
10.161.66.83 Installing Chef Client…  
10.161.66.83 --2015-03-20 20:15:34-- [https://www.chef.io/chef/install.sh](https://www.chef.io/chef/install.sh)  
10.161.66.83 Resolving [www.chef.io](http://www.chef.io)[http://www.chef.io/](http://www.chef.io/)… 199.27.79.65  
10.161.66.83 Connecting to [www.chef.io](http://www.chef.io)[http://www.chef.io/](http://www.chef.io/)|199.27.79.65|:443… connected.  
10.161.66.83 ERROR: certificate common name “[g.ssl.fastly.net](http://g.ssl.fastly.net)[http://g.ssl.fastly.net/](http://g.ssl.fastly.net/)” doesn’t match requested host name “[www.chef.io](http://www.chef.io)[http://www.chef.io/](http://www.chef.io/)”.  
10.161.66.83 To connect to [www.chef.io](http://www.chef.io)[http://www.chef.io/](http://www.chef.io/) insecurely, use ‘–no-check-certificate’.  
10.161.66.83 Starting first Chef Client run…  
10.161.66.83 bash: line 96: chef-client: command not found​  
Errrr… ummm…

* * *

Justin Franks  
Lead Operations Engineer  
SaaS, Cloud, Data Centers & Infrastructure  
Lithium Technologies, Inc  
225 Bush St., 15th Floor  
San Francisco, CA 94104  
tel: +1 415 757 3100 x3219

---

<div class="post-metadata">

**Author:** ![Lamont\_Granquist](https://avatars.discourse-cdn.com/v4/letter/l/d26b3c/32.png) [@Lamont\_Granquist](https://discourse.chef.io/u/Lamont_Granquist)\
**Post date:** [March 21, 2015, 5:03pm UTC](https://discourse.chef.io/t/chef-io-certificate-error-causing-client-install-error/6439/7 "2015-03-21T17:03:09Z")

</div>

Probably missing from the docs.

[https://github.com/chef/chef/blob/master/lib/chef/knife/bootstrap.rb#L173-L175](https://github.com/chef/chef/blob/master/lib/chef/knife/bootstrap.rb#L173-L175)  
[https://github.com/chef/chef/blob/master/lib/chef/knife/bootstrap/templates/chef-full.erb#L22-L24](https://github.com/chef/chef/blob/master/lib/chef/knife/bootstrap/templates/chef-full.erb#L22-L24)

On 3/21/15 9:10 AM, Fouts, Chris wrote:

> [config.rb](https://docs.chef.io/config_rb_knife.html)
> 
> Where is this documented? That option is not in the list above.
> 
> Chris
> 
> \*From:\*Lamont Granquist [[mailto:lamont@chef.io](mailto:lamont@chef.io)]  
> _Sent:_ Friday, March 20, 2015 5:11 PM  
> _To:_ [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
> _Cc:_ Justin Franks  
> _Subject:_ [chef] Re: Re: Re: [Chef.io](http://Chef.io) certificate error causing client  
> install error
> 
> --bootstrap-install-command on the CLI or  
> knife[:bootstrap\_install\_command] in knife.rb can be used to bypass  
> install.sh entirely and you can dpkg install or rpm install straight  
> from a URL.
> 
> On 3/20/15 1:43 PM, Justin Franks wrote:
> 
> ```
> ​ I would like to tell our chef servers to pull the client from
> out repo and not from a public place. What do I edit on the server?
> 
> *************************
> Justin Franks
> Lead Operations Engineer
> SaaS, Cloud, Data Centers & Infrastructure
> Lithium Technologies, Inc
> 225 Bush St., 15th Floor
> San Francisco, CA 94104
> tel: +1 415 757 3100 x3219
> 
> ------------------------------------------------------------------------
> 
> *From:*Christopher Webber <cwebber@chef.io> <mailto:cwebber@chef.io>
> *Sent:* Friday, March 20, 2015 1:33 PM
> *To:* chef@lists.opscode.com <mailto:chef@lists.opscode.com>
> *Subject:* [chef] Re: Chef.io certificate error causing client
> install error
> 
> Hey Justin,
> 
> Sorry you are having issues with this. While we work on a fix for
> this the workaround is to call --bootstrap-url
> https://www.opscode.com/chef/install.sh with your knife bootstrap
> command.
> 
> Please let me know if you have any questions.
> 
> — cwebber
> 
> On Mar 20, 2015, at 13:30, Justin Franks
> <justin.franks@lithium.com <mailto:justin.franks@lithium.com>>
> wrote:
> 
> Connecting to 10.161.66.83
> 
> 10.161.66.83 Installing Chef Client...
> 
> 10.161.66.83 --2015-03-20 20:15:34--
> https://www.chef.io/chef/install.sh
> 
> 10.161.66.83 Resolvingwww.chef.io <http://www.chef.io/>...
> 199.27.79.65
> 
> 10.161.66.83 Connecting towww.chef.io
> <http://www.chef.io/>|199.27.79.65|:443... connected.
> 
> 10.161.66.83 ERROR: certificate common name “g.ssl.fastly.net
> <http://g.ssl.fastly.net/>” doesn’t match requested host name
> “www.chef.io <http://www.chef.io/>”.
> 
> 10.161.66.83 To connect towww.chef.io
> <http://www.chef.io/>insecurely, use ‘--no-check-certificate’.
> 
> 10.161.66.83 Starting first Chef Client run...
> 
> 10.161.66.83 bash: line 96: chef-client: command not found​
> 
> Errrr... ummm...
> 
> *************************
> Justin Franks
> Lead Operations Engineer
> SaaS, Cloud, Data Centers & Infrastructure
> Lithium Technologies, Inc
> 225 Bush St., 15th Floor
> San Francisco, CA 94104
> tel: +1 415 757 3100 x3219
> 
> ```