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

Error returned when running vagrant digitalocean-list #231

Open
gl40014001 opened this issue Feb 15, 2016 · 1 comment
Open

Error returned when running vagrant digitalocean-list #231

gl40014001 opened this issue Feb 15, 2016 · 1 comment

Comments

@gl40014001
Copy link

Running from a DO droplet .. Ubuntu 14 04 x64.

At prompt, typing
vagrant digitalocean-list images

..with token being long string generated via DO token generation page, I get a stream of ruby related errors.. first line indicates cert issue.

Per tutuorial at DO site, I have appended "export SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt" to ~/.bashrc

error output follows. Any assistance greatly appreciated.

# vagrant digitalocean-list images <token string removed> /opt/vagrant/embedded/lib/ruby/2.2.0/net/http.rb:923:inconnect': SSL_connect returned=1 errno=0 state=error: certificate verify failed (Faraday::SSLError)
from /opt/vagrant/embedded/lib/ruby/2.2.0/net/http.rb:923:in block in connect' from /opt/vagrant/embedded/lib/ruby/2.2.0/timeout.rb:73:intimeout'
from /opt/vagrant/embedded/lib/ruby/2.2.0/net/http.rb:923:in connect' from /opt/vagrant/embedded/lib/ruby/2.2.0/net/http.rb:863:indo_start'
from /opt/vagrant/embedded/lib/ruby/2.2.0/net/http.rb:852:in start' from /opt/vagrant/embedded/lib/ruby/2.2.0/net/http.rb:1375:inrequest'
from /opt/vagrant/embedded/lib/ruby/2.2.0/net/http.rb:1133:in get' from /root/.vagrant.d/gems/gems/faraday-0.9.2/lib/faraday/adapter/net_http.rb:80:inperform_request'
from /root/.vagrant.d/gems/gems/faraday-0.9.2/lib/faraday/adapter/net_http.rb:40:in block in call' from /root/.vagrant.d/gems/gems/faraday-0.9.2/lib/faraday/adapter/net_http.rb:87:inwith_net_http_connection'
from /root/.vagrant.d/gems/gems/faraday-0.9.2/lib/faraday/adapter/net_http.rb:32:in call' from /root/.vagrant.d/gems/gems/faraday-0.9.2/lib/faraday/request/url_encoded.rb:15:incall'
from /root/.vagrant.d/gems/gems/faraday-0.9.2/lib/faraday/rack_builder.rb:139:in build_response' from /root/.vagrant.d/gems/gems/faraday-0.9.2/lib/faraday/connection.rb:377:inrun_request'
from /root/.vagrant.d/gems/gems/faraday-0.9.2/lib/faraday/connection.rb:140:in get' from /root/.vagrant.d/gems/gems/vagrant-digitalocean-0.7.10/lib/vagrant-digitalocean/commands/list.rb:72:inquery'
from /root/.vagrant.d/gems/gems/vagrant-digitalocean-0.7.10/lib/vagrant-digitalocean/commands/list.rb:33:in execute' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/cli.rb:42:inexecute'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/environment.rb:302:in cli' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/bin/vagrant:174:in

'

`

@seth-reeser
Copy link
Member

To clarify - you're running Vagrant from within a DigitalOcean droplet?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants