RoR App Only Getting 404 Errors

Discussion in 'General' started by dfberg, Feb 20, 2007.

  1. dfberg

    dfberg New Member

    Spent the evening troubleshooting this but couldn't get to the bottom. I followed the detailed step by step config guide in the wiki and have my "external app" and "context" settings configured per the wiki. Whenever I hit my RoR app I get a 404 error but the RoR welcome page shows up fine.

    I checked the main server log files error.log and stderr.log and nothing is out of the ordinary, stderr.log shows that one ENV warning but nothing else. The vhost log files are totally clean and there is nothing in my RoR app development.log file.

    I can run dispatch.lsapi from the command line and no errors are displayed.

    Only thing I noticed is when I have the doc root under the general tab in the vhost config set to the same as the "Location" field for my Rails context I get an error in the logs saying the context is invalid and because for some reason it appended another "public" to the end of the file path. But when I change the "Location" field in the Rails context so it references one folder above "public" then this error goes away.

    Maybe I'm missing something obvious here...?
  2. mistwang

    mistwang LiteSpeed Staff

    Please follow the easy configuration guide, in the step by step setup, you should not use a "Rails" context at all.
  3. dfberg

    dfberg New Member

    What about step 5 in the step by step guide?

    5) Create a LSAPI context for dispatcher.

    After reading both options in the wiki I got the impression that the easy configuration *might* be less powerful than the step by step guide so I decided to follow that instead.

    What are the real differences between the two different setups? One seems to use dispatch.lsapi and the other doesn't, does this matter?

    I apologize for the noob questions and I really appreciate your feedback.

    Thank you,

  4. mistwang

    mistwang LiteSpeed Staff

    step 5 is a "LSAPI" context not "RAILS" context, it is only for step by step configuration.

    The easy setup automates some steps in the step by step setup. Step by step setup is more flexible as you can customize it more. Behind the scene, they are almost identical.
  5. dfberg

    dfberg New Member

    Switched over to the easy configuration and got it working right away. So far it's blazing fast even in dev mode!


Share This Page