Skip to content

Conversation

@fank
Copy link
Member

@fank fank commented Feb 2, 2026

Summary

  • Rename config file from ocap-recorder.cfg.json to ocap_recorder.cfg.json to match DLL naming convention
  • The code already expects underscores but docs/example used dashes, causing config not to load
  • Add http:// scheme to serverUrl examples (required by Go http client)

Root Cause

The 403 error on mission upload was caused by the config file not being found:

  • Code looks for: ocap_recorder.cfg.json (underscores)
  • User had: ocap-recorder.cfg.json (dashes)
  • Result: defaults used, including empty apiKey → 403 Forbidden

Action Required

Users need to rename their config file:

mv ocap-recorder.cfg.json ocap_recorder.cfg.json

Test plan

  • Verify config loading with correct filename
  • Test mission upload with matching secrets

Rename config file from `ocap-recorder.cfg.json` to `ocap_recorder.cfg.json`
to match the DLL naming convention (`ocap_recorder_x64.dll`).

The code in config.go already expects `ocap_recorder.cfg.json` but the
example file and documentation used dashes, causing the config to not
be loaded (falling back to defaults with empty API key).

Changes:
- Rename example config file to use underscores
- Update .gitignore, CLAUDE.md, README.md references
- Add http:// scheme to serverUrl in examples (required by Go http client)
@fank fank merged commit b000af7 into main Feb 2, 2026
3 checks passed
@fank fank deleted the fix/config-filename-consistency branch February 2, 2026 14:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants