-2

While putting credentials information in Age-Cloud-Express.

It returns an error:

Proxy error: Could not proxy request /api/v1/db/connect from localhost:3000 to http://localhost:3001.
See https://nodejs.org/api/errors.html#errors_common_system_errors for more information (ECONNREFUSED).

In console:

enter image description here

What can be the error? and how to resolve it.

Kamlesh Kumar
  • 351
  • 1
  • 7
  • Just adding / after the port number in package.json file may work. Something like: "proxy": http://localhost:portNumber/) – Huzaifa Aug 14 '23 at 16:26

4 Answers4

0

It seems there are something wrong with the running backend of the age-viewer the issue comes at the connection of the database at the side of the backend so you can make simple check by connecting through psql session to PostgreSQL

psql demodb

to make sure it should work without age viewer to find out if there is an issue with your installation of the database server itself or you may think it is an issue in the age-viewer

Also make sure of the database credentials

Mohamed Mokhtar - rrrokhtar
  • 678
  • 5
  • 12
0

I found the answer.

So I was running the application by running the command 'npm run install' inside the Frontend folder. But when I run the same command outside the folder it worked for me.

Kamlesh Kumar
  • 351
  • 1
  • 7
0

It looks that there might be a problem with the AGE viewer's backend, namely with the database connection. By establishing a connection to the PostgreSQL database using a psql session, you may quickly analyze this. This will assist identify whether the AGE viewer is more likely to be the source of the problem than the database server installation itself. Please double-check that the database credentials you are using are accurate as well.

Raja Rakshak
  • 168
  • 2
0

It appears that there may be an issue with the database connection in the AGE viewer's backend. You can immediately investigate this by setting up a p-sql session to connect to the PostgreSQL database. This will help determine if the AGE viewer or the database server installation is more likely to be the problem's root cause. Please confirm the accuracy of the database credentials you are using as well.

Ammar Baig
  • 1
  • 1