On 19 September 2014 22:56, emachnic <emach...@engineyard.com> wrote: > I have a Rails 4.1 app and I use Vagrant for developing it. Everything has > been working fine but then I bumped the version to 4.2 and it seems to have > broken somewhere. I can start the server just fine and get a 200 response > when curling localhost from the VM but when trying to access from a web > browser on the host I only get a blank page and nothing in the logs. I don't > think the requests are actually going through to the VM but I have no errors > or anything to help diagnose. This is repeatable for another person on my > team and I've also tried with a completely vanilla application. > > Has anyone experienced this or can help point to where I should look?
Assuming you are starting the server using rails server is there anything in the terminal window when you fetch the page? If not then I think the request must be being intercepted by something else on your system. Did you use rake rails:update to update the app? See http://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html Colin -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
