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
Related
Loading https://jsonpath.herokuapp.com/ is returning this:
Application error
An error occurred in the application and your page could not be
served. If you are the application owner, check your logs for details.
You can do this from the Heroku CLI with the command heroku logs --tail
You application might be using free Heroku plan. However, heroku has shut down their free services from November 28, 2022. You should host the website to some other hosting services.
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 want to deploy my blockchain based decentralized application on heroku.
It has been deployed but when I try to login using my metamask account the account shows as null. It works on my local machine but not on heroku.
I do not want to clutter my question with code so I am sharing a link to the code
Code that is deployed on heroku
Finally figured it out. I was documenting the code for github and realized that I did not whitelist the app url in the metamask settings.
I'm an admin for our Heroku account and can see Review Apps on the Heroku pipelines page however I don't see open pull requests with the Create Review App option. I'm an admin of the account so I'm not sure what it is. Any ideas? Thanks!
Found it. I had to give Heroku access to my github account, even though it already had access to the corporate account I was a part of.
I started developing my personal blog (and a basic CMS) using Phoenix.
I successfully deployed it to Heroku following the Documentation/Guides, it's live.
Now I added my custom domain "jonathansoifer.com" to the Heroku App but everytime I access it, the URL on the browser switches from that custom domain to the "Heroku app URL" (jonathansoifer.herokuapp.com).
Am I missing something?
It might be useful to know that the DNS is being managed by CloudFlare, using CNAME flattening as recommended by CloudFlare itself.
CNAME • jonathansoifer.com • jonathansoifer.com.herokudns.com
Sure enough, the issue was within config/prod.exs.
I had hard coded the Heroku URL there in order to take advantage of Heroku's free SSL when using their subdomains.