Express.js, GCP express-session deprecated req.secret; provide secret option at - node.js

Question

Current development environment is as follows
Windows 11 Home-64bit
GCP Computer Instance: Ubuntu 20.04.5 LTS
Situation Description
Express.js + Sequelize is being used, and in the case of DB, GCP's Cloud SQL is being used.
In the local environment, it is determined that there is no problem because it is linked to Cloud SQL and reflected immediately when operated in MySQL Workbench.
Attempt to run a backend project through a GCP computer instance and verify that it works like local even in deployment.
Errors that have never been seen in a local environment are output.
DB access error and express.session error occur, but I don't understand why this error occurs only in the distribution version, and this error did not occur at all in the development version.
Error message output from GCP
code: 'ER_ACCESS_DENIED_ERROR',
errno: 1045,
sqlState: '28000',
sqlMessage: "Access denied for user 'root'#'localhost' (using password: NO)",
sql: undefined
}
express-session deprecated req.secret; provide secret option at app.js:34:9
Warning: connect.session() MemoryStore is not
designed for a production environment, as it will leak
memory, and will not scale past a single process.
Warning: connect.session() MemoryStore is not
designed for a production environment, as it will leak
memory, and will not scale past a single process.
const express = require('express');
const path = require('path');
const cookieParser = require('cookie-parser');
const session = require('express-session');
const dotenv = require('dotenv');
const cors = require('cors')
dotenv.config();
const AlphaRoute = require('./Routes/Alpha')
const AuthRouter = require('./Routes/Auth')
const {sequelize} = require('./models')
const app = express();
app.set('PORT', process.env.PORT || 8095);
sequelize.sync({force: false})
.then(() => {console.log('db ok')})
.catch((err) => {console.error(err)})
app.use(cors({
origin: '*'
}));
app.use(express.json());
app.use(express.urlencoded({ extended: false }));
app.use(cookieParser(process.env.COOKIE_SECRET));
app.use(session({
resave: false,
saveUninitialized: false,
secret: process.env.COOKIE_SECRET,
cookie: {
httpOnly: true,
secure: false,
},
}));
app.use('/auth', AuthRouter)
app.use('/alpha', AlphaRoute)
app.listen(app.get("PORT"), () => {
console.log(app.get("PORT"), 'Online')
})
The way I tried it.
In the case of DB access error, the password input part of config.js was set to process.env.DB_PASSWORD, but as the problem continued, we changed it to input the password string.
Is it a problem that occurs because the password of the DB is not unified? I unified it with the Root password when CloudSQL was created.
What code should I modify to solve this problem?