coilyco-bridge/sirens-discord-ops
1
0
Fork 0
Code Issues 8 Pull requests Projects Releases Packages Wiki Activity Actions

sirens-discord-ops.service: unknown coily flag -name + Discord auth header rejected #3

New issue
Open
opened 2026-05-23 20:55:35 +00:00 by coilysiren · 0 comments
coilysiren commented 2026-05-23 20:55:35 +00:00
Owner
Copy link

Originally filed by @coilysiren on 2026-05-19T02:52:22Z - https://github.com/coilysiren/sirens-discord-ops/issues/28

Symptom

sirens-discord-ops.service on kai-server crashloops post-reboot 2026-05-18, hits restart limit:

coily: flag provided but not defined: -name
...
discord open: Get "https://discord.com/api/v9/gateway": net/http: invalid header field value for "Authorization"
systemd[1]: sirens-discord-ops.service: Start request repeated too quickly.

Two distinct failures fused into the crashloop:

  1. Some call site is passing -name to coily, but coily no longer accepts that flag. Either a stale invocation in this repo or a coily CLI rename to chase.
  2. The Discord token used for the gateway auth header has a value that violates HTTP header rules (likely an embedded newline or stray whitespace from however it's loaded out of SSM / env). net/http: invalid header field value is the giveaway.

Next

  • Grep this repo for -name and update to the current coily flag.
  • Audit the token-loading path: trim, reject if it contains \r\n or control chars before constructing the auth header.
_Originally filed by @coilysiren on 2026-05-19T02:52:22Z - [https://github.com/coilysiren/sirens-discord-ops/issues/28](https://github.com/coilysiren/sirens-discord-ops/issues/28)_ **Symptom** `sirens-discord-ops.service` on kai-server crashloops post-reboot 2026-05-18, hits restart limit: ``` coily: flag provided but not defined: -name ... discord open: Get "https://discord.com/api/v9/gateway": net/http: invalid header field value for "Authorization" systemd[1]: sirens-discord-ops.service: Start request repeated too quickly. ``` Two distinct failures fused into the crashloop: 1. Some call site is passing `-name` to coily, but coily no longer accepts that flag. Either a stale invocation in this repo or a coily CLI rename to chase. 2. The Discord token used for the gateway auth header has a value that violates HTTP header rules (likely an embedded newline or stray whitespace from however it's loaded out of SSM / env). `net/http: invalid header field value` is the giveaway. **Next** * Grep this repo for `-name` and update to the current coily flag. * Audit the token-loading path: trim, reject if it contains `\r\n` or control chars before constructing the auth header.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-bridge/sirens-discord-ops#3
No description provided.