You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to run the npx novu@latest sync command with the specified parameters, the process fails with a 431 Request Header Fields Too Large error. This issue appears to occur during a POST request to the self hosted <REDACTED> endpoint.
👟 Reproduction steps
Install the latest version of Novu CLI using npx novu@latest.
Run the sync command with the following parameters: * --bridge-url <REDACTED> * --secret-key <REDACTED> * --api-url <REDACTED>
👍 Expected behavior
The npx novu@latest sync command should execute successfully, syncing the specified bridge URL, secret key, and API URL without errors. It should establish a connection to the server and complete the sync process without triggering any HTTP status code errors.
👎 Actual Behavior with Screenshots
Novu version
2.1.0
npm version
10.1.0
node version
20.8.1
📃 Provide any additional context for the Bug.
I also tried Github action with the same results
👀 Have you spent some time to check if this bug has been raised before?
📜 Description
When attempting to run the
npx novu@latest sync
command with the specified parameters, the process fails with a431 Request Header Fields Too Large
error. This issue appears to occur during a POST request to the self hosted<REDACTED>
endpoint.👟 Reproduction steps
npx novu@latest
.sync
command with the following parameters: *--bridge-url <REDACTED>
*--secret-key <REDACTED>
*--api-url <REDACTED>
👍 Expected behavior
The
npx novu@latest sync
command should execute successfully, syncing the specified bridge URL, secret key, and API URL without errors. It should establish a connection to the server and complete the sync process without triggering any HTTP status code errors.👎 Actual Behavior with Screenshots
Novu version
2.1.0
npm version
10.1.0
node version
20.8.1
📃 Provide any additional context for the Bug.
I also tried Github action with the same results
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Contributing Guidelines?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: