I am referencing an application hosted on my free Heroku account. I think I have hit a usage limit but I don't see any errors in the web console. Does Heroku return an error when you've hit the 256 simultaneous processes/threads limit? If so, is it in my account? Where can I find it?
https://devcenter.heroku.com/articles/dynos#process-thread-limits
Related
I have deployed heroku application - Ktor server that was working for 2 years and everything was working perfect. Since few days my application cannot access host (https://api.um.warszawa.pl/). It's getting timeout error all the time. API is accessible from my local machine. How can I check who blocked the access and why? Where can I ask for enabling the access again? Any ideas?
I have the same issue. I have had contacted the API team at Warsaw Town Hall - they have told me that City's Centre of Network and Data could set location restrictions on the API due to CHARLIE-CRP alarm.
I am trying to move my backend API app (node.js express server) from Heroku to AWS Elastic Beanstalk. But I did not realize the amount of features that Heroku was providing automatically and which I now have to set up manually in AWS.
So here is the list of features which I discovered were missing in AWS and the solutions I have implemented.
Could you please let me know if I am missing something in order to run smoothly my APIs in AWS and get the equivalent of what I had in Heroku?
auto-restart server when crashed : I am using PM2 to automatically restart my server in case of critical error
SSL certificate : I am using AWS ACM certificate,
logging : have inserted the datadog agent in order to receive logs in datadog
logging response time : I have added the "morgan-body" package to get each requests' duration and response code (had to manually filter the AWS healthchecks and search engine bots, because AWS gave me an IP adress which was visited constatntly by Baidu bots)
server timeout : I have implemented a 1200000ms timeout on the whole app (any better option ?)
auto deploy from Github : I have implemented a github automation to deploy code automatically (better options?)
Am I missing something? This app is already live so I do not want to put my customers at risk when I will move from Heroku to AWS...
Thanks for your help!
I believe you are covered:
Heroku Dynos restart after crashing or raising an error (Heroku Restarting Policy)
SSL certificates are provided for free
logging: Heroku supports various plugins, including Datadog
response time (in millisec) is logged automatically
HTTP timeout is 30 sec (it cannot be changed)
deploy from Github is possible (connecting the accounts), Docker deployment is also supported. Better options? Using Github Actions to deploy a new version after code push or tagging.
If you are migrating a production environment I strongly suggest first to setup a Heroku (Free) Dyno to test and verify all your needs are satisfied.
I am trying to access the Heroku website now and it's not responding.
API Unavailable
I can't even update my application through CLI.
How soon this will be fix?
Heroku was affected by the DDOS attacks made to DynDNS. Check Heroku Status for more info
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).
Please, try to acess:
http://unidemico.herokuapp.com/
It is working the index page, but when I'm trying to acess any Available controller:
Available Controllers:
unidemico.AreaAcademicaController
unidemico.ArtigoController
I get the following error:
Bandwidth Limit Exceeded
The server is temporarily unable to service your request due to the site owner reaching his/her bandwidth limit. Please try again later.
Apache Server at www.changeme.com Port 80
Any Idea why?
https://devcenter.heroku.com/articles/limits
I have no idea if I exceed any limit its the first time I deploy an application and its a Grails application very simple, only two controllers, project has only 2Mb...
changeme.com is a placeholder domain. You need to update your Config.groovy to point to your heroku app domain or your custom domain.