setting up a new project or a new environment in the current project
When setting up a new project, deploying to production after setting up locally causes an “Unable to authenticate you” popup. The get request goes to the localhost:3310 and not to the remote server I defined in the Admin backend URL field.
Trying instead to create a new environment on my current project, results in getting redirected to the project selection page with a “Project not found” error
Creating a new project and deploying to production should direct the get requests for authentication to the server url I defined in the Admin backend URL field for the production environment.
Deploying a new environment in my current project should deploy the project and not kick me out of the project with a project not found error
From what I can see, the configuration of your environment points to an url different from localhost:3310, and you should have no issue with cache refreshing.
Can you please simply refresh your frontend ?
I was looking at your Production environment from GSL_Admin_2023, if you’re experiencing this issue on environment test_23 from GSL_Admin, it appears that your agent hasn’t reached our backend yet. Is the agent running ? Can it reach https://api.forestadmin.com ? Do you have any error log from your agent when running it ?
when trying to connect with the test_23 from GSL_Admin env_secret, it hangs on waiting for your backend to run. when trying with the GSL_Admin_2023 Production env_secret, it tries to authenticate through the localhost and through the server