I've setuped a atom feed in development on CodeAnyWhere with this url :
http://mydevsite.codeanyapp.com:3000/posts.atom ...and everything is ok
When i push it in production to heroku here :
http://myprodsite.heroku.com/posts.atom
...i've an error --> "We're sorry, but something went wrong.
If you are the application owner check the logs for more information.
I don't know where it comes :(((
Cheers!
There might be some exception on heroku
please check log by using command heroku logs from terminal. Resolved the issue and then again deploy it on heroku.
Related
I am recently using the rubymine(ruby on rails 4) to create web pages and once I have finished some functions and run correctly,I push my code to heroku, so I can directly run the app on the heroku.
The problem is that every function could run correctly on the heroku just like running it at local except one: There is a link in one page called "calendar" to a calendar function,I can run it correctly at local, but on heroku, it goes wrong saying "we are sorry but something went wrong"
enter image description here
someone can explain to me how could it happen? Is it a bug of the heroku system, like a compatibility issue? I have push my code to heroku and run correctly many times and it won't be wrong in the push process.
here is my heroku link: https://dashboard.heroku.com/apps/clients-to-horse
Sugession
I will recommend you, please run your application on local in production mode(environment) after assets precompile, if everything will work properly then I am sure on Heroku will run also.
After deploy on Heroku make sure for migration and assets precompile for Heroku.
You are saying error as "we are sorry but something went wrong", this always comes when we miss something from our side or code bug in the application.
I am trying to deploy my rails application. After I performed cap deploy production everything worked perfectly. Then I restarted nginx server, it showed OK status.
I opened the address in Browser and I get 500 error, We're sorry but some thing went wrong!
I opened the log using less log/production.log , it is showing me all the migrations and seed running perfectly. But there is no sign of pages getting loaded.
I can't see any sign of GET requests going on! Can anyone tell me a way to get over this!
Thank you!
I have hosted a ror app in aws ec2. Development env works fine but when i start production mode it says - "We're sorry, but something went wrong.We've been notified about this issue and we'll take a look at it shortly."
I chechked production.log
production.log
[2015-07-02T16:37:21.257777 #12834] INFO -- : Migrating to <Table Name> (20150608154559)
Like this all table name are shown with a migrating msg.
Is this is an error? How to resolve this ?
I tried running its production mode in localhost where it displayed the error was due to secret_key_base.
I am trying to upload a video on heroku use the 'carrierwave' and 'streamio-ffmpeg'.
I've movement without any problems at local,
As a result of deploying the same thing to heroku,
Uploaded point in time
”We're sorry, but something went wrong.
If you are the application owner check the logs for more information”
and you get an error.
I think what should I install ffmpeg on Heroku but does not go well even try various.
And how do you will be able to upload videos on heroku if?
It should be noted that, although I see a question that is similar, "heroku run rake db: migrate" In my problem did not resolve.
Run the command in your terminal heroku logs.You will find the errors in the logs.
I have my app in production mode in my linode account and I get in one page a 500 internal server error the message:
We're sorry, but something went wrong.
However in my development environment works fine this page.
How can I debug this error?
How can I see the error origin in my production mode?
I want that rails show errors in production mode.
How can I do it?
Thank you!
If you have access to ssh, log in to your server via ssh and go to your rails log directory, which is inside your rails directory.
Once you are there run the command tail production.log . If this doesn't give you enough information you can also do a tail -n100 production.log (gives you last hundred lines of the production log).
If you have deployed via heroku, then you can access the logs by running heroku logs in your local console. (more information here https://devcenter.heroku.com/articles/logging)
I also find it helpful to use the exception_notification gem https://github.com/rails/exception_notification when running in production, as it emails you a stacktrace when an error occurs. Plenty of others also use Hoptoad (http://hoptoadapp.com/) or Exceptional (http://www.exceptional.io/) however i prefer the simple exception_notification gem.
Also, in some rare occasions when i can't trace the error as a final measure i sometimes open up port 3000 temporarily on the remote server firewall and cd to the rails project and run rails server production with the log level set to debug in config/environments/production.rb so i can see the error in the console, and then close off the port when i have finished.
Hope that helps.
tail -n100 production.log
will only show the last 100 lines of the log file. Just in case you want to see the log running in real time.
use this
tail -1000f log/production.log