mirror of
https://github.com/benbusby/whoogle-search.git
synced 2026-04-25 12:15:50 +03:00
[GH-ISSUE #1204] [QUESTION] when behind a reverse proxy, search "my ip" get container's internal ip instead of client's remote ip #722
Labels
No labels
Fixed (Pending PR Merge)
Stale
bug
enhancement
enhancement
good first issue
help wanted
keep-open
needs more info
pull-request
question
theme
unfortunate
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/whoogle-search#722
Loading…
Add table
Add a link
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?
Originally created by @paxprot on GitHub (Dec 12, 2024).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/1204
Hi, I'm using caddy and cloudflare to reverse proxy whoogle, my caddyfile is here:
When I search "my ip", I get the result of the internal container ip 172.20.0.3 instead of client's remote ip. I checked the logs in caddy, remote ip (both cloudflare and the real client's ip) should have been sent to whoogle
How can I get "my ip" return my client's real ip?
@paxprot commented on GitHub (Dec 19, 2024):
I have switched to another project, and I encountered the same issue, the solution is to add the ip returned by cf-connecting-ip in request header to whoogle, something like X-Real-IP or X-Forwarded-For, I haven't tested it on whoogle, but I think they should be the same. The config is here, I'll close the issue as resolved.