Region is missing
Any idea how to fix this?
[Nest] 16 - 06/24/2023, 6:41:42 PM ERROR [ExceptionHandler] Region is missing
Error: Region is missing
at resolveRegionConfig (/usr/src/app/node_modules/.pnpm/@[email protected]/node_modules/@aws-sdk/config-resolver/dist-cjs/regionConfig/resolveRegionConfig.js:9:15)
at new S3Client (/usr/src/app/node_modules/.pnpm/@[email protected]/node_modules/@aws-sdk/client-s3/dist-cjs/S3Client.js:23:69)
at new S3StorageService (/usr/src/app/packages/application-generic/build/main/services/storage/storage.service.js:34:19)
11 Replies
hi @harrisyn Please share steps to reproduce this
Hi @Pawan Jain
I am not sure exactly how I got to it, I setup a new VM using the last update 0.16, I then tried to set it up to use GCS, after restarting the containers I noticed that the error was there so the api fails to start, I have tried reverting to the previous config and it still remains the same.
Also I wonder, when I look at the compose file, it has entries for AWS storage, however there is none for GCS, should I be updating that file with any specific env changes for GCS (my .env is in the same folder as the compose file, so I expected it to work), also left an issue on github relating to the omission of restart on most of the services as well.
We do not support GCS at this time as there unfortunately are to many differences to support this by just switching the urls.
If your interested in building a PR for this, we would be more then happy to review it!
Thank you for reaching out with your question.
Thanks for the response @zacclifton , I suppose then I can only use LocalStack in the interim, also I still have the error above, any ideas how to go beyond that?
I don't have a strong need for GCS, I only need to be able to save the brand logo, I am unsure what else requires storage down the line.
Update: I cleared all docker images and volumes and ran docker compose and the error no longer shows up.
I still need help with two issues.
1) {
"statusCode": 404,
"message": "In app integration could not be found",
"error": "Not Found"
}
this is the response to the "v1/widgets/session/initialize" endpoint call from within the frontend
2) I know it is probably configuration related, but I am trying to connect to the widget also from a client app running locally, and I get a preflight CORS error
For first error, make this first in-app novu active
for 2nd error, there must be some mismatch in environment variables
@Pawan Jain any suggestions which of the env variables I should be adjusting for this?
for context, novu is setup behind nginx using proxies@harrisyn
Checkout this post https://discord.com/channels/895029566685462578/1097448355237462017
Hi @Pawan Jain already did and contributed to that thread before, then I hadn't set up notification on any client, I have all other parts running well now, it's the connection from the web client that's failing now.
I see this is generated in newRelic.js script
New relic is not a required dependency
Is this error stopping you in using novu?
@Pawan Jain no this isn't generated from newRelic, i left tthe newRelic log there to show the preflight message, the CORS error on the initialize is the connection to Novu that fails, these logs are from another application attempting to connect to the Novu backend from React