Unable to Setup New Project with Local Application URL

Feature(s) impacted

New Project Setup

Observed behavior

On the project setup step titled “What is your local application URL?” I enter our local URL http://local.transport4.com:3000 and the step never completes. The browser error console shows the following errors:

Failed to load resource: the server responded with a status of 422 (Unprocessable Entity)
api.forestadmin.com/api/environments/123572:1

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading ‘captureException’)
at p.tryBeforeNext (client-689f4f17016a2544cb40f7af341d7c47.js:1:39429)
at async p.onGoNext (client-689f4f17016a2544cb40f7af341d7c47.js:1:3170438)
at async v.onClick (client-689f4f17016a2544cb40f7af341d7c47.js:1:986421)

Expected behavior

When I enter my application local URL, it should complete the step and proceed to the next step.

Failure Logs

Failed to load resource: the server responded with a status of 422 (Unprocessable Entity)
api.forestadmin.com/api/environments/123572:1

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading ‘captureException’)
at p.tryBeforeNext (client-689f4f17016a2544cb40f7af341d7c47.js:1:39429)
at async p.onGoNext (client-689f4f17016a2544cb40f7af341d7c47.js:1:3170438)
at async v.onClick (client-689f4f17016a2544cb40f7af341d7c47.js:1:986421)

Context

  • Project name: T4 Admin Tools
  • Team name: …?
  • Environment name: …?
  • Agent type & version: Google Chrome version 108.0.5359.125
  • Recent changes made on your end if any: No changes, haven’t been able to setup/install ForestAdmin.

Hello @nprinsloo and welcome to our community !

I am sad to hear that you have issues with your onboarding experience. You are unable to create your project because the url you have given is not a localhost nor secured using https. I have reproduced the steps and confirm that there is an issue with our frontend, it should display a popup error with the following message “HTTPS must be used for the apiEndpoint.”. I will immediately create a ticket for this.

In your case, you could finish the onboarding with a localhost apiEndpoint or use HTTPS.

I hope this helps.

Best regards,

Dogan