setting up a new project or a new environment in the current project
Observed behavior
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
Expected behavior
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
I’m new to forest admin and facing same issue. Why the authentication call back calls to localhost:3310? I’m tried to change my application url. But it’s still call the localhost:3310.
We are experiencing cache refresh issue on certain actions, I have manually refreshed your cache. Could you please tell me if you still encounter any issue on your environments ?
I’m sorry to hear that you have issues with your configuration.
For us to be able to help we will need more details as it appears to me you are not facing an issue with cache refreshing.
Could you please open a new topic with the template filled out ? Thanks
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 ?
The behaviour of “reverting” to the older url was due to bad cache refreshing, you should no longer experience a similar issue. We’re sorry for the inconvenience.
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
the test_23 from GSL_Admin, tries to authenticate through the server url on the Production environment and not through the new one I am trying to migrate to and defined in the Admin backend URL field
It appears to me that both your test_23 and Production environments point to the same backend URL, can you try to update the apiEndpoint of your test_23 environment once more ?
I changed the url to other locations and it works, it sends the request to those locations but when I change it back to my server url, it reverts back to localhost
When you refresh your page with your web console open, can you give me the result of this call https://api.development.forestadmin.com/api/projects/:projectId/environments in the network tab ?
. DO you still experiment this issue ?
)