DIYgod/RSSHub · error · ConfigNotFoundError

Skeb followings RSS is disabled due to the lack of relevant

Error message

Skeb followings RSS is disabled due to the lack of relevant config

What it means

Same gate as following-creators, applied to the following-works route: requires `config.skeb.bearerToken` to call the Skeb API for the latest works from a user's followings. Throws before `getFollowingsItems(username, 'following_works')`.

Source

Thrown at lib/routes/skeb/following-works.ts:44

    },
    name: 'Following Works',
    maintainers: ['SnowAgar25'],
    handler,
    radar: [
        {
            title: 'Following Works',
            source: ['skeb.jp/:username'],
            target: '/following_works/:username',
        },
    ],
    description: "Get the latest works for the specified user's followings on Skeb.",
};

async function handler(ctx): Promise<Data> {
    const username = ctx.req.param('username');

    if (!config.skeb || !config.skeb.bearerToken) {
        throw new ConfigNotFoundError('Skeb followings RSS is disabled due to the lack of relevant config');
    }

    const items = await getFollowingsItems(username, 'following_works');

    return {
        title: `Skeb - ${username} - フォロー中のクリエイターの新着作品`,
        link: `https://skeb.jp/${username}`,
        item: items as DataItem[],
    };
}

View on GitHub (pinned to bed535e087)

Solutions

Set `SKEB_BEARER_TOKEN` and restart the instance.
Confirm the token still works by calling the Skeb API directly with curl.
Re-issue the token periodically.

Example fix

// before
# SKEB_BEARER_TOKEN unset

// after
SKEB_BEARER_TOKEN=<your bearer token>

Defensive patterns

Strategy: validation

Validate before calling

if (!config.skeb?.bearerToken) {
    return ctx.body('Skeb route requires SKEB_BEARER_TOKEN.', 503);
}

Type guard

const hasSkebToken = (c: typeof config): boolean => Boolean(c.skeb?.bearerToken);

Prevention

Share one Skeb config check across all three skeb routes via a helper.
Document token acquisition steps in the route description.
Monitor for 401 responses that indicate token expiry.

When it happens

Trigger: A request to /following_works/:username on an instance where the Skeb bearer token is unset.

Common situations: Default deploy without Skeb env; token expired and removed; public instance that does not share Skeb credentials.

Related errors

AI-assisted analysis of DIYgod/RSSHub@bed535e087 (2026-08-12). Data as JSON: /api/errors/2bb0691b32f40a53. Report an issue: GitHub.