It seems to be the issue with rack and the host that it's binding to. Try running the Rails server and bind it to 0.0.0.0
Evan — Evan Machnic @emachnic On Mon, Oct 6, 2014 at 10:09 PM, Thiago Dias <tdta...@gmail.com> wrote: > Just wondering if you've solved this issue. I'm experiencing the exact same > problem. > On Saturday, September 20, 2014 8:51:16 AM UTC-3, emachnic wrote: >> >> His Colin, >> >> There's nothing in the terminal window during the request. I didn't use >> the update task, just updated in the Gemfile. >> >> Evan >> — >> Evan Machnic >> @emachnic >> >> >> On Sat, Sep 20, 2014 at 3:49 AM, Colin Law <cla...@gmail.com <javascript:> >> > wrote: >> >>> On 19 September 2014 22:56, emachnic <emac...@engineyard.com >>> <javascript:>> 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 a topic in the >>> Google Groups "Ruby on Rails: Core" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/rubyonrails-core/sd38-TuVTNI/unsubscribe. >>> >>> To unsubscribe from this group and all its topics, send an email to >>> rubyonrails-co...@googlegroups.com <javascript:>. >>> To post to this group, send email to rubyonra...@googlegroups.com >>> <javascript:>. >>> Visit this group at http://groups.google.com/group/rubyonrails-core. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> > -- > You received this message because you are subscribed to a topic in the Google > Groups "Ruby on Rails: Core" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/rubyonrails-core/sd38-TuVTNI/unsubscribe. > To unsubscribe from this group and all its topics, 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. -- 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.
