My Sinatra App displaying 'Internal Server Error' after deployed to Heroku - ruby

My app is working locally, But after deploying to Heroku I'm getting an 'Internal Server Error' on my page
The Error log is as follows.
http://pastie.org/private/b5lgfmij1by3krieyp9sq
I cannot see what the problem is
Thanks for your help!

The problem is related to your database (or lack of):
2013-05-13T06:58:57.488018+00:00 app[web.1]: PG::Error - could not connect to server: Connection refused
Did you add one with $ heroku addons:add heroku-postgresql:[dev|basic|crane|etc] -a app_name? Checkout this Dev Center article with info on setting up Rack based web apps (including Sinatra) and setting up database access:
Deploying Rack-based Apps

Related

The herokuapp jsonpath site is down

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.

Could the server and app run in the same domain?

The situation I met is that.
I design a frontend app by React, but I want to connect to MongoDB.
From what I knew so far, I could only connect to MongoDB in the backend. So, I use the express to set up a server but when I try to connect the frontend to the backend, the answer I found seems to tell me that I should run the server and the app on different domains, so I should run the server and app on different Heroku apps.
Could I put the server and app in just one Heroku app and connect between them?

Bad Auth with mongoose when deploying NestJS app on Heroku

I'm trying to deploy my NestJS app on Heroku but now all of the sudden app is throwing Bad Auth error.
On the development it's all working fine.
This is the error I'm getting:
I'm storing the credentials in .env
Are these constants populated by Heroku with some unexpected values?
And I'm allowing the connection from every IP address:
What is going on and how to fix this?
I was having the same trouble, the solution for me was to put the whole link to connect in an environment variable instead of just the secret. I was using node, express, mongoose and MongoDB Atlas, so for me it was:
//on .env file
ATLAS_CONNECT=mongodb+srv://yourusername:yoursecret#cluster0.mre5gvd.mongodb.net/yourDBname
//to connect
mongoose.connect(process.env.ATLAS_CONNECT);

Heroku Connect - No connections found

I am trying to use heroku connect with my salesforce instance.
I have added Heroku connect as addon together with my postgresql.
This is what I am getting when I am clicking on it:
Am I missing some misconfiguration? What can I check?
This was due to a conflicting behaviour between two heroku users connecting.
on the cli I have one user meanwhile in the browser there was another user connected

Cannot Access Heroku Dashboard

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

Resources