-
Notifications
You must be signed in to change notification settings - Fork 525
Open
Description
问题描述 | Describe the bug
Telegram notifications are not working after adding the necessary environment variables and redeploying the service on Vercel.
When a comment is posted, the API returns a 200 status code, but the notification is not sent to Telegram.
Additionally, the Vercel Function logs show configuration warnings/errors related to the database connection (TiDB via MySQL2 protocol):
Ignoring invalid configuration option passed to Connection: acquireWaitTimeoutIgnoring invalid configuration option passed to Connection: handleIgnoring invalid configuration option passed to Connection: prefix
复现步骤 | Steps to reproduce
- Add Telegram bot token and chat ID environment variables.
- Redeploy the Waline service on Vercel.
- Post a new comment on the website.
- No notification is received in the Telegram chat, even though the comment is successfully created (API returns 200).
期望行为 | Expected behavior
Telegram notification should be sent successfully after a comment is posted.
相关的日志数据 | Relevant log output
03:58:43.568 Ignoring invalid configuration option passed to Connection: acquireWaitTimeout. This is currently a warning, but in future versions of MySQL2, an error will be thrown...
03:58:43.568 Ignoring invalid configuration option passed to Connection: handle. This is currently a warning, but in future versions of MySQL2, an error will be thrown...
03:58:43.568 Ignoring invalid configuration option passed to Connection: prefix. This is currently a warning, but in future versions of MySQL2, an error will be thrown...
环境信息 | Environment
- Waline version: (Latest)
- Deployment: Vercel
- Database: TiDB
- Website URL: https://gavined.com/ (API: https://api.gavined.com/) (Auth: https://auth.gavined.com/)
Screenshot
问题网站 | Website URL
服务部署在哪里? | Where your waline deploy?
Vercel (Default)
数据存储在哪里?| Where your comment data store?
TiDB
Metadata
Metadata
Assignees
Labels
No labels