Expected behavior Access Forest Admin in the development environment after migrating to forest-express-sequelize@7 Actual behavior After upgrading from v6 to v7, there was no issue running our application locally. However, when trying to access the Development environment with v7 installed, I’m se…

Unfortunately, forest-express-sequelize depends on openid-client which depends on got, and the interaction is between got and signalfx-tracing. Other providers updated their packages, datadog with dd-trace for instance, to fix this issue. I think that the problem comes from signalfx-tracing and the…

Hello @rwinz , Some other users reported the same problem than yours on the v7, and it was caused by a third-party package that was interfering with HTTP requests. Can you please share with us the list of other packages that your application is depending on? Here are other topics covering the same…

Hi @GuillaumeGautreau , thank you for your assistance. Here is an excerpt from our application’s package.json showing the packages we are using "dependencies": { "@finicity/aws-secrets": "^3.1.0", "@finicity/express": "^8.1.0", "@finicity/public-constants": "^2.1.2", "@sendgrid/clie…

Hello, can you please try to deactivate signalfx-tracing? It seems to be present in the stack trace, and seems to be a good candidate. You can also try deactivating signalfx-collect.

Hi, thank you for the suggestion, it turns out that signalfx-tracing was in fact causing this issue. Unfortunately, signalfx-tracing is critical in our application and we are already on the latest version. I have already reached out to them, but I just thought I’d ask – is updating/removing that pa…

Okay, thanks again for your help!

@GuillaumeGautreau I too facing the same issue any updates whether it is fixed?

Hello @Vishnu_Gupta , I don’t know. Maybe you can ask to the authors of signalfx-tracing. The problem is linked to this library.

@GuillaumeGautreau We tried contacting the authors of signalfx-tracing library but there is no positive response to resolve the issue. Could it be possible to have this issue resolved by creating or setting a new FOREST_CLIENT_ID ? If you could suggest some other solution, it would be very helpful.

Can you open a different thread for your problem? I’m not sure it’s related to the original problem.

Unable to register the client, Unexpected error: connect ECONNREFUSED 127.0.0.1:443

Help me!

Vishnu_Gupta May 31, 2022, 1:29pm 13

started a new thread Issue between `signalfx-tracing` and `forest-express-moongose` sass

Topic		Replies	Views
Unexpected error: connect ECONNREFUSED 127.0.0.1:443 Help me! setup	10	8213	May 31, 2021
Problems authenticating when upgrading to v7 of Liana (forest-express-mongoose) Help me!	8	1220	June 16, 2021
Authentication error after migrating to forest-express-sequelize v7 Help me!	19	3678	July 7, 2021
Upgrade to forest-express-mongoose@7.x.x failed due to openid login callback Help me! setup	8	1016	May 28, 2021
Unable to register the client error after upgrade v7 Help me!	22	993	December 2, 2022

Unable to register the client, Unexpected error: connect ECONNREFUSED 127.0.0.1:443

Related topics