hermes - 💡(How to fix) Fix [Bug]: Broken relative link in Docker docs to API server page [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#14532Fetched 2026-04-24 06:16:42
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×3commented ×1

Error Message

Additional Logs / Traceback (optional)

Root Cause

Root Cause Analysis (optional)

The link target appears stale after docs reorganization:

  • Current broken reference: website/docs/user-guide/docker.md./api-server.md
  • Existing target page: website/docs/user-guide/features/api-server.md

Fix Action

Fix / Workaround

Proposed Fix (optional)

Patch website/docs/user-guide/docker.md line with:

  • from: ./api-server.md
  • to: ./features/api-server.md
RAW_BUFFERClick to expand / collapse

Bug Description

The Docker user guide links to a non-existent relative page for the API server docs.

In website/docs/user-guide/docker.md, the sentence:

Port 8642 exposes the gateway's OpenAI-compatible API server and health endpoint.

uses ./api-server.md, but that file does not exist in website/docs/user-guide/.

The actual page currently lives at:

  • website/docs/user-guide/features/api-server.md

This causes a dead link in the rendered docs from a high-traffic setup page.

Steps to Reproduce

  1. Open website/docs/user-guide/docker.md.
  2. Locate the link target ./api-server.md in the “Running in gateway mode” section.
  3. Verify file existence under website/docs/user-guide/.
  4. Observe that api-server.md is missing there.
  5. Check website/docs/user-guide/features/ and confirm api-server.md exists there.

Expected Behavior

The Docker docs should link to a valid API server documentation page so readers can navigate directly from Docker setup to API server usage details.

Actual Behavior

The current relative link points to a missing file (./api-server.md), resulting in a broken/dead docs link.

Affected Component

  • Setup / Installation
  • Other (documentation site content/navigation)

Messaging Platform (if gateway-related)

  • N/A (CLI only)

Debug Report

N/A — docs-only static content issue; no runtime environment or logs required.

Operating System

N/A (docs content issue, reproducible by repository inspection)

Python Version

N/A

Hermes Version

N/A

Additional Logs / Traceback (optional)

None.

Root Cause Analysis (optional)

The link target appears stale after docs reorganization:

  • Current broken reference: website/docs/user-guide/docker.md./api-server.md
  • Existing target page: website/docs/user-guide/features/api-server.md

Likely fix options:

  1. Update the link in docker.md to ./features/api-server.md (or site-absolute equivalent).
  2. Optionally add docs-link checks in CI (if not already enforced for this path) to catch future regressions.

Proposed Fix (optional)

Patch website/docs/user-guide/docker.md line with:

  • from: ./api-server.md
  • to: ./features/api-server.md

Optional hardening: enforce dead-link validation for docs pages in CI if this path is currently skipped.

Are you willing to submit a PR for this?

Yes — happy to open a tiny docs PR if maintainers want.

extent analysis

TL;DR

Update the link in website/docs/user-guide/docker.md to point to the correct location of the API server documentation, ./features/api-server.md.

Guidance

  • Verify the file structure and location of api-server.md to ensure it matches the expected path.
  • Update the link in docker.md to use the correct relative path, ./features/api-server.md, to fix the broken link.
  • Consider adding dead-link validation in CI to catch similar issues in the future and prevent regressions.
  • Review the documentation for any other potential stale links that may have been affected by the reorganization.

Example

The corrected link in website/docs/user-guide/docker.md would be:

Port 8642 exposes the gateway's [OpenAI-compatible API server](./features/api-server.md) and health endpoint.

Notes

This fix assumes that the api-server.md file is correctly located at website/docs/user-guide/features/api-server.md and that updating the link in docker.md will resolve the issue.

Recommendation

Apply the workaround by updating the link in docker.md to point to the correct location of the API server documentation, as this is a straightforward fix that can be verified and tested easily.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING