Followed the directions here: http://docs.webfaction.com/software/rails.html And I have a new app called lab95. In my nginx/conf/nginx.conf file I have:
However, I get a "passenger" error when I try to access the page. http://vegan.webfactional.com/ asked 11 Jun '13, 17:27 vegan |
I don't know why I'm posting this but here is the solution: Hello, There appears to be something wrong with my setup where my production environment, using mysql will not work (website says "We're sorry, but something went wrong.") but using development (sqlite3) works just fine. I found the true cause of your error by setting the following value in your environments/production.rb file: config.consider_all_requests_local = true Here was the result (shown on the error page instead of the default worthless "something went wrong" message): Sprockets::Helpers::RailsHelper::AssetPaths::AssetNotPrecompiledError in Home#index Showing /home/vegan/webapps/lab95ror/lab95/app/views/layouts/application.html.erb where line #5 raised: kickstrap.css isn't precompiled ..So your problem was being caused by non-pre-compiled assets. I told Rails to auto-compile your assets by setting this in production.rb: config.assets.compile = true Now your site works: http://vegan.webfactional.com/ (I also disabled the "consider_all_requests_local" setting for your security.) Please do me a favor: summarize and post this solution onto the Community page so other people can also benefit from this solution. Let me know if you have any questions. Regards, Christopher S. WebFaction Support answered 13 Jun '13, 13:25 vegan You're posting it so that other users who run into the same problem can benefit from the solution. :)
(13 Jun '13, 13:41)
seanf
Obviously, seanf. The emphasis was on the letter "I", not on the act of posting it at all.
(13 Jun '13, 14:04)
vegan
|
The nginx log should provide more verbosity if you change the error log level to debug,
With this data you should be able to figure out why passenger is failing. answered 11 Jun '13, 21:57 johns Thanks, @johns However, last night the problem got worse, as I cannot start or stop the server itself:
(12 Jun '13, 06:36)
vegan
The pid in your ~/webapps/<application>/nginx/logs/nginx.pid does not match your current running nginx process. You will need to manually kill the process by first getting a list of your processes:
Then kill the nginx processes with:
After that you should be able to start with the standard bin/start and stop with bin/stop since the pid in nginx.pid should match now.
(12 Jun '13, 07:51)
timg ♦♦
Thanks. I killed those processes, the server is back up, I finally got it to write to the mysql database, now it just says "We're sorry, but something went wrong." on the page. The error log has been changed to verbose and now says:
(12 Jun '13, 08:41)
vegan
I followed the instructions here: http://docs.webfaction.com/software/rails.html#installing-multiple-gems-with-bundler When I switched the env to development, it worked fine, switching back to production, it gave me the same error. So I assume it has something to do with mysql. However, looking at the phpmyadmin of my mysql db, everything migrated and installed correctly (it appears).
(12 Jun '13, 09:08)
vegan
Please open a ticket at our support site so that we can look at your setup, and we'll help you find the cause of the issue.
(12 Jun '13, 09:31)
timg ♦♦
Thank you. I've submitted a ticket.
(12 Jun '13, 09:45)
vegan
showing 5 of 6
show 1 more comments
|