Skip to content

Hey, I'm getting a 404 (Request failed) error on FreeBuff #1425

Description

@fcuckthenorm

What happened

Hey, I'm getting a 404 (Request failed) error on FreeBuff (the free codeing website online) when my custom chatbot tries to perform a search. Any idea what's causing this?"

Steps to reproduce

Image

Where does this happen?

CLI (terminal client)

Operating system

Linux

Version

freebuff --version

Model

freebuff --version

Logs or screenshots

404 (Request failed) error

Activity

  1. added
    area:cliThe Codebuff/Freebuff terminal client
    bot:triagedClassified by the community triage bot
    needs-infoBlocked on the reporter for version, OS, logs, or a repro
    on Sep 24, 2026
  2. roshandhiman commented on Sep 29, 2026

    @roshandhiman

    Hi @fcuckthenorm 👋 — thanks for the detailed report!

    Likely root cause: The 404 (Request Failed) error during search in the CLI almost always occurs when the request is sent without a valid auth token, or when the CLI version being used has a stale API endpoint URL.

    A few things to try / confirm:

    1. Are you logged in? Run:

      freebuff login

      Then retry the search. The CLI sends an authToken with every API request; without it the backend returns 404.

    2. What is your exact CLI version? Please paste the full output of:

      freebuff --version

      (The issue template shows freebuff --version literally — we need the actual version string.)

    3. Is this a custom chatbot integration? If you are calling the freebuff CLI programmatically from a chatbot without going through the normal login flow, your process will not have a valid session token, causing the API endpoint to return 404 instead of 401 (the backend treats unauthenticated requests to certain routes as "not found" for security reasons).

    Workaround while we investigate: Export your auth token and pass it via environment variable:

    export FREEBUFF_AUTH_TOKEN="$(cat ~/.freebuff/token)"

    I have opened a PR (#1455) that improves the error message so it clearly says "Authentication required — run freebuff login" instead of the generic 404, making this much easier to diagnose in the future.

    Fixes: #1425

  3. added and removed
    needs-infoBlocked on the reporter for version, OS, logs, or a repro
    on Sep 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:cliThe Codebuff/Freebuff terminal clientbot:triagedClassified by the community triage bottype:bugA defect in the code with a reproducible failuretype:questionA usage question

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions