Feature(s) impacted
I’m having a issue upgrading from version 6 to 7 (choice of a senior dev)
After following the documentation you provide, I’m having a problem connecting to my staging environment.
It tells me that my password is incorrect, whereas on the production environment it works correctly and it’s the same account that works in staging in version 6.
The project is tax-BO from the company 24s
The meta object in the .forestadmin-schema.json file looks like this:
"meta": {
"liana": "forest-express-mongoose",
"liana_version": "7.9.2",
"stack": {
"database_type": "MongoDB",
"engine": "nodejs",
"engine_version": "14.16.0",
"orm_version": "5.8.13"
}
}
We have two environments, staging and prod. I’m trying to upgrade on staging before going to prod. The two don’t share the same FOREST_ENV_SECRET.
Maybe you can come up with an idea, I can provide you more information you need.
Observed behavior
Expected behavior
Etre connecter et avoir acces aux données
Failure Logs
Context
- Project name: tax-BO
- Team name: 24s
- Environment name: zolastaging
- Agent technology: nodejs
- Agent (forest package) name & version:
“forest-express”: “^7.4.0”,
“forest-express-mongoose”: “^7.9.2”,
- Database type: MongoDB
Hello @n.liyanage, welcome to the community
It tells me that my password is incorrect
I dont see that from the logs provided. where does it appear ? In the frontend ?
I assume that you are able to connect to the forest admin frontend, but not your agent, is that correct ?
Your backend logs only show http code 200, which dont indicate any error.
Are you sure that your updated backend is running at the expect endpoint ?
Sorry, I had a password error but now it’s the error you see on the screen (Unable to authenticate you). I’m actually in 200 in my logs, that’s why I don’t understand.
I have a callback that broke after authentication. But I managed to get it to work, I followed the migration but I still get this ‘Unable to authenticate you’ error. Do you have any ideas?
I don’t see an explicit log.
Do you have an idea ?
The Unable to authenticate you is certainly coming from from a failed network request that you should be able to see in your browser logs. would you be able to retry to login to your agent and find the failed request in your dev tools ?
This failed request can either be from the agent (but since you only see 200 thats unlikely). Otherwise it could come from the Forest Admin backend.
How do you authenticate ? email+password ? sso ? Google sign in ?
I don’t see any errors in the dev tool, I use email and password identification.
However, I have made the breaking changes
What is your agent local port ? Did you set the proper APPLICATION_URL to target it ? I noticed 8080 somewhere in your logs, which is not standard for the agent.
If this is still not this issue, would you be willing to share (in a private message) an HAR extract of your network calls when the failure occurs ?
Thanks !
2 Likes
Hi, we have changed port 8080 to 3310 but we are still experiencing this problem. But we don’t see any log that could help us.
I would like to open a private conversation with you, in order to provide you with the .har file.
Thank you
The problem was with the value of the APPLICATION_URL variable. I added the value of my application and this enabled the callback to return the correct data.
2 Likes
