DIYgod/RSSHub · error · Error
接口错误,错误代码:${responseBody.code},错误原因:${responseBody.msg}
Error message
接口错误,错误代码:${responseBody.code},错误原因:${responseBody.msg} What it means
Thrown when the Nowcoder recommendation API (`www.nowcoder.com/recommand/activity?token=&type=3`) returns a non-zero `code`. The handler sends no user-specific parameters (no ctx input beyond defaults), so this is purely an upstream availability or business error.
Source
Thrown at lib/routes/nowcoder/recommend.ts:32
supportPodcast: false,
supportScihub: false,
},
radar: [
{
source: ['nowcoder.com/'],
},
],
name: '求职推荐',
maintainers: ['junfengP'],
handler,
url: 'nowcoder.com/',
};
async function handler() {
const link = `https://www.nowcoder.com/recommand/activity?token=&type=3&_=${Date.now()}`;
const responseBody = (await got.get(link)).data;
if (responseBody.code !== 0) {
throw new Error(`接口错误,错误代码:${responseBody.code},错误原因:${responseBody.msg}`);
}
const data = responseBody.data.activitys;
return {
title: '牛客网-推荐',
link: 'https://www.nowcoder.com/recommend',
description: '牛客网-推荐',
item: data.map((item) => ({
title: item.name,
description: `<img src="${item.img}">`,
link: `https://www.nowcoder.com${item.url}`,
})),
};
}
View on GitHub (pinned to bed535e087)
Solutions
- Retry the request after a few minutes.
- Open `https://www.nowcoder.com/recommand/activity?token=&type=3&_=<timestamp>` in a browser to check the live response.
- If the endpoint changed, update line 28 of `lib/routes/nowcoder/recommend.ts`.
- Add caching to reduce the blast radius of repeated failures.
Defensive patterns
Strategy: retry
Try / catch
try {
const responseBody = (await got.get(link)).data;
if (responseBody.code !== 0) {
throw new Error(`接口错误,错误代码:${responseBody.code},错误原因:${responseBody.msg}`);
}
} catch (e) {
logger.error(`Nowcoder recommend API failed: ${e}`);
throw e;
} Prevention
- Cache the recommendation feed since it is parameterless.
- Monitor the endpoint for deprecation.
- Use config.trueUA for requests.
When it happens
Trigger: Any request to the nowcoder recommend route when the upstream recommand/activity API returns an error code. Since the handler is parameterless, the error is entirely upstream-driven.
Common situations: The recommendation API endpoint was deprecated or renamed. The upstream server returns an error during maintenance windows. Anti-crawler measures block the RSSHub User-Agent.
Related errors
- 接口错误,错误代码:${responseBody.code},错误原因:${responseBody.msg}
- 接口错误,错误代码: ${responseBody.code},错误原因: ${responseBody.msg}
- 接口错误,错误代码:${responseBody.code},错误原因:${responseBody.msg}
- 接口错误,错误代码:${responseBody.code},错误原因:${responseBody.msg}
- Invalid type parameter
AI-assisted analysis of DIYgod/RSSHub@bed535e087 (2026-08-12).
Data as JSON: /api/errors/7811e71438aad144.
Report an issue: GitHub.