Note that there are some explanatory texts on larger screens.

plurals
  1. POheroku keys:add error: "non-blocking socket operation could not be completed"
    primarykey
    data
    text
    <p>I'm a beginner on Ruby on Rails, Git and Heroku. I am following the Rails Tutorial behind a corporate proxy. So far I am able to install RailsInstaller that helped me set up Ruby, Rails, and Git (also GitHub) rather smoothly. But I am really stuck on the section (http://ruby.railstutorial.org/ruby-on-rails-tutorial-book#sec:1.4.1), where I am trying to link my public key to my new Heroku account to push the repository to Heroku.</p> <p>I am on a Windows 7 box behind a corp proxy. I have my HTTP_PROXY env variable set up and it is working for my push to GitHub. I'm not able to get past the following error. It does not seem to get to the point of complaining about ssh public key and the other posts here about heroku keys:add errors have different output.. And I haven't located relevant info at help.heroku.com. Any insights would be greatly appreciated!</p> <pre><code>c:\Sites\testproj\thirdapp&gt;heroku keys:add Enter your Heroku credentials. Email: my.email@gmail.com Password (typing will be hidden): ! Heroku client internal error. ! Search for help at: https://help.heroku.com ! Or report a bug at: https://github.com/heroku/heroku/issues/new Error: A non-blocking socket operation could not be completed immediately. (Excon::Errors::SocketError) Backtrace: C:/RailsInstaller/Ruby1.9.3/lib/ruby/1.9.1/openssl/buffering.rb:53:in `sysread' C:/RailsInstaller/Ruby1.9.3/lib/ruby/1.9.1/openssl/buffering.rb:53:in `sysread' C:/RailsInstaller/Ruby1.9.3/lib/ruby/1.9.1/openssl/buffering.rb:53:in `fill_rbuff' C:/RailsInstaller/Ruby1.9.3/lib/ruby/1.9.1/openssl/buffering.rb:293:in `eof?' C:/RailsInstaller/Ruby1.9.3/lib/ruby/1.9.1/openssl/buffering.rb:246:in `readline' C:/RailsInstaller/Ruby1.9.3/lib/ruby/gems/1.9.1/gems/excon-0.14.0/lib/excon/ssl_socket.rb:68:in `initialize' C:/RailsInstaller/Ruby1.9.3/lib/ruby/gems/1.9.1/gems/excon-0.14.0/lib/excon/connection.rb:330:in `new' C:/RailsInstaller/Ruby1.9.3/lib/ruby/gems/1.9.1/gems/excon-0.14.0/lib/excon/connection.rb:330:in `socket' C:/RailsInstaller/Ruby1.9.3/lib/ruby/gems/1.9.1/gems/excon-0.14.0/lib/excon/connection.rb:175:in `request_kernel' C:/RailsInstaller/Ruby1.9.3/lib/ruby/gems/1.9.1/gems/excon-0.14.0/lib/excon/connection.rb:101:in `request' C:/RailsInstaller/Ruby1.9.3/lib/ruby/gems/1.9.1/gems/heroku-api-0.2.5/lib/heroku/api.rb:60:in `request' C:/RailsInstaller/Ruby1.9.3/lib/ruby/gems/1.9.1/gems/heroku-api-0.2.5/lib/heroku/api/login.rb:9:in `post_login' C:/RailsInstaller/Ruby1.9.3/lib/ruby/gems/1.9.1/gems/heroku-2.27.1/lib/heroku/auth.rb:74:in `api_key' C:/RailsInstaller/Ruby1.9.3/lib/ruby/gems/1.9.1/gems/heroku-2.27.1/lib/heroku/auth.rb:183:in `ask_for_credentials' C:/RailsInstaller/Ruby1.9.3/lib/ruby/gems/1.9.1/gems/heroku-2.27.1/lib/heroku/auth.rb:214:in `ask_for_and_save_credentials' C:/RailsInstaller/Ruby1.9.3/lib/ruby/gems/1.9.1/gems/heroku-2.27.1/lib/heroku/auth.rb:78:in `get_credentials' C:/RailsInstaller/Ruby1.9.3/lib/ruby/gems/1.9.1/gems/heroku-2.27.1/lib/heroku/command/keys.rb:66:in `add' C:/RailsInstaller/Ruby1.9.3/lib/ruby/gems/1.9.1/gems/heroku-2.27.1/lib/heroku/command.rb:176:in `run' C:/RailsInstaller/Ruby1.9.3/lib/ruby/gems/1.9.1/gems/heroku-2.27.1/lib/heroku/cli.rb:10:in `start' C:/RailsInstaller/Ruby1.9.3/lib/ruby/gems/1.9.1/gems/heroku-2.27.1/bin/heroku:16:in `&lt;top (required)&gt;' C:/RailsInstaller/Ruby1.9.3/bin/heroku:19:in `load' C:/RailsInstaller/Ruby1.9.3/bin/heroku:19:in `&lt;main&gt;' Command: heroku keys:add Version: heroku-gem/2.27.1 (i386-mingw32) ruby/1.9.3 </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload