Q: Persistent TimeoutError: ResourceRequest timed out (with 500 errors) on Vercel + MongoDB Atlas M0 using Waline v3 #3051
Replies: 2 comments 3 replies
-
How you config mongodb?The env settings format should be like following doc https://waline.js.org/en/guide/database.html#mongodb |
Beta Was this translation helpful? Give feedback.
3 replies
-
I changed it to a different comment system. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug | 问题描述
Issue Body:
Environment:
@waline/vercel
(set tolatest
inpackage.json
, assumed to be v3 based on Vercel template/preview)@waline/client@v3
via unpkg inwaline.html
, displaying version v3.5.6)Bug Description:
I deployed the backend using the latest Waline Vercel template and configured MongoDB Atlas M0 as the database. The frontend is also using Waline Client v3 (v3.5.6). However, I am unable to use the comment functionality due to persistent timeout errors during comment loading and submission.
Problem Progression:
MONGO_URI
andDB_TYPE: MongoDB
environment variables, the Vercel runtime logs consistently showedError: Not initialized
errors referencingleancloud-storage
paths (resulting in 500 server errors). It appeared the backend was ignoring the MongoDB settings.MONGO_URI
and setting individual MongoDB environment variables (MONGO_HOST
,MONGO_DB
,MONGO_USER
,MONGO_PASSWORD
,MONGO_AUTHSOURCE
,MONGO_OPT_SSL
) and redeploying, the LeanCloud-related errors disappeared. This suggested the backend was now recognizing the intention to use MongoDB.TimeoutError: ResourceRequest timed out
errors occur in the Vercel runtime logs. The browser console shows 500 Internal Server Error along withFailed to fetch
errors for the corresponding requests.Steps Taken:
MONGO_URI
method and the individual MongoDB environment variables method.index.js
(orindex.cjs
) code uses the default (module.exports = Waline();
).waline.html
to use the Waline Client v3 loading method.package.json
uses"latest"
for the@waline/vercel
version (assumed v3).vercel.json
(no longer seeing CORS errors).Expected Behavior:
The comment functionality should work without timeouts.
Actual Behavior:
Backend requests result in timeout errors (Vercel:
TimeoutError
, Browser: 500).Relevant Logs (Vercel Runtime Log Type):
Question:
Are there known performance issues or timeout problems when using the Waline v3 backend with MongoDB Atlas M0 free tier on the Vercel Hobby plan? Is this issue likely caused by the performance limitations of the M0 tier, or is it possible that the
@waline/vercel
package itself requires optimization or bug fixes related to MongoDB interaction in this environment?Any advice or potential solutions would be greatly appreciated.
Website URL | 问题网站
https://tipsyoncola.gitlab.io/posts/my-first-post/
Where your waline deploy? | 服务部署在哪里?
Vercel (Default)
Where your comment data store? | 数据存储在哪里?
MongoDB
Beta Was this translation helpful? Give feedback.
All reactions