Migrating to forest-express-sequelize v7, "Please verify that your admin backend is correctly configured and running."

Help me!
1

I’m migrating to forest-express-sequelize v7 from v6. I followed this guide: https://docs.forestadmin.com/documentation/how-tos/maintain/upgrade-notes-sql-mongodb/upgrade-to-v7#upgrading-to-v7

I launched my server, there’s no errors from forest.
But I went to the dashboard and clicked on my development environment and it’s trying to reach the wrong url.

It’s maklng a call on the following url: http://localhost:8000/forest/authentication/callback?code=... when it should make a call to http://localhost:8000/admin/forest/authentication/callback?code=.... (I have a custom thing and all the forest url are under the admin path.

My base url in my environment configuration is correct (the /admin is there).

It is caused by this line in forest-express: forest-express/authentication.js at 305c33c75d0d183da071c2427d4950e9e162be63 · ForestAdmin/forest-express · GitHub

As you can see here, it removes the path if there’s already one:
Screen Shot 2021-03-09 at 17.21.25

2

Hello @julien,

Thank you for your feedback. Can you please share with us which technology and package version you use? Do you use forest-rails, forest-express-sequelize or forest-express-mongoose?

Also, can you share the value you entered for the APPLICATION_URL env variable?

Thanks

3

I use forest-express-sequelize, APPLICATION_URL is http://localhost:8000/admin

The forest admin dashboard makes a first request to http://localhost:8000/admin/forest/authentication, and that request returns the incorrect redirect URL because of the line of code in forest-express I linked to.

4

Thank you for your feedback. I’m creating an issue on our side, indeed, there is a problem with this implementation.

We will work on a fix and release it as soon as possible. I’ll let you know when it’ll be available.

3 Likes
5

Hello @julien,

We just released forest-express-sequelize@7.1.1 and forest-express-mongoose@7.0.5 that should fix the bug that you encountered.

Can you test on your side and confirm that it’s fixing yout issue?

Thanks