I have updated the password of my database and updated it in my Forest Admin sequelize node js project.
But getting error
[
{
“status”: 500,
“detail”: “getaddrinfo ENOTFOUND supportpay_admin”,
“name”: “SequelizeHostNotFoundError”
}
]
I have updated the password of my database and updated it in my Forest Admin sequelize node js project.
But getting error
[
{
“status”: 500,
“detail”: “getaddrinfo ENOTFOUND supportpay_admin”,
“name”: “SequelizeHostNotFoundError”
}
]
Hello @Alishba_Khan1 ,
Can you share the code of your Forest Admin agent (without the database credentials of course) ?
Are you able to connect to your database from another app using the same credentials ?
Its difficult to help without much info, but the error is pretty clear: your database is unreachable. It can be due to wrong credentials, connectivity issue…
Kind regards,
Enki
Hi @Enki ,
I have created another project (SupportPay) using the same password, and it worked fine. However, while creating the SupportPay project, the connection URL modified the password due to the presence of special characters.
I do not want to create a new project since my current project (New SupportPay 3.0 Database) has several layout changes.
Is there a way to update the database credentials from the Forest Admin UI? Currently, I am updating them directly in the code.
“dependencies”: {
“@sequelize/core”: “^7.0.0-alpha.10”,
“body-parser”: “1.19.0”,
“chalk”: “~1.1.3”,
“cookie-parser”: “1.4.4”,
“cors”: “2.8.5”,
“debug”: “~4.0.1”,
“dotenv”: “~6.1.0”,
“express”: “~4.17.1”,
“express-jwt”: “6.0.0”,
“forest-cli”: “^3.0.10”,
“forest-express-sequelize”: “^9.3.14”,
“morgan”: “1.9.1”,
“pg”: “~8.2.2”,
“require-all”: “^3.0.0”,
“sequelize”: “~5.15.1”
},
Hi @Enki ,
I would appreciate it if you could look into this issue, as it requires urgent attention. Thank you for your prompt response.
From what I understand, your Forest Admin agent is hosted by yourself (not the cloud agent). In this case, the only way to update database credentials is via the code of your agent.
The special characters in the database password is certainly the cause of your issue.
Have you tried to URI encode the password ( “pass@word” ==> “pass%40word”), so that the connection URI can be parsed normally using “:” and “@” as separators for values ?