Skip to content

LLM-741: memory-api listens on 127.0.0.1 only - #377

Merged
jeffdafoe merged 2 commits into
mainfrom
LLM-741-listen-loopback
Oct 12, 2026
Merged

jeffdafoe merged 2 commits into
mainfrom
LLM-741-listen-loopback

Conversation

@jeffdafoe

Copy link
Copy Markdown
Owner

LLM-741

The API listened on every interface (*:3100); only UFW kept the port off the internet. The connector login rate limit (LLM-733) trusts the X-Forwarded-For hop nginx appends, so a request that reached :3100 directly could forge its client address.

  • server.js binds to MEMORY_API_HOST, default 127.0.0.1.
  • New Ansible var memory_api_host: 127.0.0.1 (group_vars), written to /etc/memory-api/env. The env task already notifies Restart memory-api.

Checked on the VPS: all live connections to :3100 come from 127.0.0.1 (nginx, salem engine); no config uses localhost:3100 or [::1]:3100.

code_review: no blocking issue; renamed HOST → MEMORY_API_HOST on its advice.

Agent: Home

🤖 Generated with Claude Code

jeffdafoe and others added 2 commits October 12, 2026 10:40
The API listened on every interface (*:3100); only UFW kept the port
off the internet. The connector login rate limit trusts the
X-Forwarded-For hop nginx appends, so a direct request could forge its
client address. Bind to HOST (default 127.0.0.1), set from the new
memory_api_host Ansible var through the env file.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jeffdafoe
jeffdafoe merged commit bda0969 into main Oct 12, 2026
9 checks passed
@jeffdafoe
jeffdafoe deleted the LLM-741-listen-loopback branch October 12, 2026 14:48
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.

1 participant