Is it possible to create a branch in the development environment?

Help me!
,
26

yes we updated all the secrets and deployed

27

And the previous one is no longer running? Since itā€™s the same endpoint that could be an issue.

  • Did you try to disconnect? And maybe clear your browser Local Storage?
  • Are you sure to be connected to your new project? (Maybe share your current URL just to be sure)

The issue 401 is an authorization error. Like you donā€™t have the right token to talk to your new agent.

Let me know if it helps.

Kind regards,
Morgan

28

Even I think itā€™s weird because we checked and FOREST_ENV_SECRET and FOREST_AUTH_SECRET are correct.

Can it be linked to the FOREST_AGENT_URL variable?

29

What value do you use?

30

we donā€™t use it because we use APPLICATION_URL instead of FOREST_AGENT_URL

Iā€™m going to see to the one who made the server if the value of APPLICATION_URL corresponds well to that of FOREST_AGENT_URL

Iā€™ll keep you informed !

31

Youā€™re using forest-express-sequelize so you donā€™t need to set FOREST_AGENT_URL (only used in our brand new agent-nodejs). In your case, only APPLICATION_URL should matter.

Can you send me in a private message all your environment variables for your new production environment so I can check everything is well configured?

Kind regards,
Morgan

32

Ok, I send you this !

33

itā€™s strange that even if we put the right value in the variable APPLICATION_URL we still get the error 401

Are there any other useful variables that we might have misused?

34

Hello @jacques_liao,

I donā€™t think youā€™re missing something here.

A little recap, you hit an error 401 (Invalid signature) since you deployed your new project production environment.

To have a clear mind on what is happening:

  • Can you share your token (Authorization header of a failing call)? So I can check it is well formed.
  • Did it works for your development environment?

Kind regards,
Morgan

35

Hello @morganperre

I send you in private

36

Iā€™m closing this topic.

The issue came from a misconfigured FOREST_AUTH_SECRET due to custom environment variables management.

Kind regards,
Morgan

1 Like