-
Notifications
You must be signed in to change notification settings - Fork 89
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
Problem with SSL certificate #70
Comments
Never mind, it was a DO issue. They confirmed and repaired it. So now it works again. |
I am getting this again, now. |
If you also experience this, i found the following solution to fix this, taken from here. NOTE: [...] you may need to install a CA bundle to enable SSL communication with the Digital Ocean API. It is recommended to first install Homebrew. With Homebrew installed, run the following command to install the bundle:
Once the bundle is installed, add the following environment variable to your .bash_profile script and source it:
|
@d1rk Awesome, thanks, going to add that to the README. |
You're welcome. Thanks for your quick response. |
Hi,
I have been using tugboat without any issues for a few weeks now. All of the sudden it stopped working and says:
user@computer:~$ tugboat droplets
SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed!
/var/lib/gems/1.8/gems/tugboat-0.0.8/lib/tugboat/middleware/authentication_middleware.rb:24:in
call': undefined method
status' for nil:NilClass (NoMethodError)from /var/lib/gems/1.8/gems/faraday-0.8.8/lib/faraday/connection.rb:253:in
run_request' from /var/lib/gems/1.8/gems/faraday-0.8.8/lib/faraday/connection.rb:106:in
get'from /var/lib/gems/1.8/gems/digital_ocean-1.0.1/lib/digital_ocean/resource/droplet.rb:6:in
list' from /var/lib/gems/1.8/gems/tugboat-0.0.8/lib/tugboat/middleware/list_droplets.rb:8:in
call'from /var/lib/gems/1.8/gems/tugboat-0.0.8/lib/tugboat/middleware/inject_client.rb:33:in
call' from /var/lib/gems/1.8/gems/tugboat-0.0.8/lib/tugboat/middleware/check_configuration.rb:13:in
call'from /var/lib/gems/1.8/gems/tugboat-0.0.8/lib/tugboat/middleware/inject_configuration.rb:10:in
call' from /var/lib/gems/1.8/gems/middleware-0.1.0/lib/middleware/runner.rb:31:in
call'from /var/lib/gems/1.8/gems/middleware-0.1.0/lib/middleware/builder.rb:102:in
call' from /var/lib/gems/1.8/gems/tugboat-0.0.8/lib/tugboat/cli.rb:50:in
droplets'from /var/lib/gems/1.8/gems/thor-0.18.1/lib/thor/command.rb:27:in
__send__' from /var/lib/gems/1.8/gems/thor-0.18.1/lib/thor/command.rb:27:in
run'from /var/lib/gems/1.8/gems/thor-0.18.1/lib/thor/invocation.rb:120:in
invoke_command' from /var/lib/gems/1.8/gems/thor-0.18.1/lib/thor.rb:363:in
dispatch'from /var/lib/gems/1.8/gems/thor-0.18.1/lib/thor/base.rb:439:in
start' from /var/lib/gems/1.8/gems/tugboat-0.0.8/bin/tugboat:10 from /usr/local/bin/tugboat:19:in
load'from /usr/local/bin/tugboat:19
I have no idea what happened or what changed. It woked a few hours ago and I did not change anything (as far as I can tell).
Thanks,
David
The text was updated successfully, but these errors were encountered: