Log the real client IP for requests proxied through pi4 #58
Labels
No labels
automerge
bug
dependencies
duplicate
help wanted
invalid
lang
rust
migrations
opencode
question
security
type
documentation
type
enhancement
type
maintenance
type
refactor
vulnerability
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Personal/nixos-configuration#58
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
nidaros nginx logs every proxied request with pi4's LAN address (192.168.10.188), so external clients cannot be attributed. This made triaging the 2026-11-09 callback burst much harder than necessary.
Context
X-Forwarded-ForthroughrecommendedProxySettings.combinedlog format, which omits the header./var/log/nginx/access.log), sojournalctl -u nginxshows no request lines.Scope
$http_x_forwarded_forand apply it to proxied virtual hosts (the kitchenowl vhost is generated by the flake module, so it needs anaccessLogoverride from this repository).set_real_ip_fromfor pi4 so$remote_addris the real client.Acceptance criteria