Expected behavior Users can login. Actual behavior Users can’t login. Failure Logs [Capture d’écran 2021-09-30 à 16.18.47] [Capture d’écran 2021-09-30 à 16.18.29] [Capture d’écran 2021-09-30 à 16.18.41] Context Please provide any relevant information about your setup. Package Version: …

Hi everyone, The origin of the issue you guys experimented with the Forest Admin gem is due to the failure of a pretty commun Ruby gem named httpclient the forest_liana uses. This dependency contains an hardcoded list of CA certificates (including Let’s Encrypt ones), and unfortunately, today was …

Thank you @GuillaumeGautreau Yes, yes. We’re using a load balancer, that’s the reason because we did what your documentation sais at the previously provided link. :wink: Now I understand from your answer that in these condition we have no way on our side to improve our resilience more than this. S…

Thanks for your feedback @Matteo , We are thinking about a way to reduce the pain introduced with these FOREST_CLIENT_ID and APPLICATION_URL configuration variables that are sources of errors when deploying Forest Admin. I guess that your answer is showing that this need is also present when maintai…

@GuillaumeGautreau I guess that your answer is showing that this need is also present when maintaining a working installation. In my perspective, the more resilient (even to external problem sources) the better :+1: Matteo

I have already upgraded the gem to 6.6.3 and also moved to usage of FOREST_CLIENT_ID. Still we are facing the issue where API is returning 403 with message “IP whitelist not retrieved”. Please someone help. Also getting this issue when trying to run console on our ENV. “Forest :deciduous_tree:…

Still having the same issue as @Prateek_mittal . We upgraded to 6.6.3. We regenerated the client id. Added the new client id to our env vars Checked that the new client id has been well added We still get the error : {“errors”:[{“status”:500,“detail”:“SSL_connect returned=1 errno=0 state=error: …

Hello @Imad_Wakidi and @Prateek_mittal . Could you please run a curl https://api.forestadmin.com on the server on which you are experiencing the issue? Lower versions than 6.6.3 rely on a library that does not support the new root certificate of Let’s encrypt. In order to bypass this, we included a…

[image] GuillaumeGautreau: curl https://api.forestadmin.com Thanks Guillaume. Here’s the result of the command : [Screenshot 2021-10-08 at 10.33.27]

Ok, then it means that the problem does not come from your OS, but likely from the rails lib again. Just to be sure, can you run gem query --local on your server, in the directory where you deployed your rails app ?

Sure here’s the result [Screenshot 2021-10-08 at 10.41.49]

🚨 Forest down (SSL issue) - Trouble logging in - error 400: Invalid client id 🚨

Help me!

GuillaumeGautreau October 8, 2021, 9:26am 63

Ok, the version of forest_liana is not displayed here :-/
Can you share the name of your project and your environment? I’ll check in our database.

Forest suddenly won't load on application startup

Topic		Replies	Views
Unable to authenticate you - 500 or 400 error Help me!	15	750	October 5, 2021
Unable to authenticate you Help me!	2	483	October 4, 2021
Forest auth issue with Rails version v6.6.3 Help me!	6	331	October 1, 2021
Cannot Access to ForestAdmin - /forest/authentication/callback is returning a 500 Help me!	4	665	October 4, 2021
Forest UI Authentication - V7 Help me!	10	555	June 22, 2021

🚨 Forest down (SSL issue) - Trouble logging in - error 400: Invalid client id 🚨

Related topics