sql_error_code = 28000 FATAL logs in working API

Question

Heroku is hosting my node.js API and the PostgreSQL addon is responsible for my DB.

I recently upgraded my heroku db plan from hobby-dev to standard-0 and got some issues with SSL connection. After setting sslmode=require, my new DB was performing with no problems and I was really happy with it.

Suddenly, without any changes in code, nor in environment config vars and in a day with a reduced request flow, it started to print on PaperTrail the following error:

[COBALT] [10-1] sql_error_code = 28000 FATAL: no pg_hba.conf entry for host "xx.xxx.xx.xxx", user "postgres", database "postgres", SSL off

Even when my node.js API is not requested, this error gets printed. I'm intrigued with the credentials user "postgres", database "postgres", my DB in which the API stores requests, responses and some useful data has other credentials.

The API is working fine, but these logs are really pissing me off and I have no idea what is going on.

Any ideas?

Something probably was changed after all. This is the general purpose "cannot connect" message. Look into the PostgreSQL log file for details. — Laurenz Albe, Mar 07 '19 at 15:46

Mgan · Answer 1 · 2019-03-07T17:07:04.483

1

For those that land here from seeing this log message -- FATAL: no pg_hba.conf entry.

edited Mar 07 '19 at 17:07

answered Mar 07 '19 at 16:35

Mgan

21
1
3

Also see https://help.heroku.com/MDM23G46/why-am-i-getting-an-error-when-i-upgrade-to-pg-8 – Jacob Horbulyk Oct 23 '20 at 12:07

score 0 · Answer 2 · edited Jun 10 '22 at 00:26

I am extremely green. I just started coding 5 months ago. While working on a school assignment, I encountered the same issue. Near identical situation to that outlined in the OP. I ended up finding my solution. I found a spelling error in my code here. But It seems that error is related to ssl.

const sequelize = new Sequelize(CONNECTION_STRING, {
    dialect:"postgres", 
    dialectOptions: {
        ssl: {
            rejectUnauthorized: false
        }
    }
})

sql_error_code = 28000 FATAL logs in working API

2 Answers2