[GH-ISSUE #522] Cant' Hide Real Requester Client IP On Reverse Proxy #425

Open
opened 2026-02-27 23:16:51 +03:00 by kerem · 8 comments
Owner

Originally created by @hangadelen-qop on GitHub (Jan 24, 2023).
Original GitHub issue: https://github.com/snail007/goproxy/issues/522

I have tried TCP and HTTP Reverse proxy and upstream configs on commercial licence. But on main server, we can still see requester user real IP details. I have also tried outgoing ip configs for both tcp and http.
Client -> Proxy VPS -> Main Server
We have to show VPS ip address details on main server for requester client.
Do i have to add secondary reverse proxy vps or miss something maybe?

Originally created by @hangadelen-qop on GitHub (Jan 24, 2023). Original GitHub issue: https://github.com/snail007/goproxy/issues/522 I have tried TCP and HTTP Reverse proxy and upstream configs on commercial licence. But on main server, we can still see requester user real IP details. I have also tried outgoing ip configs for both tcp and http. Client -> Proxy VPS -> Main Server We have to show VPS ip address details on main server for requester client. Do i have to add secondary reverse proxy vps or miss something maybe?
Author
Owner

@hangadelen-qop commented on GitHub (Jan 24, 2023):

Outgoing ip configs -> --bind-listen

<!-- gh-comment-id:1401850626 --> @hangadelen-qop commented on GitHub (Jan 24, 2023): Outgoing ip configs -> --bind-listen
Author
Owner

@hangadelen-qop commented on GitHub (Jan 24, 2023):

Or which config details do we have to use

<!-- gh-comment-id:1401871811 --> @hangadelen-qop commented on GitHub (Jan 24, 2023): Or which config details do we have to use
Author
Owner

@snail007 commented on GitHub (Jan 24, 2023):

fill the issue template

<!-- gh-comment-id:1401914714 --> @snail007 commented on GitHub (Jan 24, 2023): fill the issue template
Author
Owner

@hangadelen-qop commented on GitHub (Jan 24, 2023):

Let me fill

<!-- gh-comment-id:1401920752 --> @hangadelen-qop commented on GitHub (Jan 24, 2023): Let me fill
Author
Owner

@hangadelen-qop commented on GitHub (Jan 24, 2023):

Expected Behavior

Proxy VPS Server IP Must Be Shown On Reverse Proxy / Upstream

Current Behavior

Still Showing Real User IP On Main Server

Possible Solution

Maybe I Miss Something From Configs. Dont Know.

Steps to Reproduce

  1. Installed goproxy commercial with following command
  2. proxy http -t tcp -p :PORT -T tls -P "MAIN-SERVER:MAIN-PORT" -C proxy.crt -K proxy.key --bind-listen
  3. also tried tcp upstream and outgoing ip with -B and also with flexible option too

Context (Environment)

  1. proxy version is : commercial_12.6
  2. full command is : proxy http -t tcp -p :PORT -T tls -P "MAIN-SERVER:MAIN-PORT" -C proxy.crt -K proxy.key --bind-listen
  3. proxy tcp -p ":PORT" -T tcp -P" MAİN-SERVER:MAIN-PORT" -B
  4. system is : linux ubuntu 20.04
  5. full log is: no error logs.

Detailed Description

I have tried TCP and HTTP Reverse proxy and upstream configs on commercial licence. But on main server, we can still see requester user real IP details. I have also tried outgoing ip configs for both tcp and http.
Client -> Proxy VPS -> Main Server
We have to show VPS ip address details on main server for requester client.
Do i have to add secondary reverse proxy vps or miss something maybe?

Possible Implementation

<!-- gh-comment-id:1402325181 --> @hangadelen-qop commented on GitHub (Jan 24, 2023): <!--- Provide a general summary of the issue in the Title above --> ## Expected Behavior <!--- Tell us what should happen --> Proxy VPS Server IP Must Be Shown On Reverse Proxy / Upstream ## Current Behavior <!--- Tell us what happens instead of the expected behavior --> Still Showing Real User IP On Main Server ## Possible Solution <!--- Not obligatory, but suggest a fix/reason for the bug, --> Maybe I Miss Something From Configs. Dont Know. ## Steps to Reproduce <!--- Provide a link to a live example, or an unambiguous set of steps to --> <!--- reproduce this bug. Include code to reproduce, if relevant --> 1. Installed goproxy commercial with following command 1. proxy http -t tcp -p :PORT -T tls -P "MAIN-SERVER:MAIN-PORT" -C proxy.crt -K proxy.key --bind-listen 1. also tried tcp upstream and outgoing ip with -B and also with flexible option too ## Context (Environment) <!--- How has this issue affected you? What are you trying to accomplish? --> <!--- Providing context helps us come up with a solution that is most useful in the real world --> 1. proxy version is : commercial_12.6 1. full command is : proxy http -t tcp -p :PORT -T tls -P "MAIN-SERVER:MAIN-PORT" -C proxy.crt -K proxy.key --bind-listen 2. proxy tcp -p ":PORT" -T tcp -P" MAİN-SERVER:MAIN-PORT" -B 1. system is : linux ubuntu 20.04 1. full log is: no error logs. <!--- Provide a general summary of the issue in the Title above --> ## Detailed Description <!--- Provide a detailed description of the change or addition you are proposing --> I have tried TCP and HTTP Reverse proxy and upstream configs on commercial licence. But on main server, we can still see requester user real IP details. I have also tried outgoing ip configs for both tcp and http. Client -> Proxy VPS -> Main Server We have to show VPS ip address details on main server for requester client. Do i have to add secondary reverse proxy vps or miss something maybe? ## Possible Implementation <!--- Not obligatory, but suggest an idea for implementing addition or change -->
Author
Owner

@hangadelen-qop commented on GitHub (Jan 25, 2023):

Hey sir i filled the template on same issue link

24 Oca 2023 Sal 16:03 tarihinde snail007 @.***> şunu
yazdı:

fill the issue template


Reply to this email directly, view it on GitHub
https://github.com/snail007/goproxy/issues/522#issuecomment-1401914714,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEJDEFSL57A4ZBPMVMSXRGTWT7HKTANCNFSM6AAAAAAUFAORTI
.
You are receiving this because you authored the thread.Message ID:
@.***>

<!-- gh-comment-id:1403305558 --> @hangadelen-qop commented on GitHub (Jan 25, 2023): Hey sir i filled the template on same issue link 24 Oca 2023 Sal 16:03 tarihinde snail007 ***@***.***> şunu yazdı: > fill the issue template > > — > Reply to this email directly, view it on GitHub > <https://github.com/snail007/goproxy/issues/522#issuecomment-1401914714>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AEJDEFSL57A4ZBPMVMSXRGTWT7HKTANCNFSM6AAAAAAUFAORTI> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
Author
Owner

@snail007 commented on GitHub (Jan 26, 2023):

what is your "main server", it is impossiable to get your client ip by "tcp remote address".

<!-- gh-comment-id:1404589240 --> @snail007 commented on GitHub (Jan 26, 2023): what is your "main server", it is impossiable to get your client ip by "tcp remote address".
Author
Owner

@hangadelen-qop commented on GitHub (Jan 26, 2023):

My command is true ? Or missing something btw ?

<!-- gh-comment-id:1404849864 --> @hangadelen-qop commented on GitHub (Jan 26, 2023): My command is true ? Or missing something btw ?
Sign in to join this conversation.
No milestone
No project
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
starred/goproxy#425
No description provided.