-
Notifications
You must be signed in to change notification settings - Fork 425
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Webhook stops working #263
Comments
None of my webhooks work. I enter the URL and nothing gets there. I'm also using docker. |
In this case, the problem might be in the settings. Check the environment variables related to webhooks. Run exec /bin/bash to open a terminal in your container, and try accessing the endpoint using curl from within it. |
This my settings. Both are correct. I have tested with curl in my local machine, linux 22, and from my vps. API_KEY=XXXXXXXXXXXXXXXXXXXXXXXX
BASE_WEBHOOK_URL=https://webhook.site/XXXXXXXXXXXXXXXXXX
DISABLED_CALLBACKS=
ENABLE_LOCAL_CALLBACK_EXAMPLE=false
ENABLE_SWAGGER_ENDPOINT=true
MAX_ATTACHMENT_SIZE=10000000
PORT=3000
RATE_LIMIT_MAX=1000
RATE_LIMIT_WINDOW_MS=1000
RECOVER_SESSIONS=true
SESSIONS_PATH=./sessions
SET_MESSAGES_AS_SEEN=false
WEB_VERSION='2.2328.5'
WEB_VERSION_CACHE_TYPE=none Inside docker, I don't have curl. Is it required? |
It`s required for testing only |
So where is the error? |
I have two computers with Windows 11, Node 22 and PM2. They have been running since May of this year and one of them no longer triggers the webhook, it does not send any data, it does not even call the URL that was previously configured and working. |
To solve this issue, I forked the project and modified the code to write the webhook data directly to the database. |
When I start the service, the webhook runs well. But after an undetermined amount of time, it stops working. Is anyone else experiencing this? Ps: I am running with docker.
The text was updated successfully, but these errors were encountered: