English
Configuration
Configure RSSHub by setting environment variables
Network Configuration
PORT: listening port, default to 1200
SOCKET: listening Unix Socket, default to null
LISTEN_INADDR_ANY: open up for external access, default to 1
DISABLE_IPV6: disable IPv6 support, when enabled, RSSHub will listen on 0.0.0.0 instead of ::, default to false
REQUEST_RETRY: retries allowed for failed requests, default to 2
REQUEST_TIMEOUT: milliseconds to wait for the server to end the response before aborting the request with error, default to 3000
REQUEST_AUTO_SELECT_FAMILY: controls Node's address-family autoselection for outgoing connections made by RSSHub's default dispatcher and TLS-version-specific agents. Leaving it unset preserves Node's default. true lets Node automatically attempt IPv4 and IPv6 addresses; false disables automatic family selection without forcing IPv4. This setting is not used in Workers and does not change RSSHub's listening address.
REQUEST_RATE_LIMITS: JSON object of outgoing request limits keyed by exact hostname, default {}. Each policy requires points (a positive integer number of requests) and duration (a positive number of seconds). For example, {"api.example.com":{"points":2,"duration":1}} spaces request starts at least 0.5 seconds apart and queues excess requests. Subdomains are separate hosts. Limits are local to each Node process or Worker isolate and do not coordinate multiple instances. The existing Node global limit of 10 outgoing requests per second remains in effect. Only requests through RSSHub's fetch wrapper are covered, not requests made inside browser sessions.
UA: user agent, using random user agent (Chrome on macOS) by default
NO_RANDOM_UA: disable random user agent, default to null
CORS Request
RSSHub by default reject CORS requests. This behavior can be modified via setting ALLOW_ORIGIN: * or ALLOW_ORIGIN: www.example.com.
Cache Configurations
RSSHub supports two caching methods: memory and redis, it is recommended to use redis for persistent caching.
CACHE_TYPE: cache type, memory or redis, empty this value will disable caching, default to memory
CACHE_EXPIRE: route cache expiry time in seconds, default to 5 * 60
CACHE_CONTENT_EXPIRE: content cache expiry time in seconds, it will be recalculated when it is accessed, default to 1 * 60 * 60
REDIS_URL: Redis target address (invalid when CACHE_TYPE is set to memory), default to redis://localhost:6379/
MEMORY_MAX: maximum number of cached items (invalid when CACHE_TYPE is set to redis), default to 256
Proxy Configurations
Partial routes have a strict anti-crawler policy, and can be configured to use proxy.
PROXY_URI: The proxy URI should be in the format {protocol}://{host}:{port}. Supported protocols: http, https, socks, socks5 and socks5h. socks4 and socks4a are not supported, and setting them disables the proxy. Use socks5h or socks to resolve DNS through the proxy.
PROXY_AUTH: Authentication credentials for the proxy server, will add header Proxy-Authorization: Basic ${PROXY_AUTH}
PROXY_URL_REGEX: Regular expression of URL to enable proxy, all enabled by default .*
TIP
For failover or load balancing across multiple proxies, set PROXY_URI to a gost instance. You can then change proxies in gost without restarting RSSHub and losing the in-memory cache.
Access Control Configurations
RSSHub supports access control using access keys/codes. Enabling it will activate global access control, and lack of access permission will result in denied access.
Allowlisting/denylisting
This configuration has been removed. It is recommended to use a proxy server such as Nginx or Cloudflare for access control.
Access Key/Code
ACCESS_KEY: the access key. When set, access via the key directly or the access code described above
Access code is the md5 generated based on the access key + route, eg:
| Access key | Route | Generating access code | Access code |
|---|---|---|---|
| ILoveRSSHub | /qdaily/column/59 | md5('/qdaily/column/59' + 'ILoveRSSHub') | 0f820530128805ffc10351f22b5fd121 |
Routes are accessible via
code, eg:https://rsshub.app/qdaily/column/59?code=0f820530128805ffc10351f22b5fd121Or using
keydirectly, eg:https://rsshub.app/qdaily/column/59?key=ILoveRSSHub
Healthcheck Configuration
When ACCESS_KEY is enabled, the healthcheck endpoint also requires authentication.
For a Docker Compose deployment, you'll need to update the healthcheck configuration in your docker-compose.yml to include the access key or access code parameter.
The recommended configuration is:
diff
healthcheck:
- test: ["CMD", "curl", "-f", "http://localhost:1200/healthz"]
+ test: ["CMD", "curl", "-f", "http://localhost:1200/healthz?key=${ACCESS_KEY}"]Logging Configurations
DEBUG_INFO: display route information on the homepage for debugging purposes. When set to neither true nor false, use parameter debug to enable display, eg: https://rsshub.app/?debug=value_of_DEBUG_INFO . Default to true
LOGGER_LEVEL: specifies the maximum level of messages to the console and log file, default to info
NO_LOGFILES: disable logging to log files, default to false
SHOW_LOGGER_TIMESTAMP: Show timestamp in log, default to false
SENTRY: Sentry dsn, used for error tracking
HONEYBADGER_API_KEY: Honeybadger API key, used for error tracking
ERROR_TRACKING_ROUTE_TIMEOUT: Report to error tracking service (Sentry or Honeybadger) if route execution takes more than this milliseconds, default to 30000 ms. This option is previously named SENTRY_ROUTE_TIMEOUT, and the old name is still supported for backward compatibility, but it is recommended to switch to the new name.
Image Processing
New Config Format
We are currently testing out a new format, providing end-user with more flexibility. For more info, please refer to Parameters->Multimedia processing.
When using our new config, please leave the following environment vairable blank. By default, image hotlink template will be forced when present.
HOTLINK_TEMPLATE: replace image URL in the content to avoid anti-hotlink protection, leave it blank to disable this function. Usage reference #2769. You may use any property listed in URL (suffixing with _ue results in URL encoding), format of JS template literal. e.g. ${protocol}//${host}${pathname}, https://i3.wp.com/${host}${pathname}, https://images.weserv.nl?url=${href_ue}
HOTLINK_INCLUDE_PATHS: limit the routes to be processed, only matched routes will be processed. Set multiple values with comma , as delimiter. If not set, all routes will be processed
HOTLINK_EXCLUDE_PATHS: exclude routes that do not need to be processed, all matched routes will be ignored. Set multiple values with comma , as delimiter. Can be used alone, or to exclude routes that are already included by HOTLINK_INCLUDE_PATHS. If not set, no routes will be ignored
Route matching pattern
HOTLINK_INCLUDE_PATHS and HOTLINK_EXCLUDE_PATHS match the root path and all recursive sub-paths of the route, but not substrings. Note that the path must start with / and end without /.
e.g. /example, /example/sub and /example/anthoer/sub/route will be matched by /example, but /example_route will not be matched.
It is also valid to contain route parameters, e.g. /weibo/user/2612249974.
Features
Experimental features
Configs in this sections are in beta stage, and are turn off by default. Please read corresponded description and turn on if necessary.
ALLOW_USER_HOTLINK_TEMPLATE: Parameters->Multimedia processing
FILTER_REGEX_ENGINE: Define Regex engine used in Parameters->filtering. Valid value are [re2, regexp]. Default value is re2. We suggest public instance should leave this value to default, and this option right now is mainly for backward compatibility.
ALLOW_USER_SUPPLY_UNSAFE_DOMAIN: allow users to provide a domain as a parameter to routes that are not in their allow list, respectively. Public instances are suggested to leave this value default, as it may lead to Server-Side Request Forgery (SSRF)
Other Application Configurations
DISALLOW_ROBOT: prevent indexing by search engine, default to enable, set false or 0 to disable
ENABLE_CLUSTER: enable cluster mode, default to false
NODE_ENV: display error message on pages for authentication failing, default to production (i.e. no display)
NODE_NAME: node name, used for load balancing, identify the current node
USER_ROUTES_PATH: directory containing private route modules, unset by default. Supported in Node and Docker deployments. Put standalone .mjs ES modules that export namespace and routes in this directory; modules are loaded at startup, so changes require a restart. Private namespaces cannot override built-in namespaces. Setting this variable does not add access protection; configure ACCESS_KEY or protect the instance separately when needed. See Private routes for module format and mounting instructions.
PLAYWRIGHT_WS_ENDPOINT: remote browser WebSocket endpoint using the Playwright protocol. The server must use a compatible Playwright version. Do not put a Chromium CDP endpoint in this variable. PUPPETEER_WS_ENDPOINT remains a fallback alias when PLAYWRIGHT_WS_ENDPOINT is unset.
PLAYWRIGHT_CDP_ENDPOINT: Chromium Chrome DevTools Protocol endpoint for Node deployments. The Docker Compose Browserless V2 service uses ws://browserless:3000?token=<token>, where the token must match the Browserless service's TOKEN. In Node, this setting takes precedence over PLAYWRIGHT_WS_ENDPOINT and a locally launched browser. Workers use PLAYWRIGHT_WS_ENDPOINT or their Browser Run binding instead.
CHROMIUM_EXECUTABLE_PATH: path to the local Chromium or Chrome executable used by Playwright. It applies when neither a CDP nor a WebSocket endpoint is configured. For Docker deployments that use a local browser, use the chromium-bundled image.
TITLE_LENGTH_LIMIT: limit the length of feed title generated in bytes, an English alphabet counts as 1 byte, the rest such as Chinese, Japanese, Korean or Arabic counts as 2 bytes by design, default to 150
FORMAT: output format, default to rss; the format parameter, if specified in the feed address, will override this setting
OPENAI_API_KEY: OpenAI API Key, used for using ChatGPT to summarize articles
OPENAI_MODEL: OpenAI model name, used for using ChatGPT to summarize articles, default to gpt-3.5-turbo-16k, see OpenAI API reference for details
OPENAI_TEMPERATURE: OpenAI temperature parameter, used for using ChatGPT to summarize articles, default to 0.2, see OpenAI API reference for details
OPENAI_MAX_TOKENS: OpenAI maximum token number, used for using ChatGPT to summarize articles, default to null, see OpenAI API reference for details
OPENAI_API_ENDPOINT: OpenAI API URL, used for using ChatGPT to summarize articles, default to https://api.openai.com/v1, see OpenAI API reference for details
OPENAI_PROMPT: OpenAI prompt, used for using ChatGPT to summarize articles, see OpenAI API reference for details
REMOTE_CONFIG: Remote configuration URL, used for dynamically updating configurations. The address should return a JSON with an environment variable name as the key. It will be loaded and merged with local configurations when the application starts. In case of conflicts with local configurations, remote configurations will take precedence. But please note that some basic configuration items do not support remote retrieval.
Route-specific Configurations
TIP
Configs here are incomplete.
See docs of the specified route and lib/config.ts for detailed information.
4399 论坛
GAME_4399: 对应登录后的 cookie 值,获取方式:- 在 4399 首页登录。
- 打开开发者工具,切换到 Network 面板,刷新
- 查找
www.4399.com的访问请求,点击请求,在右侧 Headers 中找到 Cookie.
bilibili
BILIBILI_COOKIE_{uid}: 用于用户关注动态系列路由,对应 uid 的 b 站用户登录后的 Cookie 值,{uid}替换为 uid,如BILIBILI_COOKIE_2267573,获取方式:- 打开 https://api.vc.bilibili.com/dynamic_svr/v1/dynamic_svr/dynamic_new?uid=0&type=8
- 打开控制台,切换到 Network 面板,刷新
- 点击 dynamic_new 请求,找到 Cookie
- 视频和专栏,UP 主粉丝及关注只要求
SESSDATA字段,动态需复制整段 Cookie(删掉bili_ticket和bili_ticket_expires字段来延长有效期)
BILIBILI_DM_IMG_LIST: 用于获取UP主投稿系列的路由,获取方式:- 打开 任意UP主个人空间页
- 打开控制台,切换到 Network 面板,关闭缓存,刷新,鼠标在窗口内不断移动
- 使用过滤器找到符合
https://api.bilibili.com/x/space/wbi/arc/search的请求 - 复制请求参数中
dm_img_list字段的内容,如[{"x":2721,"y":615,"z":0,"timestamp":29,"type":0}]
Bitbucket
BITBUCKET_USERNAME: Your Bitbucket usernameBITBUCKET_PASSWORD: Your Bitbucket app password
BTBYR
BTBYR_HOST: 支持 ipv4 访问的 BTBYR 镜像,默认为原站https://bt.byr.cn/。BTBYR_COOKIE: 注册用户登录后的 Cookie 值,获取方式:- 登录后打开网站首页
- 打开控制台,刷新
- 找到
https://bt.byr.cn/index.php请求 - 找到请求头中的 Cookie
BUPT
BUPT_PORTAL_COOKIE: 登录后获得的 Cookie 值,获取方式- 打开 https://webapp.bupt.edu.cn/wap/login.html?redirect=https:// 并登录
- 无视掉报错,并打开 https://webapp.bupt.edu.cn/extensions/wap/news/list.html?p-1&type=xnxw
- 打开控制台,刷新
- 找到
https://webapp.bupt.edu.cn/extensions/wap/news/list.html?p-1&type=xnxw请求 - 找到请求头中的 Cookie
Ci-en
CI_EN_COOKIE: optional Cookie request header value from your signed-in Ci-en account, used by/dlsite/ci-en/:id/article. The same Cookie is sent for the article list and details, and detail caches are separated by Cookie value. Leave it unset for public articles. Access to subscriber articles remains limited to your account and subscribed plans.
Civitai
CIVITAI_COOKIE: Cookie of Civitai
Dianping
DIANPING_COOKIE: 大众点评登录后的 Cookie 值,获取方式:访问https://m.dianping.com,登录,输入document.cookie获取
Discord
DISCORD_AUTHORIZATION: Discord authorization token, can be found in the header of XHR requests after logging in Discord web client
Discourse
DISCOURSE_CONFIG_{id}:idcould be arbitrary number or string, while the value should be the format of{"link":link,"key":key}, where:linkis the link to the forum.keyis the access key for the forum API, which you can refer to this snippet to obtain one. Ensure that this key is granted sufficient permission.
Discuz cookie
DISCUZ_COOKIE_{cid}: Cookie of a forum powered by Discuz, cid can be anything from 00 to 99. When visiting a Discuz route, use cid to specify this cookie.
Disqus
DISQUS_API_KEY: Disqus API
douban
DOUBAN_COOKIE: Cookie from your own signed-in Douban account. Used by personal lists and by group topics that require login; public group topics can be accessed without it. The account must have access to the requested content.
/douban/group/topic/:id/:author? tracks the main post and the first page of replies. author defaults to all; use author to request the source website's author-only view. Changes to the main post title or body produce a new GUID. Replies keep their source creation times. The source sorts replies from oldest to newest, so new replies on later pages of a long topic are not covered.
User broadcasts and gallery topics add source IP locations to categories when the detail page provides them: IP属地:… for the author and 回帖IP属地:… for first-page replies. You can use the common filter_category parameter, for example filter_category=^IP属地:广东$. Profile locations are not used as IP locations. Details hidden from anonymous visitors require DOUBAN_COOKIE; if an IP field is unavailable, it is omitted.
E-Hentai
EH_IPB_MEMBER_ID: The value ofipb_member_idin the cookie header after logging in E-HentaiEH_IPB_PASS_HASH: The value ofipb_pass_hashin the cookie header after logging in E-HentaiEH_SK: The value ofskin the cookie header after logging in E-HentaiEH_STAR: The value ofstarin the cookie header if your account has stars. If this value is set, image limit allocation will links to the account rather than IP addressEH_IGNEOUS: The value ofigneousin the cookie header after logging in ExHentai. If this value is set, RSS will be generated from ExHentaiEH_IMG_PROXY: Cover proxy address. If this is set, the link to the cover image will be replaced with this value at the beginning. When using ExHentai, the cover image requires cookies to access it, so you can use this with a cookie-added proxy server to access the cover image without cookies in some readers.
Fantia
FANTIA_COOKIE: Thecookieafter login can be obtained by viewing the request header in the console, If not filled in will cause some posts that require login to read to get exceptions
Gitee
GITEE_ACCESS_TOKEN: Gitee 私人令牌
GitHub
GITHUB_ACCESS_TOKEN: GitHub Access Token
Google Fonts
GOOGLE_FONTS_API_KEY: API key
Instagram
INSTAGRAM_COOKIE: Your Instagram cookie, only thesessionidandds_user_idcookies are required. Optional for public profiles, required for stories, highlights, hashtags and private profiles.IG_COOKIEis still accepted as a fallback.
Iwara
IWARA_USERNAME: username of Iwara UserIWARA_PASSWORD: password of Iwara User
Last.fm
LASTFM_API_KEY: Last.fm API Key
LightNovel.us
SECURITY_KEY: security_key in the token,please remove %22,example{%22security_key%22:%223cXXXX%22},only need 3cXXXX
Email
EMAIL_CONFIG_{email}: Mail setting, replace{email}with the email account, replace@and.in email account with_, e.g.EMAIL_CONFIG_xxx_gmail_com. The value is in the format ofpassword=password&host=server&port=port, eg:Linux env:
EMAIL_CONFIG_xxx_qq_com="password=123456&host=imap.qq.com&port=993"docker env:
EMAIL_CONFIG_xxx_qq_com=password=123456&host=imap.qq.com&port=993, please do not include quotations',"Note: socks5h proxy is not supported due to the limit of email lib
ImapFlow
Mastodon
For user timeline
Apply API at https://mastodon.example/settings/applications (replace mastodon.example). Scopes read:search and read:statuses are needed.
MASTODON_API_HOST: API instance domain, only domain, nohttp://orhttps://protocol headerMASTODON_API_ACCESS_TOKEN: user access tokenMASTODON_API_ACCT_DOMAIN: acct domain for this instance, i.e. thedomainin the WebFinger URIusername@domain. It's usually the same asMASTODON_API_HOST.
Medium
Open the console, copy the cookie (in theory, only uid and sid are required)
MEDIUM_ARTICLE_COOKIE: Cookie used when requesting the full article, can access the full text of paid content when there is an active Member subscription.MEDIUM_COOKIE_{username}: Cookie of the user corresponding to the username, required for personalized recommendation related routes.
MiniFlux
MINIFLUX_INSTANCE: The instance used by the user, by default, is the official MiniFlux paid service addressMINIFLUX_TOKEN: User's API key, please log in to the instance used and go toSettings->API Key->Create a new API keyto obtain.
Netease Cloud Music Playlists
For playlists and song rankings
NCM_COOKIES: Cookies after logging into Netease Cloud Music, available viadocument.cookiein the browser console.
nhentai torrent
NHENTAI_USERNAME: nhentai username or emailNHENTAI_PASSWORD: nhentai password
Notion
NOTION_TOKEN: Notion Internal Integration Token, Refer to Notion Official Set Up Flow to create Token
pianyuan
PIANYUAN_COOKIE: 对应 cookie 中的py_loginauth, 例:PIANYUAN_COOKIE='py_loginauth=xxxxxxxxxx'
Pixabay
PIXABAY_KEY: Pixabay API key
pixiv
PIXIV_REFRESHTOKEN: Please refer to this article to get arefresh_tokenPIXIV_BYPASS_CDN: bypass Cloudflare bot check by directly accessing Pixiv source server, defaults to disable, settrueor1to enablePIXIV_BYPASS_HOSTNAME: Pixiv source server hostname or IP address, hostname will be resolved to IPv4 address viaPIXIV_BYPASS_DOH, defaults topublic-api.secure.pixiv.netPIXIV_BYPASS_DOH: DNS over HTTPS endpoint, it must be compatible with Cloudflare or Google DoH JSON schema, defaults tohttps://1.1.1.1/dns-queryPIXIV_IMG_PROXY: Used as a proxy for image addresses, as pixiv images have anti-theft, default tohttps://i.pixiv.re
pixiv fanbox
Get paid content
FANBOX_SESSION_ID: equals toFANBOXSESSIDin site cookies.
Saraba1st
用于获取帖子里的图片
SARABA1ST_COOKIE: 对应网页端的 Cookie。
Sci-Hub
For scientific journal routes
SCIHUB_HOST: The Sci-Hub mirror address that is accessible from your location, default tohttps://sci-hub.se.
Spotify
SPOTIFY_CLIENT_ID: Client ID of the applicationSPOTIFY_CLIENT_SECRET: Client secret of the application
For user data related routes
SPOTIFY_REFRESHTOKEN: The refresh token of the user from the Spotify application. You can obtain it through spotify-refresh-token by alecchendev.
TIP
Remember to check user-top-read and user-library-read in the scope for Personal Top Items and Personal Saved Tracks respectively.
Telegram
TELEGRAM_TOKEN: Telegram bot token for stickerpack feedsTELEGRAM_SESSION: for video, file streaming and some restricted channels, should create your telegram app viahttps://my.telegram.org/apps, getapi_idandapi_hashfrom there, then runnode ./lib/routes/telegram/scripts/get-telegram-session.mjsin RSSHub root directory to getTELEGRAM_SESSION
Twitter
It is recommended to use a non-important account, new accounts or logins from different regions may be restricted.
TWITTER_USERNAME: Twitter usernameTWITTER_PASSWORD: Twitter passwordTWITTER_PHONE_OR_EMAIL: Optional, Twitter phone or emailTWITTER_AUTHENTICATION_SECRET: Optional, Twitter Two-factor authentication -> Authentication app -> Secret part inotpauth://totp/Twitter:@_RSSHub?secret=xxxxxxxxxxxxxxxx&issuer=TwitterTWITTER_AUTH_TOKEN: Theauth_tokenCookie value from your own authorized X session. Required by/twitter/spaces/:username; developer API keys and third-party timeline providers do not supply this route's speaker status. Configure it on your own instance and refresh expired sessions.
/twitter/spaces/:username reports when the user hosts, co-hosts, or speaks in a live Space, including Spaces hosted by someone else. Listeners are excluded. Entries use the actual Space start time and a stable user/Space GUID; when no speaking session is found, the route emits a fixed status entry without a publication date. The route does not join or listen to the Space.
Wordpress
WORDPRESS_ALLOWED_DOMAINS: comma-separated exact hostnames permitted by the WordPress route whileALLOW_USER_SUPPLY_UNSAFE_DOMAINremains disabled, for examplewordpress.org,blog.example.com. Empty by default. Whitespace is trimmed and matching is case-insensitive. Use hostnames without a scheme, port, path or wildcard; list each subdomain explicitly. EnablingALLOW_USER_SUPPLY_UNSAFE_DOMAINinstead allows arbitrary WordPress hostnames.WORDPRESS_CDN: Proxy HTTP image link with HTTPS link. Consider using:url backbone https://imageproxy.pimg.tw/resize?url= akamai https://images.weserv.nl/?url= cloudflare https://pic1.xuehuaimg.com/proxy cloudflare https://cors.netnr.workers.dev cloudflare https://netnr-proxy.openode.io digitalocean
YouTube
- All routes:
YOUTUBE_KEY: YouTube API Key, support multiple keys, split them with,YOUTUBE_VIDEO_EMBED_URL: Base URL of the YouTube iframe embed player. Defaults tohttps://www.youtube-nocookie.com/embed/.- Extra requirements for subscriptions route:
YOUTUBE_CLIENT_ID: YouTube API OAuth 2.0 client IDYOUTUBE_CLIENT_SECRET: YouTube API OAuth 2.0 client secretYOUTUBE_REFRESH_TOKEN: YouTube API OAuth 2.0 refresh token. Check this gist for detailed instructions.
ZodGame
ZODGAME_COOKIE: Cookie of ZodGame User
北京大学
用于北大未名 BBS 全站十大
PKUBBS_COOKIE: BBS 注册用户登录后的 Cookie 值,获取方式:- 登录后打开论坛首页
- 打开控制台, 刷新
- 找到
https://bbs.pku.edu.cn/v2/home.php请求 - 找到请求头中的 Cookie
滴答清单
DIDA365_USERNAME: 滴答清单用户名DIDA365_PASSWORD: 滴答清单密码
Douyin
/douyin/live/:rid/:showTime? keeps its existing title by default. Set showTime to 1 or true to append the time RSSHub first detected the current live event, in UTC+8. This is an observation time, not the source's actual start time, and is not used as pubDate. It is cached by the event's real room ID for 30 days without extending its lifetime on reads. Clearing the cache or restarting an instance with memory caching resets the record; use Redis to retain it across restarts.
DOUYIN_COOKIE: The Cookie request header from your own signed-in Douyin web session. It is required for/douyin/likes/selfand/douyin/collection; for/douyin/likes/:uid, the liked list must be visible to the current account. The routes read only the first screen and use each video's original publication time, because Douyin does not provide the time it was liked or collected. Keep this configuration on an instance with access control. Refresh the Cookie when the session expires.To obtain it, sign in to Douyin, open the browser's Network panel, select the liked or collected videos tab, and copy the
Cookierequest header of the correspondingaweme/favoriteoraweme/listcollectionrequest. Do not put it in a subscription URL. The collection route covers collected videos; folders, music, series, and short dramas are outside its scope.
Xueqiu
/xueqiu/column/:id also uses the configured Cookie for both the profile and its timeline. Without it, the route tries an anonymous visitor session; columns that hide posts from that session require a signed-in account with access.
XUEQIU_COOKIES: The Cookie request header from your own signed-in Xueqiu browser session./xueqiu/user_stock/:idrequires it, and/xueqiu/snb/:iduses it when configured. The account must be able to view the requested watchlist or portfolio on the source website. Refresh expired sessions; inaccessible data produces an authorization error instead of a successful empty feed.
饭否
FANFOU_CONSUMER_KEY: 饭否 Consumer KeyFANFOU_CONSUMER_SECRET: 饭否 Consumer SecretFANFOU_USERNAME: 饭否登录用户名、邮箱、手机号FANFOU_PASSWORD: 饭否密码
和风天气
HEFENG_KEY:API key
米游社
MIHOYO_COOKIE:登录米游社后的 cookie,用于获取用户关注动态时间线。
南方周末
用于付费全文
INFZM_COOKIE: infzm 账户登陆后的 cookie,目前只需要passport_session=...即可获取全文
轻小说文库
WENKU8_COOKIE: 登陆轻小说文库后的 cookie
色花堂
SEHUATANG_COOKIE: 登陆色花堂后的 cookie 值。
微博
用于个人时间线路由
WEIBO_APP_KEY: 微博 App KeyWEIBO_APP_SECRET: 微博 App SecretWEIBO_REDIRECT_URL: Weibo OAuth callback URL, defaulting to<RSSHub request origin>/weibo/timeline/0. A custom callback must forward both OAuth query parameters,codeandstate, unchanged to<RSSHub URL>/weibo/timeline/0?code=<oauth-code>&state=<returned-state>.When
ACCESS_KEYis enabled, first open the desired timeline route with a valid RSSHubkeyor accesscodeto start authorization. RSSHub creates a one-timestatevalid for ten minutes and consumes it when the callback returns, then redirects to the final subscription URL with its route-specific access code. This requires an available memory or Redis cache; HTTP and KV cache backends do not support this protected callback flow. Start authorization again if the state expires or has already been used. The configuredWEIBO_REDIRECT_URLmust not contain RSSHubkeyor accesscodeparameters; preserve the OAuthcodeandstatereturned by Weibo instead.
用于自定义分组
WEIBO_COOKIES: 用户访问网页微博时所使用的 cookie, 获取方式:- 打开并登录 https://m.weibo.cn (确保打开页面为手机版,如果强制跳转电脑端可尝试使用可更改 UserAgent 的浏览器插件)
- 按下
F12打开控制台,切换至Network(网络)面板 - 在该网页切换至任意关注分组,并在面板打开最先捕获到的请求 (该情形下捕获到的请求路径应包含
/feed/group) - 查看该请求的
Headers(请求头), 找到Cookie字段并复制内容
小宇宙
需要 App 登陆后抓包获取相应数据。
XIAOYUZHOU_ID: 即数据包中的x-jike-device-id。XIAOYUZHOU_TOKEN: 即数据包中的x-jike-refresh-token。
新榜
NEWRANK_COOKIE: 登陆后的 COOKIE 值,其中 token 是必要的,其他可删除
喜马拉雅
XIMALAYA_TOKEN: 对应 cookie 中的1&_token,获取方式:- 登陆喜马拉雅网页版
- 打开控制台,刷新
- 查找名称为
1&_token的cookie,其内容即为XIMALAYA_TOKEN的值(即在cookie中查找1&_token=***;,并设置XIMALAYA_TOKEN = ***)
知乎
用于用户关注时间线
ZHIHU_COOKIES: 知乎登录后的 cookie 值。- 可以在知乎网页版的一些请求的请求头中找到,如
GET /moments请求头中的cookie值。
- 可以在知乎网页版的一些请求的请求头中找到,如
