"Your project is being configured" forever

Help me!
1

Feature(s) impacted

Viewing data

Observed behavior

I have set up one development environment, one production environment, and two other remote environments. In all cases, I see " Your project is being configured" when I go to look at my data, and have been seeing those for perhaps an hour.

Expected behavior

I expect to see my data.

Context

  • Project name: TruthOrLie
  • Team name: Operations and Engineering
  • Environment name: All (Prod, Staging, AMI Preview, and a local Development env)
  • Database type: Postgres
  • Recent changes made on your end if any: Implementing now; it’s never worked

And, if you are self-hosting your agent:
Yes, self-hosting

  • Agent technology: (nodejs, php, ruby, python) NodeJS / Express
  • Agent (forest package) name & version (from your .lock file): @forestadmin/agent 1.61.1, @forestadmin/datasource-sequelize 1.12.1

Other notes: I can hit the /forest route in my browser (for all environments); I get “{“error”:null,“message”:“Agent is running”}” as the response. This happens both in my local env (which is fronted by ngrok.io) and my remote environments (which are fronted by CloudFront and NginX).

I believe I initially created this project as a “cloud” project, not realizing that what I wanted was a “self-hosted” project. But I deleted the environment (Production) that was configured for that, then created three environments, each in “self-hosted” mode (with their own URLs for forest to hit, on the /forest route), with my “Prod” environment being my “production”.

I LOVE Forest!!! I’ve used it on two other projects. It’s invaluable. But this has been a really frustrating setup process - more so than previously. Maybe I’ve just had bad luck. Please help? Thanks!

2

Hello @avocado876

Thanks for reaching out to the support, I’ll try to sort you out.

I think you’ve already diagnosed the cause of your issue, I would bet that this is caused by the initial Cloud setup of your project as they would wait for different event for Cloud and Self-hosted.

The best way to resolve this is for you to create a new project to ensure that we’re not missing any technical step and configuration.

To create a self-hosted project, you would have to add ?customHosting=true to the url once you’ve named your newly created project. This will enable you to see the previously existing onboarding choices.

I’ll forward your feedback to the team. The new onboarding provides only the Cloud setup to ease installation, maybe we could provide by default this “older” screen to already existing Forest users that face no issue setting up self-hosted agents.

Best regards,

1 Like
3

Thanks very much, @dogan.ay. Creating a new project was indeed the solution. Perhaps you could just pass on my feedback, which is: Forest is a lifesaver; I’m a huge fan, have been for several years, and have deployed it for several clients. But this onboarding experience was just absolutely horrible. If I wasn’t already familiar with Forest already, I would have ditched during the onboarding and found another solution.

I’m happy to share more thoughts; there were four or five other major pain points during my onboarding, so if your product or dev teams are looking for friendly but honest feedback, feel free to give them my contact info.

Thanks again for yur help.

3 Likes
4

Thanks for your feedback, I’ve reached out to you privately to hear more about the pain points you encountered.

I have marked this as resolved. Please do not hesitate to reach out if you encounter any other issue.