Helium+ guides: correct the RadSecProxy archive filename - #2080
Open
odolan-rgb wants to merge 1 commit into
Open
Helium+ guides: correct the RadSecProxy archive filename#2080odolan-rgb wants to merge 1 commit into
odolan-rgb wants to merge 1 commit into
Conversation
Deploying heliumdocs with
|
| Latest commit: |
6323a5e
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://2aed66d9.heliumdocs.pages.dev |
| Branch Preview URL: | https://fix-radsec-proxy-repo-name.heliumdocs.pages.dev |
The guides referenced `Helium_RadSec_Docker.tar.gz`, which isn't published anywhere. Downloading the archive from novalabsxyz/radsec-proxy gives `radsec-proxy-main.tar.gz` (GitHub names it after the repo and branch), so use that name instead. The un-tar step and everything after it are unchanged. Also corrects `Radsecproxy.conf` to `radsecproxy.conf` in the file lists, to match the file the repo actually ships. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
odolan-rgb
force-pushed
the
fix/radsec-proxy-repo-name
branch
from
August 6, 2026 23:24
cb2aad8 to
6323a5e
Compare
odolan-rgb
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Eight Helium+ vendor guides tell operators to un-tar
Helium_RadSec_Docker.tar.gz. That filename isn't published anywhere, so there's nothing to download.Raised in #deployment-support — flagged in Dec 2025, still live.
Fix
Just the filename. Downloading the archive from
novalabsxyz/radsec-proxygivesradsec-proxy-main.tar.gz(GitHub names it after the repo and branch), so the guides now say that:Everything else is untouched — same un-tar step, same file list, same certificate and
docker compose up -dsteps, same prerequisites.Also corrects
Radsecproxy.conf→radsecproxy.confin the file lists, since that's what the repo actually ships and the capitalized spelling breaks on a case-sensitive filesystem.Guides updated
Aruba · Cambium cnMaestro · Cisco WLC 5520 · Cisco WLC 9800 · Extreme · Fortinet · Meraki · MikroTik
Not fixed here
The radsec-proxy README has the same stale reference, spelled
Helium_RadSec_Docker.tag.gz(note.tag.gz— a second typo). novalabsxyz/radsec-proxy#5 has been open since 2025-12-19 and would fix it. Different repo, so out of scope here.Verification
rg 'Helium_RadSec_Docker|Radsecproxy\.conf'overdocs/→ no matchescontent-disposition: attachment; filename=radsec-proxy-main.tar.gz🤖 Generated with Claude Code