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

Windows 10 Install fails #446

Closed
cosmoneer opened this Issue May 10, 2017 · 4 comments

Comments

Projects
None yet
3 participants
@cosmoneer

Attempted installation on Windows 10 fails due to SSL Error.

Error appears related to this (now closed) issue:
#406
Following instructions for that issue had no effect.

The issue is related to the version of Ruby being installed (read about it here):
http://guides.rubygems.org/ssl-certificate-update/#installing-using-update-packages

Attempts to manually install the trust certificate also did not solve the problem, but created a new one.
http://guides.rubygems.org/ssl-certificate-update/#installing-using-update-packages

Note the error response below:

Downloading COSMOS_Windows_Install.zip
E:/CosmosRB/Vendor/Ruby/lib/ruby/2.2.0/rubygems/config_file.rb:333:in read': Is a directory @ rb_sysopen - E (Errno::EISDIR) from E:/CosmosRB/Vendor/Ruby/lib/ruby/2.2.0/rubygems/config_file.rb:333:inload_file'
from E:/CosmosRB/Vendor/Ruby/lib/ruby/2.2.0/rubygems/config_file.rb:200:in block in initialize' from E:/CosmosRB/Vendor/Ruby/lib/ruby/2.2.0/rubygems/config_file.rb:199:ineach'
from E:/CosmosRB/Vendor/Ruby/lib/ruby/2.2.0/rubygems/config_file.rb:199:in inject' from E:/CosmosRB/Vendor/Ruby/lib/ruby/2.2.0/rubygems/config_file.rb:199:ininitialize'
from E:/CosmosRB/Vendor/Ruby/lib/ruby/2.2.0/rubygems/gem_runner.rb:74:in new' from E:/CosmosRB/Vendor/Ruby/lib/ruby/2.2.0/rubygems/gem_runner.rb:74:indo_configuration'
from E:/CosmosRB/Vendor/Ruby/lib/ruby/2.2.0/rubygems/gem_runner.rb:39:in run' from E:/CosmosRB/Vendor/Ruby/bin/gem:21:in

'
ERROR: Problem updating gem to 2.4.4
INSTALL FAILED
Press any key to continue . . .

msoucy added a commit to msoucy/COSMOS that referenced this issue May 11, 2017

Use newer versions of gem
Due to an issue with ruby certificates, the version of gem that comes with the installer can't download files (see #446).

Manually download the latest and update to it per http://guides.rubygems.org/ssl-certificate-update/

msoucy added a commit to msoucy/COSMOS that referenced this issue May 11, 2017

Use newer versions of gem
Due to an issue with ruby certificates, the version of gem that comes with the installer can't download files (see #446).

Manually download the latest and update to it per http://guides.rubygems.org/ssl-certificate-update/
@KenErnandes

This comment has been minimized.

Show comment
Hide comment
@KenErnandes

KenErnandes May 16, 2017

I experienced the exact same problem. So I updated to the latest version [rubygems-2.6.12] in a new directory on my c: drive. But that didn't fix the problem.

When you try re-installing cosmos via the batch file, it immediately fails because the C:\COSMOS directory already exists. Delete the directory and the original problem repeats as it's apparently the batch file is working from the old rubygems version. This seems to be a chicken-and-egg situation. Will editing the batch file to point to the new version allow the install?

I experienced the exact same problem. So I updated to the latest version [rubygems-2.6.12] in a new directory on my c: drive. But that didn't fix the problem.

When you try re-installing cosmos via the batch file, it immediately fails because the C:\COSMOS directory already exists. Delete the directory and the original problem repeats as it's apparently the batch file is working from the old rubygems version. This seems to be a chicken-and-egg situation. Will editing the batch file to point to the new version allow the install?

@ryanatball

This comment has been minimized.

Show comment
Hide comment
@ryanatball

ryanatball May 16, 2017

Member

There is an updated version of the installer in progress here:
#451

But the easiest solution is to change line 12 in the existing bat file to use http instead of https. You can't have SSL issues if you dont use SSL.

Was:

:: Change Protocol to http if you have SSL issues
set PROTOCOL=https

Is:

:: Change Protocol to http if you have SSL issues
set PROTOCOL=http

Ryan

Member

ryanatball commented May 16, 2017

There is an updated version of the installer in progress here:
#451

But the easiest solution is to change line 12 in the existing bat file to use http instead of https. You can't have SSL issues if you dont use SSL.

Was:

:: Change Protocol to http if you have SSL issues
set PROTOCOL=https

Is:

:: Change Protocol to http if you have SSL issues
set PROTOCOL=http

Ryan

@KenErnandes

This comment has been minimized.

Show comment
Hide comment
@KenErnandes

KenErnandes May 16, 2017

@ryanatball

This comment has been minimized.

Show comment
Hide comment
@ryanatball

ryanatball May 30, 2017

Member

These issues should be resolved with the updated script today. If there are any additional SSL issues in the future that can be addressed by my earlier comment.

Member

ryanatball commented May 30, 2017

These issues should be resolved with the updated script today. If there are any additional SSL issues in the future that can be addressed by my earlier comment.

@ryanatball ryanatball closed this May 30, 2017

@ryanatball ryanatball modified the milestone: v4.0.0 Aug 4, 2017

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