Issue
I'm trying to launch a rails application to Elastic Beanstalk.
On the tutorial here: rel="nofollow">http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_Ruby_rails.html
I'm on step 6.3 where it covers updating the application.
eb status --verbose
returns ready and green.
Although, the page that displays at the url it gives me says:
"The page you were looking for doesn't exist.
You may have mistyped the address or the page may have moved."
The tutorial is expecting the "Welcome aboard You’re riding Ruby on Rails!" page to render.
What might be the issue here? I'm pretty new at this so I'm not sure where to begin diagnosing the issue.
I've ran rails s for this apps local directory and it does display the "Welcome aboard You’re riding Ruby on Rails!" page properly.
Thanks!
When I do eb status --verbose it does return green and ready although just before that it gives me this error twice like this:
error: git-credential-osxkeychain died of signal 11
error: git-credential-osxkeychain died of signal 11
I followed the tutorial here https://help.github.com/articles/set-up-git to fix this signal 11 error. The error is gone, although visiting the url where my site is located still gives me the same error page.
Ok I fixed the signal 11 error, although its still not rendering the Ruby on Rails welcome page.
When I create an Application from the Elastic Beanstalk UI the Sample Application works fine. But when I upload the app files on my computer to EB and deploy the link to view the app says "403 Forbidden".
Again, this is just a plain vanilla app that works fine locally.
EB UI says "Green and Healthy" as well.
I reinstalled git and consequently updated it, and then just continued on with the tutorial even though the correct page still isn't rendering. Basically I completed the tutorial except for the termination part.
Now I get a 502 Bad Gateway error.
Using "eb log" I found that I keep getting a message about installing mysql2 and adding it to the gemfile, which I have already done and ran "bundle install". Nada.
It is, however, included in my gem list.
Solution
Of course there are not many clues of what might be wrong, but you can have a look at the log after connecting to your instance through ssh.
In short:
connect to your instance through ssh
go to /var/app/current/log
read the production.log file
Answered By - Miotsu Answer Checked By - Terry (WPSolving Volunteer)