I want to turn my app into idling mode on Heroku. All I want is to trace my timeout app exception and fix it.
I installed Relic but it is too complicated to make it work. So I think I just need to fix this error on the client side.
You cannot "idle" your app manually.
You can scale it down though:
heroku ps:scale web=0
Related
Today I noticed that my bot was sending double messages (usually means that it's running 2 clients). After I shut down my bot from heroku, it was still online. Any idea how can I fix this?
Check if you are running the bot locally, and make sure all servers linked to the bot are turned off, sometimes the bot takes a while to completely shut down and go offline in discord, so try waiting for a few minutes.
in Heroku => navigate to resources tab and turn off npm worker: start
I have deployed an Elixir/Phoenix web app on Heroku 2x instance, the backend is in Postgres. The app works fine most of the time but every now and then it returns no such app I am not able to figure out, why is it happening. I have checked the logs and metrics but nothing is helping. In fact, no logging happens when such errors are happening. It feels as if temporarily the DNS resolver on their side has crashed. I haven't added any custom domain and using the default domain name provided by Heroku.
I'm having an issue with my botkit slack bot hosted on Heroku. The bot itself is just the "starter kit."
https://github.com/howdyai/botkit-starter-slack
After a little while, the bot stops working. The logs complain of not being able to find the team. I hit the /login path of my heroku-deployed app and allow it and it works again for a bit.
Is there a heroku configuration that I need to change to keep it from going idle or something? Or is this an issue with the starter kit? Could there be something I need to do in the slack configuration?
I am pretty sure that you run your bot on a hobby dyno. Heroku sends hobby dynos to sleep if they dont receive any requests.
What had happened:
You deployed the bot -> the bot is running and working
Everybody can write with the bot -> so great!
After a few minutes, while the bot is not used, the dyno falls asleep
At this moment the bot is not working
You hit the /login request and yeah -> the dyno starts again and the bot is running and working
Read more about free dynos here: https://devcenter.heroku.com/articles/free-dyno-hours.
Solution: Switch to Standard Dynos
I'm new to Heroku. I've mistakenly created second app on my account and now I can't execute heroku open command to see my app running on the server. I'm posting the screen of the error message. I need only the one named guarded-wildwood-67162. How can I delete other app - shielded-sea-53572?
To permanently destroy a Heroku app you can use heroku apps:destroy --app <app-name> or use the Heroku web interface. Note that this doesn't just disconnect the app; it completely destroys it.
I deployed a web app to Heroku yesterday and it seemed to work if I access the URL from my machine. However I was not able to access from any other devices on the same AND different network.
I thought that maybe it's just my browser cached the website and in reality it's down.
Some of the web services that tell you if a specific URL is down or not report various results - some say it's down, some say it's up.
(Not sure if I can post links here!)
http://downforeveryoneorjustme.com/rock-paper-scissors-.herokuapp.com
https://currentlydown.com/rock-paper-scissors-.herokuapp.com
But then again - I am able to see it via https://browserling.com/
I thought that this might be due to cached DNS but 1 day is way too long and Android flushes DNS after every 10 minutes (as far as I know)
To see if your app on Heroku is running and responding to requests, use the Heroku Toolbelt command
heroku logs --tail
This command shows messages about the app status, i.e when it is up or if it crashes.
Having the logs running with the tail option show the requests as they happen.
If you are on the Heroku free plan, then your application will sleep after 30 minutes of activity.
Once sleeping, the next request to your Heroku app will automatically wake the app up. The time taken to wake your app is largely dependant on how quickly your app starts, but should be a matter of seconds hopefully.
If an application is a little slow in starting, this could lead to a timeout and making it seem like you app is down.
If you do not see real-time log entries when trying to access your Heroku app from a particular device or network, my only thought is that there is some network policy or device blocking access to certain IP ranges (ie. Amazon Web Services).