You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to login to the Inspec Compliance server at AWS (it's a fresh Opsworks + Chef Automate build) I receive the following error which has no information on google (yet).
/Users/josiah/.rvm/gems/ruby-2.4.0/gems/inspec-1.47.0/lib/bundles/inspec-compliance/api/login.rb:24:in `login': Unable to determine if https://chef-opsworks-<redacted>.us-west-2.opsworks-cm.io is a Chef Automate or Chef Compliance server (Compliance::API::Login::CannotDetermineServerType)
InSpec and Platform Version
Mac OS Sierra 10.12.1
Inspec 1.47.0
Replication Case
Install gem "inspec", this happens on both v1.43.8 and when I updated to the latest Inspec v1.47.0
Let Opsworks on AWS provision you an Opsworks + Chef Automate server
Note: I have added "Chef Manage" web interface to the server via CLI
Attempt to login via CLI: inspec compliance login https://chef-opsworks-<redacted>.us-west-2.opsworks-cm.io --insecure --user='admin' --token='<redacted>' --ent='default'
Possible Solutions
The inspec compliance login command attempts to hit up to two endpoints to figure out if what you’re asking us to login to is an older-generation Chef Compliance server, or a newer Chef Automate server. Given that you are referring to an Opsworks instance, I believe, it’s possible that those endpoints are filtered or returning data we don’t expect.
Description
When attempting to login to the Inspec Compliance server at AWS (it's a fresh Opsworks + Chef Automate build) I receive the following error which has no information on google (yet).
/Users/josiah/.rvm/gems/ruby-2.4.0/gems/inspec-1.47.0/lib/bundles/inspec-compliance/api/login.rb:24:in `login': Unable to determine if https://chef-opsworks-<redacted>.us-west-2.opsworks-cm.io is a Chef Automate or Chef Compliance server (Compliance::API::Login::CannotDetermineServerType)
InSpec and Platform Version
Mac OS Sierra 10.12.1
Inspec 1.47.0
Replication Case
inspec compliance login https://chef-opsworks-<redacted>.us-west-2.opsworks-cm.io --insecure --user='admin' --token='<redacted>' --ent='default'
Possible Solutions
The
inspec compliance login
command attempts to hit up to two endpoints to figure out if what you’re asking us to login to is an older-generation Chef Compliance server, or a newer Chef Automate server. Given that you are referring to an Opsworks instance, I believe, it’s possible that those endpoints are filtered or returning data we don’t expect.Stacktrace
https://gist.github.com/dcijj/9a25994f05999ed744894259276a5760
The text was updated successfully, but these errors were encountered: