色花堂 - Authentication failed. Access denied.

[ak502-hk]

Routes

/sehuatang/gqzwzm

Full routes

https://rss.ing.gs/sehuatang/gqzwzm

Related documentation

https://docs.rsshub.app/routes/multimedia#%E8%89%B2%E8%8A%B1%E5%A0%82

What is expected?

RSS feed

What is actually happening?

Route requested: /sehuatang/gqzwzm

Error message: Authentication failed. Access denied.

Helpful Information to provide when opening issue:
Path: /sehuatang/gqzwzm
Node version: v18.20.8
Git Hash: 659e3ad

Deployment information

Self-hosted

Deployment information (for self-hosted)

No response

Additional info

Route requested: /sehuatang/gqzwzm

Error message: Authentication failed. Access denied.

Helpful Information to provide when opening issue:
Path: /sehuatang/gqzwzm
Node version: v18.20.8
Git Hash: 659e3ad

This is not a duplicated issue

• I have searched existing issues to ensure this bug has not already been reported

[github-actions]

I found similar issues that might help:

• 配置 ACCESS_KEY 导致 healthcheck 失败 #17090 (similarity: 0.85)
• Pixiv - User Activity 获取失败 #15425 (similarity: 0.81)

[github-actions]

Searching for maintainers:

• /sehuatang/gqzwzm: Route not found

To maintainers: if you are not willing to be disturbed, list your username in scripts/workflow/test-issue/call-maintainer.js. In this way, your username will be wrapped in an inline code block when tagged so you will not be notified.

If all routes can not be found, the issue will be closed automatically. Please use NOROUTE for a route-irrelevant issue or leave a comment if it is a mistake.
如果所有路由都无法匹配，issue 将会被自动关闭。如果 issue 和路由无关，请使用 NOROUTE 关键词，或者留下评论。我们会重新审核。

[dosubot]

Hi @ak502-hk! I'm Dosu and I’m helping the RSSHub team.

The /sehuatang/gqzwzm route relies on fetching a "safeid" token from the 色花堂 homepage and setting it as a _safe cookie for all requests. If this cookie is missing, invalid, or expired, you'll get "Authentication failed. Access denied." This can happen if the site changes its anti-bot mechanism, the token can't be fetched, or the cache is stale. For most /sehuatang routes, this process is automatic, but for user-based routes, you need to set the SEHUATANG_COOKIE environment variable with a valid 色花堂 cookie in your deployment config.

To troubleshoot: check your server's network access to 色花堂, clear the cache, make sure you're running the latest RSSHub version, and review logs for more details. If the problem persists, it's likely due to stricter anti-bot measures or recent site changes, which may require waiting for an upstream fix or further investigation.
Source 1 | Source 2

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}