# Still cannot login to Forest after upgrading to 7.2.2

**URL:** <https://community.forestadmin.com/t/still-cannot-login-to-forest-after-upgrading-to-7-2-2/3407>\
**Category:** Help me!\
**Created:** [October 1, 2021, 6:00pm UTC](https://community.forestadmin.com/t/still-cannot-login-to-forest-after-upgrading-to-7-2-2/3407 "2021-10-01T18:00:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![KidA001](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/kida001/32/2734_2.png) [@KidA001](https://community.forestadmin.com/u/KidA001)\
**Post date:** [October 1, 2021, 6:00pm UTC](https://community.forestadmin.com/t/still-cannot-login-to-forest-after-upgrading-to-7-2-2/3407/1 "2021-10-01T18:00:11Z")

</div>

Trying to get a response as I really need access to Forest right now…Please see my original post: [Cannot Access to ForestAdmin - /forest/authentication/callback is returning a 500](https://community.forestadmin.com/t/cannot-access-to-forestadmin-forest-authentication-callback-is-returning-a-500/3405)

I have upgraded the gem to 7.2.2 and re-deployed my server. I still cannot login. I re-generated my client\_id but realized I’m not using a static client\_id.

The error is a 500 on the authtication callback for forest.

---

<div class="post-metadata">

**Author:** ![KidA001](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/kida001/32/2734_2.png) [@KidA001](https://community.forestadmin.com/u/KidA001)\
**Post date:** [October 1, 2021, 6:14pm UTC](https://community.forestadmin.com/t/still-cannot-login-to-forest-after-upgrading-to-7-2-2/3407/3 "2021-10-01T18:14:10Z")

</div>

It’s an exceptional platform. i’ve been using for years with different clients. this is the first hiccup they’ve accidentally caused. Just trying to get some support. Please don’t post unless you have something constructive to offer.

---

<div class="post-metadata">

**Author:** ![anon39848301](https://avatars.discourse-cdn.com/v4/letter/a/b9e5f3/32.png) [@anon39848301](https://community.forestadmin.com/u/anon39848301)\
**Post date:** [October 4, 2021, 8:35am UTC](https://community.forestadmin.com/t/still-cannot-login-to-forest-after-upgrading-to-7-2-2/3407/6 "2021-10-04T08:35:54Z")

</div>

@KidA001,

Could you eventually try to do a `curl https://api.forestadmin.com` from your OS (or docker container if you are using one)?  
If you are experiencing the SSL issue, you could either

- try to upgrade your docker base image to a newer one, or
- try to manually invalidate and update the certificate causing the issue via

```javascript
rm /usr/share/ca-certificates/mozilla/DST_Root_CA_X3.crt
update-ca-certificates

```

If the `curl` command works as expected, (404 on `https://api.forestadmin.com`), then the issue might come from the code. You could try to monkey-patch directly on your end, just in case you are still impacted by the `HTTPClient` issue declared [here](https://github.com/nahi/httpclient/issues/445).

Let me know if that helps 🙏