-
Notifications
You must be signed in to change notification settings - Fork 380
'Installing Heroku Toolbelt v4' fails #1758
Comments
I got this error too.
error log:
And I try to debug it...
I found this url cause the error: The params body is
There's no connection problem when access to
|
There should be a 60 second timeout when connecting. Is it taking that long? |
Yes, every time is timeout, toolbelt 3.42.15 works well, but what's wrong with v4? |
Hey @gmahajan31 , I add this to Excon.defaults[:read_timeout] = 3600 |
I suppose I could increase the timeout a bit, but that's a pretty high time. Any idea how long it took to connect on your connection? This file is served over cloudfront so it's a bit strange it took that long. |
You could run |
Maybe it's cause by cloudfront? Are they deploy some nodes in China or Asia? My location is Beijing, China. But, toolbelt v3 works fine...
|
The next release will have a longer timeout for this request |
I am also in Beijing, China and have the same timeout error |
Timeout increased |
I am still getting this error, I have increased the timeout but still there are errors, I did increase the timeout in jsplugin.rb file, but no success
|
Is it taking a full hour? |
Hey @dickeyxxx I tried once again and finally it did get upgraded. Thanks |
I am in Nanjing, China and I got this error too.
|
Location Hangzhou China, seems like it needs hours to download:
|
There isn't anything we can do to deliver that file more quickly, it's already served by a CDN. |
Delhi, India Error: connect timeout reached (Excon::Errors::Timeout) |
@rneha725 did you increate the timeout in jsplugin.rb
|
@rneha725 If increasing the timeout does not help, you may want to have your sysadmin check your proxy logs, the proxy server is another place at which this could happen. |
When I run the heroku command, it is trying to update the heroku toolbelt to v4. But it fails with a timeout exception. Here is a complete log.
$ heroku
Installing Heroku Toolbelt v4...heroku login ! Heroku client internal error.
! Search for help at: https://help.heroku.com
! Or report a bug at: https://github.com/heroku/heroku/issues/new
Can someone guide me on what steps to take?
The text was updated successfully, but these errors were encountered: