# Problems authenticating when upgrading to v7 of Liana (forest-express-mongoose)

**URL:** <https://community.forestadmin.com/t/problems-authenticating-when-upgrading-to-v7-of-liana-forest-express-mongoose/2681>\
**Category:** Help me!\
**Created:** [June 12, 2021, 7:24am UTC](https://community.forestadmin.com/t/problems-authenticating-when-upgrading-to-v7-of-liana-forest-express-mongoose/2681 "2021-06-12T07:24:02Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Richard\_Garner](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/richard_garner/32/1136_2.png) [@Richard\_Garner](https://community.forestadmin.com/u/Richard_Garner)\
**Post date:** [June 12, 2021, 7:24am UTC](https://community.forestadmin.com/t/problems-authenticating-when-upgrading-to-v7-of-liana-forest-express-mongoose/2681/1 "2021-06-12T07:24:03Z")

</div>

I just did the upgrade from `"forest-express-mongoose": "^3.2.4"`, to `"forest-express-mongoose": "^7.7.1"` as per your docs [Upgrade to v7 - Documentation](https://docs.forestadmin.com/documentation/how-tos/maintain/upgrade-notes-sql-mongodb/upgrade-to-v7). Just having some trouble with the authentication now though. I don’t have my express server running on port 433 with HTTPS but instead, I have a load balancer in front of it that handles the HTTPS side of things. This worked with the previous version of Liana but not now. From the error message given it seems to be expecting the express node process itself to be running on port 433 locally.

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/2X/4/476008572035283823ea9e10a09daf6fc205732d.png)

Is this correct, it seems to be overly restrictive to dictate how the process runs on the server. Is there any way around this?

- Package Version: 7.7.1
- Express Version: 4.17
- Database Dialect: MongoDB

These are the logs on my node server when this happens:

```javascript

[forest] 🌳🌳🌳 Unable to register the client
{
  "configuration": {
    "authorization_endpoint": "https://api.forestadmin.com/oidc/auth",
    "device_authorization_endpoint": "https://api.forestadmin.com/oidc/device/auth",
    "claims_parameter_supported": false,
    "claims_supported": [
      "sub",
      "email",
      "sid",
      "auth_time",
      "iss"
    ],
    "code_challenge_methods_supported": [
      "S256"
    ],
    "end_session_endpoint": "https://api.forestadmin.com/oidc/session/end",
    "grant_types_supported": [
      "authorization_code",
      "urn:ietf:params:oauth:grant-type:device_code"
    ],
    "id_token_signing_alg_values_supported": [
      "HS256",
      "RS256"
    ],
    "issuer": "https://api.forestadmin.com",
    "jwks_uri": "https://api.forestadmin.com/oidc/jwks",
    "registration_endpoint": "https://api.forestadmin.com/oidc/reg",
    "response_modes_supported": [
      "query"
    ],
    "response_types_supported": [
      "code",
      "none"
    ],
    "scopes_supported": [
      "openid",
      "email",
      "profile"
    ],
    "subject_types_supported": [
      "public"
    ],
    "token_endpoint_auth_methods_supported": [
      "none"
    ],
    "token_endpoint_auth_signing_alg_values_supported": [],
    "token_endpoint": "https://api.forestadmin.com/oidc/token",
    "request_object_signing_alg_values_supported": [
      "HS256",
      "RS256"
    ],
    "request_parameter_supported": false,
    "request_uri_parameter_supported": true,
    "require_request_uri_registration": true,
    "claim_types_supported": [
      "normal"
    ]
  },
  "registration": {
    "redirect_uris": [
      "http://localhost:3000/forest/authentication/callback"
    ],
    "token_endpoint_auth_method": "none"
  },
  "error": {
    "name": "RequestError",
    "code": "ECONNREFUSED",
    "timings": {
      "start": 1623482042173,
      "socket": 1623482042173,
      "lookup": 1623482042173,
      "error": 1623482042174,
      "phases": {
        "wait": 0,
        "dns": 0,
        "total": 1
      }
    }
  }
}
[forest] 🌳🌳🌳 Unexpected error: connect ECONNREFUSED 127.0.0.1:443
{
  "name": "RequestError",
  "code": "ECONNREFUSED",
  "timings": {
    "start": 1623482042173,
    "socket": 1623482042173,
    "lookup": 1623482042173,
    "error": 1623482042174,
    "phases": {
      "wait": 0,
      "dns": 0,
      "total": 1
    }
  },
  "stack": "RequestError: connect ECONNREFUSED 127.0.0.1:443\n at ClientRequest.<anonymous> (/home/ubuntu/out-there-api/node_modules/got/dist/source/core/index.js:956:111)\n at Object.onceWrapper (events.js:422:26)\n at ClientRequest.emit (events.js:327:22)\n at ClientRequest.EventEmitter.emit (domain.js:486:12)\n at ClientRequest.origin.emit (/home/ubuntu/out-there-api/node_modules/@szmarczak/http-timer/dist/source/index.js:39:20)\n at TLSSocket.socketErrorListener (_http_client.js:469:9)\n at TLSSocket.emit (events.js:315:20)\n at TLSSocket.EventEmitter.emit (domain.js:486:12)\n at emitErrorNT (internal/streams/destroy.js:106:8)\n at emitErrorCloseNT (internal/streams/destroy.js:74:3)\n at processTicksAndRejections (internal/process/task_queues.js:80:21)\n at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)"

```

---

<div class="post-metadata">

**Author:** ![wawrzy](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/wawrzy/32/2431_2.png) [@wawrzy](https://community.forestadmin.com/u/wawrzy)\
**Post date:** [June 13, 2021, 11:06am UTC](https://community.forestadmin.com/t/problems-authenticating-when-upgrading-to-v7-of-liana-forest-express-mongoose/2681/2 "2021-06-13T11:06:14Z")

</div>

Hello, I got the same issue

This reply fixed it

> [@Authentication error after migrating to forest-express-sequelize v7](https://community.forestadmin.com/t/authentication-error-after-migrating-to-forest-express-sequelize-v7/2440/16):
>
> So the issue with ECONNREFUSED error and request to localhost was caused by 3-rd party packages using agent-base package (I had to update all of them to fix the issue). The original issue with callback url not working remains. For anyone else who’ll get here after having ECONNREFUSED error when requesting 127.0.0.1:443: run npm ls agent-base and try to update all of packages which are using agent-base package.

---

<div class="post-metadata">

**Author:** ![anon34731316](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@anon34731316](https://community.forestadmin.com/u/anon34731316)\
**Post date:** [June 14, 2021, 8:40am UTC](https://community.forestadmin.com/t/problems-authenticating-when-upgrading-to-v7-of-liana-forest-express-mongoose/2681/3 "2021-06-14T08:40:56Z")

</div>

Hello @Richard_Garner,

Thanks for your message and welcome to our community! 🙌

Let us know if @wawrzy’s message solved your issue 😉

Thanks!

---

<div class="post-metadata">

**Author:** ![Richard\_Garner](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/richard_garner/32/1136_2.png) [@Richard\_Garner](https://community.forestadmin.com/u/Richard_Garner)\
**Post date:** [June 14, 2021, 10:35pm UTC](https://community.forestadmin.com/t/problems-authenticating-when-upgrading-to-v7-of-liana-forest-express-mongoose/2681/4 "2021-06-14T22:35:03Z")

</div>

Thanks for the response! Much appreciated. I upgraded the packages. Before doing so I got this:

```javascript
yarn list agent-base
yarn list v1.22.10
warning Filtering by arguments is deprecated. Please use the pattern option instead.
├─ agent-base@4.3.0
├─ https-proxy-agent@5.0.0
│ └─ agent-base@6.0.2
├─ socks-proxy-agent@4.0.2
│ └─ agent-base@4.2.1
└─ teeny-request@6.0.3
   └─ agent-base@6.0.2
✨ Done in 0.70s.

```

Then I ran `yarn upgrade https-proxy-agent@latest agent-base@latest teeny-request@latest socks-proxy-agent@latest` and got the following, but I am still getting the same error I was before.

```javascript
yarn list agent-base
yarn list v1.22.10
warning Filtering by arguments is deprecated. Please use the pattern option instead.
├─ @google/maps@1.1.3
│ └─ agent-base@4.3.0
├─ agent-base@6.0.2
├─ http-proxy-agent@2.1.0
│ └─ agent-base@4.3.0
├─ pac-proxy-agent@3.0.1
│ ├─ agent-base@4.3.0
│ └─ socks-proxy-agent@4.0.2
│ └─ agent-base@4.2.1
└─ proxy-agent@3.0.3
   ├─ agent-base@4.3.0
   └─ socks-proxy-agent@4.0.2
      └─ agent-base@4.2.1
✨ Done in 0.72s.

```

Unfortunately this hasn’t solved the issue.

---

<div class="post-metadata">

**Author:** ![Richard\_Garner](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/richard_garner/32/1136_2.png) [@Richard\_Garner](https://community.forestadmin.com/u/Richard_Garner)\
**Post date:** [June 14, 2021, 10:35pm UTC](https://community.forestadmin.com/t/problems-authenticating-when-upgrading-to-v7-of-liana-forest-express-mongoose/2681/5 "2021-06-14T22:35:33Z")

</div>

Thanks, unfortunately it doesn’t appear to have solved my issue. Do you know why it’s trying to connect to `127.0.0.1:443` in the first place?

---

<div class="post-metadata">

**Author:** ![morganperre](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/morganperre/32/1296_2.png) [@morganperre](https://community.forestadmin.com/u/morganperre)\
**Post date:** [June 16, 2021, 7:02am UTC](https://community.forestadmin.com/t/problems-authenticating-when-upgrading-to-v7-of-liana-forest-express-mongoose/2681/6 "2021-06-16T07:02:26Z")

</div>

Hello @Richard_Garner,

Let’s try to help you. 🤝

**Upgrades**  
First of all, I see you upgraded from **v3** to **v7**. Did you follow all the upgrade notes version by version ( I mean v3 → [v4](https://docs.forestadmin.com/documentation/how-tos/maintain/upgrade-notes-sql-mongodb/upgrade-to-v4) → [v5](https://docs.forestadmin.com/documentation/how-tos/maintain/upgrade-notes-sql-mongodb/upgrade-to-v5) → [v6](https://docs.forestadmin.com/documentation/how-tos/maintain/upgrade-notes-sql-mongodb/upgrade-to-v6) → [v7](https://docs.forestadmin.com/documentation/how-tos/maintain/upgrade-notes-sql-mongodb/upgrade-to-v7)) ? It’s the best way to isolate potential regression.

**Your issue**  
The error `connect ECONNREFUSED 127.0.0.1:443`, means the agent is trying to connect to [https://localhost](https://localhost) when trying to register the client instead of calling our server. This error comes from a dependency that we use for OIDC management. See [this issue](https://github.com/panva/node-openid-client/issues/320) for more informations.

Back to you.

1. Looking at the trace your agent (backend) should be running on `http://localhost:3000`. Am I right ?
2. Can you try to upgrade `@google/maps` to the latest version ? I’ve seen that can cause the same error in an other thread.

Kind regards,  
Morgan

---

<div class="post-metadata">

**Author:** ![morganperre](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/morganperre/32/1296_2.png) [@morganperre](https://community.forestadmin.com/u/morganperre)\
**Post date:** [June 16, 2021, 8:11am UTC](https://community.forestadmin.com/t/problems-authenticating-when-upgrading-to-v7-of-liana-forest-express-mongoose/2681/9 "2021-06-16T08:11:27Z")

</div>

Hey,

It’s strongly encouraged to update to new agents that have enforced security and will continue to work on future Chrome version. You can find all detailed informations in the following thread.

> [@May 2021 - Agent upgrade to latest major version required](https://community.forestadmin.com/t/may-2021-agent-upgrade-to-latest-major-version-required/2435):
>
> Dear Forest Admin community, In light of upcoming Chrome browser updates, Forest Admin strongly encourages you to upgrade to the latest major version of our agents in order to keep your development environments up and running without service interruption. Please note that the remote and production environments of your projects won’t be impacted by the change below and will continue to run without necessary intervention. What is happening? In July 2021, with the release of Chrome 92, Chrome br…

As I said I found [a thread where the user had the same issue caused by` @google/maps`](https://community.forestadmin.com/t/unexpected-error-connect-econnrefused-127-0-0-1-443/2507/8). To be honest this specific issue is pretty obscure to me.

Cheers,  
Morgan

---

<div class="post-metadata">

**Author:** ![Richard\_Garner](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/richard_garner/32/1136_2.png) [@Richard\_Garner](https://community.forestadmin.com/u/Richard_Garner)\
**Post date:** [June 16, 2021, 8:46am UTC](https://community.forestadmin.com/t/problems-authenticating-when-upgrading-to-v7-of-liana-forest-express-mongoose/2681/10 "2021-06-16T08:46:20Z")

</div>

Awesome, removing `@google/maps` worked! It must’ve been messing with the http module or something. `@google/maps` is deprecated for `@googlemaps/google-maps-services-js`. I installed that in its place and, after a few minor changes to how the methods are called, it played nicely with Forest Admin.

Thanks so much @morganperre @anon34731316 @wawrzy ! Appreciate your help on this.

---

<div class="post-metadata">

**Author:** ![morganperre](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/morganperre/32/1296_2.png) [@morganperre](https://community.forestadmin.com/u/morganperre)\
**Post date:** [June 16, 2021, 8:53am UTC](https://community.forestadmin.com/t/problems-authenticating-when-upgrading-to-v7-of-liana-forest-express-mongoose/2681/11 "2021-06-16T08:53:25Z")

</div>

Glad you finally manage to resolve the problem. 🙏

Have a nice journey @Richard_Garner.