Hi,
I have gone through the setup steps as prescribed and set up a backend server that is connected to my DB server. Now I want to test it but I am prevented from logging in because apparently the frontend expects me to configure a local test setup first and won’t even let me switch to a production environment or do any further configuration. Basically, I am now completely locked out of that project now. How do I resolve this? Thanks!
I have also tried to set up another local app now using the demo database provided in the documentation but it does not seem to work as intended:
apricot_prod | Your application is listening on port 3310.
apricot_prod | Your admin panel is available here: https://app.forestadmin.com/projects
apricot_prod | [forest] 
Unexpected error: connect ECONNREFUSED 192.168.65.2:5432
apricot_prod | SequelizeConnectionRefusedError: connect ECONNREFUSED 192.168.65.2:5432
apricot_prod | at connection.connect.err (/usr/src/app/node_modules/sequelize/lib/dialects/postgres/connection-manager.js:170:24)
apricot_prod | at Connection.connectingErrorHandler (/usr/src/app/node_modules/pg/lib/client.js:213:14)
apricot_prod | at Connection.emit (events.js:198:13)
apricot_prod | at Socket.reportStreamError (/usr/src/app/node_modules/pg/lib/connection.js:57:10)
apricot_prod | at Socket.emit (events.js:198:13)
apricot_prod | at emitErrorNT (internal/streams/destroy.js:91:8)
apricot_prod | at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
apricot_prod | at process._tickCallback (internal/process/next_tick.js:63:19)
Hello @fabian,
Sorry to hear you are having difficulties setting your project up.
Reading the error message you pasted, it seems your database access is either not properly configured or your database does not answer.
Can you assert that you can access the database via a GUI or command line tool?
If yes, please ensure your .env file contains the proper values in DATABASE_URL.
You can also check that http://localhost:3310/ is accessible via your internet browser.
Once the ECONNREFUSED error is gone and the LumberJS page is visible at http://localhost:3310/ if the problem is still there, it can come from an invalid value in FOREST_ENV_SECRET (shown in the setup process).
Let me know if this helps.
