Feature(s) impacted I have followed the instructions to start the development server and it starts locally. Observed behavior When I switch to the development environment I get the error “Forest Admin can’t reach your agent; please ensure that it’s running.” Expected behavior I was expecting to be…

Hello @Janet_Gilbert Thanks for reaching out to the community support. As you are in a Cloud project, the setup was minimised to reduce friction as much as possible, the environment is configured to reach localhost:3310 which is the default port the local development agent should listen on. Are y…

There is no access via button in the UI to reach the configuration screen of your development environment as it was designed to show/provide an experience as minimalistic as possible. However you can still access the configuration screen of your development environment by following this link . I wi…

Thanks! A quick access button is a great idea. Now I get a different error “An error occurred during authentication. Please check that your database credentials are correct and resync your agent.” [image]

I don’t seem to be using anything on port 3310, so is there a way of forcing Forest to launch on 3310?

The configuration relating to your local agent can be found in the .env inside of the directory that was generated after the bootstrap step. As well as datasources.js to configure your development database

I added these lines to my .env file but it’s still not launching on the port 3310. It always mounts on 3351 FOREST_ENV_SECRET=[redacted] TOKEN_PATH=C:\Users\janet LOG_LEVEL=Info APPLICATION_URL= http://localhost:3310 APPLICATION_PORT=3310

OK it finally managed to connect to my server on 3351! Thanks and enjoy your evening.

it’s great that you’ve been able to access your local agent, if you encounter any other issue, I’ll be glad to help as it is not expected for your agent to start on port 3351. I’ll forward to the team the idea of having a way to reach the environment configuration via the error modal. Thanks ! hav…

I didn’t set my agent to start on port 3351 and there’s no reason why it shouldn’t have started on 3310. The .env file seems to be ignored.

"Forest Admin can't reach your agent; please ensure that it's running."

Help me!

Janet_Gilbert March 26, 2025, 2:38pm 3

I think we are using 3310 for something else. How can I get it to look for the 3351 port?

Topic		Replies	Views
FA can't connect to my local node js server: forest tries to connect to port 3310 Help me!	6	274	January 3, 2023
My local (deveoppement environnement) not work and recette /prod work Help me!	14	222	November 6, 2025
Can't connect to Dev server Help me!	4	281	November 7, 2023
Issue creating local environment Help me!	1	538	June 24, 2022
Not able to configure for production environment Help me!	17	1134	August 17, 2022

"Forest Admin can't reach your agent; please ensure that it's running."

Related topics