Chef.io certificate error causing client install error

Justin_Franks · March 20, 2015, 8:30pm

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 Resolving 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” doesn’t match requested host name “www.chef.io”.
10.161.66.83 To connect to 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

cwebber · March 20, 2015, 8:33pm

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 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 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 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

Justin_Franks · March 20, 2015, 8:43pm

?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
Sent: Friday, March 20, 2015 1:33 PM
To: 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 Resolving www.chef.io http://www.chef.io/… 199.27.79.65
10.161.66.83 Connecting to 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/” 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

AJ_Christensen2 · March 20, 2015, 9:10pm

You can get the packages from here:
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 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
Sent: Friday, March 20, 2015 1:33 PM
To: 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 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 Resolving 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” doesn’t match
requested host name “www.chef.io”.
10.161.66.83 To connect to 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

Lamont_Granquist · March 20, 2015, 9:11pm

--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
Sent: Friday, March 20, 2015 1:33 PM
To: 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

Chris_F · March 21, 2015, 4:10pm

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]
Sent: Friday, March 20, 2015 5:11 PM
To: chef@lists.opscode.com
Cc: Justin Franks
Subject: [chef] Re: Re: Re: 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 Resolving www.chef.io http://www.chef.io/… 199.27.79.65
10.161.66.83 Connecting to 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/” 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

Lamont_Granquist · March 21, 2015, 5:03pm

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/templates/chef-full.erb#L22-L24

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

config.rb

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

Chris

*From:*Lamont Granquist [mailto:lamont@chef.io]
Sent: Friday, March 20, 2015 5:11 PM
To: chef@lists.opscode.com
Cc: Justin Franks
Subject: [chef] Re: Re: Re: 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

Topic		Replies	Views
Hostname does not match the server certificate Chef Infra (archive)	3	2353	September 28, 2016
Chef Server certificates Problem Chef Infra (archive)	2	420	May 31, 2019
Just ran chef-server-ctl reconfigure by mistake and now CHEF is broken :-( Chef Infra (archive)	2	870	August 18, 2016
SSL Cert Error Chef Infra (archive)	4	354	March 27, 2015
Error: The SSL certificate of "Chef Server name" could not be verified Chef Infra (archive)	2	1395	June 9, 2016

Chef.io certificate error causing client install error

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

Related Topics

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