This is due to an (accidental) breaking change in node-postgres
version 8 (see this GitHub issue).
The solution is to pass rejectUnauthorized: false
to the sequelize
connection parameters inside of dialectOptions
>ssl
, as described here by GitHub user jsanta, bypassing the SSL certificate check (which is okay when connecting to a trusted server over a secure connection such as on your local host or between your own servers in the same network):
const sequelize = new Sequelize({
database: "xxxxx",
username: "xxxxx",
password: "xxxxx",
host: "xxxxx",
port: 5432,
dialect: "postgres",
dialectOptions: {
ssl: {
require: true,
rejectUnauthorized: false // <<<<<<< YOU NEED THIS
}
},
});