Home>

About the rails tutorial "1.5.2 Deploy to Heroku (1)".
Even if you open the app page after deploying, is the initial page below? The screen remains displayed.

Heroku | Welcome to your new app!
Refer to the documentation if you need help deploying.</Code></pre>

<p>You can also run $git push origin master</p>
<pre><code>remote:!
remote:! Failed to install gems via Bundler.
remote:!


Does it mean that the Gemfile setting is strange?


  

$bundle install --without production

The dependency tzinfo-data (&gt;= 0) will be unused by any of the platforms Bundler is installing for.Bundler is installing for ruby ​​but the dependency is only for x86-mingw32, x86-mswin32, x64 -mingw32, java.To add those platforms to the bundle, run `bundle lock --add-platform x86-mingw32 x86-mswin32 x64-mingw32 java`.
Fetching gem metadata from https: //rubygems.org/..........
Fetching gem metadata from https://rubygems.org/.
Resolving dependencies ...
↓ The following is in red
Bundler could not find compatible versions for gem "activesupport":
  In snapshot (Gemfile.lock):
    activesupport (= 5.1.6)
  In Gemfile:
    rails (= 5.1.4) was resolved to 5.1.4, which depends on
      activesupport (= 5.1.4)
    coffee-rails (= 4.2.2) was resolved to 4.2.2, which depends on
      railties (&gt;= 4.0.0) was resolved to 5.1.6, which depends on
        activesupport (= 5.1.6)
Running `bundle update` will rebuild your snapshot from scratch, using
only
the gems in your Gemfile, which may resolve the conflict.
  

$bundle update

The dependency tzinfo-data (&gt;= 0) will be unused by any of the platforms Bundler is installing for.Bundler is installing for ruby ​​but the dependency is only for x86-mingw32, x86-mswin32, x64 -mingw32, java.To add those platforms to the bundle, run `bundle lock --add-platform x86-mingw32 x86-mswin32 x64-mingw32 java`.
Fetching source index from https://rubygems.org/
Retrying fetcher due to error (2/4): Bundler :: Fetcher :: CertificateFailureError Could not verify the SSL certificate for https://rubygems.org/.
There is a chance i am experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for verification.For information about OpenSSL certificates, see http://bit.ly/ruby- ssl.To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'.
Retrying fetcher due to error (3/4): Bundler :: Fetcher :: CertificateFailureError Could not verify the SSL certificate for https://rubygems.org/.
There is a chance i am experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for verification.For information about OpenSSL certificates, see http://bit.ly/ruby- ssl.To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'.
Retrying fetcher due to error (4/4): Bundler :: Fetcher :: CertificateFailureError Could not verify the SSL certificate for https://rubygems.org/.
There is a chance i am experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for verification.For information about OpenSSL certificates, see http://bit.ly/ruby- ssl.To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'.
↓ The following is in red
** Could not verify the SSL certificate for https://rubygems.org/.
There is a chance i am experiencing a man-in-the-middle attack, but
most likely your system doesn't have the CA certificates needed for
verification. For information about OpenSSL certificates, see
http://bit.ly/ruby-ssl.To connect without using SSL, edit your Gemfile
sources and change 'https' to 'http'. **
  • Answer # 1

      

    $bundle update

    followed by

      

    $bundle install

    Run

    .

  • Answer # 2

    Retrying fetcher due to error (2/4): Bundler :: Fetcher :: CertificateFailureError Could not verify the SSL certificate for https://rubygems.org/.
    There is a chance you are experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for verification.For information about OpenSSL certificates, see http://bit.ly/ruby- ssl.To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'.
    Retrying fetcher due to error (3/4): Bundler :: Fetcher :: CertificateFailureError Could not verify the SSL certificate for https://rubygems.org/.
    There is a chance you are experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for verification.For information about OpenSSL certificates, see http://bit.ly/ruby- ssl.To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'.
    Retrying fetcher due to error (4/4): Bundler :: Fetcher :: CertificateFailureError Could not verify the SSL certificate for https://rubygems.org/.
    There is a chance you are experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for verification.For information about OpenSSL certificates, see http://bit.ly/ruby- ssl. To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'.

    You need to resolve this first.
    Failure to perform a localbundle installbundle updatewill not generate theGemfile.lockrequired for Heroku deployment.

    Please refer to the following.

    https://qiita.com/JFCheval/items/91ba766b63878ff80d23
    https://StackOverflow.com/questions/52166