starred/proxyman-windows-linux
1
0
Fork 0
mirror of https://github.com/ProxymanApp/proxyman-windows-linux.git synced 2026-04-27 00:45:55 +03:00
Code Issues 541 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #234] [Bug] Can't switch listening address #232

New issue
Open
opened 2026-03-03 19:49:19 +03:00 by kerem · 12 comments
kerem commented 2026-03-03 19:49:19 +03:00
Owner
Copy link

Originally created by @lqzhgood on GitHub (May 15, 2023).
Original GitHub issue: https://github.com/ProxymanApp/proxyman-windows-linux/issues/234

Originally assigned to: @kics223w1 on GitHub.

Description

Can't switch listening address, alway to listening Docker getway ip address

Steps to Reproduce

  1. open proxyman

Current Behavior

auto listening ip address

Expected Behavior

can manually switch

Environment

  • App version: 1.7.0
  • Windows/Linux version: Windows
Originally created by @lqzhgood on GitHub (May 15, 2023). Original GitHub issue: https://github.com/ProxymanApp/proxyman-windows-linux/issues/234 Originally assigned to: @kics223w1 on GitHub. ## Description Can't switch listening address, alway to listening `Docker` getway ip address ## Steps to Reproduce 1. open `proxyman` ## Current Behavior auto listening ip address ## Expected Behavior can manually switch ## Environment - App version: 1.7.0 - Windows/Linux version: Windows
kerem commented 2026-03-03 19:49:20 +03:00
Author
Owner
Copy link

@NghiaTranUIT commented on GitHub (May 15, 2023):

@lqzhgood When Proxyman opens, it will listen on 0.0.0.0 at port 9090.

You can change the listening port in the Preference -> General Tab.

Not sure what do you mean to listen on Docker gateway IP?

<!-- gh-comment-id:1547094706 --> @NghiaTranUIT commented on GitHub (May 15, 2023): @lqzhgood When Proxyman opens, it will listen on 0.0.0.0 at port 9090. You can change the listening port in the Preference -> General Tab. Not sure what do you mean to listen on Docker gateway IP?
kerem commented 2026-03-03 19:49:20 +03:00
Author
Owner
Copy link

@lqzhgood commented on GitHub (May 15, 2023):

// ipconfig

vEthernet (Default Switch):              <--- docker geteway

   IPv4  . . . . . . . . . . . . : 172.25.224.1
   MASK  . . . . . . . . . . . . : 255.255.240.0
   Gateway. . . . . . . . . . . . . :

vEthernet (WSL):

   IPv4  . . . . . . . . . . . . : 172.20.96.1
   MASK  . . . . . . . . . . . . : 255.255.240.0
   Gateway. . . . . . . . . . . . . :

LAN:                                     <----  physical network

   IPv4  . . . . . . . . . . . . : 192.168.27.14
   MASK  . . . . . . . . . . . . : 255.255.255.0
   Gateway. . . . . . . . . . . . . : 192.168.27.1

ZeroTier One [b15644912e2e0ac6]:
 
   IPv4  . . . . . . . . . . . . : 192.168.50.212
   MASK  . . . . . . . . . . . . : 255.255.255.0
   Gateway. . . . . . . . . . . . . : 25.255.255.254

// proxyman screenshots
image

  1. I modified the proxy option to 192.168.27.14:8888 in Android wifi settings , is couldn't access.
  2. close proxyman to use Charles at 192.168.27.14:8888 is ok.
  3. So my previous guess was that the problem occurred because Proxyman was listening on 172.25.224.1 ( docker getway )
<!-- gh-comment-id:1547142110 --> @lqzhgood commented on GitHub (May 15, 2023): ```shell // ipconfig vEthernet (Default Switch): <--- docker geteway IPv4 . . . . . . . . . . . . : 172.25.224.1 MASK . . . . . . . . . . . . : 255.255.240.0 Gateway. . . . . . . . . . . . . : vEthernet (WSL): IPv4 . . . . . . . . . . . . : 172.20.96.1 MASK . . . . . . . . . . . . : 255.255.240.0 Gateway. . . . . . . . . . . . . : LAN: <---- physical network IPv4 . . . . . . . . . . . . : 192.168.27.14 MASK . . . . . . . . . . . . : 255.255.255.0 Gateway. . . . . . . . . . . . . : 192.168.27.1 ZeroTier One [b15644912e2e0ac6]: IPv4 . . . . . . . . . . . . : 192.168.50.212 MASK . . . . . . . . . . . . : 255.255.255.0 Gateway. . . . . . . . . . . . . : 25.255.255.254 ``` // proxyman screenshots ![image](https://github.com/ProxymanApp/proxyman-windows-linux/assets/9134671/9757c2d4-b646-42ee-a75b-ae6d57528a29) 1. I modified the proxy option to `192.168.27.14:8888` in Android wifi settings , is couldn't access. 2. close `proxyman` to use `Charles` at `192.168.27.14:8888` is ok. 3. So my previous guess was that the problem occurred because `Proxyman` was listening on 172.25.224.1 ( docker getway )
kerem commented 2026-03-03 19:49:20 +03:00
Author
Owner
Copy link

@lqzhgood commented on GitHub (May 15, 2023):

  • I uninstall proxyman is not ok
  • i delete C:\Users\user\AppData\Roaming\Proxyman\map-local and reinstall is ok

I don't know what the problem

<!-- gh-comment-id:1547166386 --> @lqzhgood commented on GitHub (May 15, 2023): - I uninstall `proxyman` is not ok - i delete `C:\Users\user\AppData\Roaming\Proxyman\map-local` and reinstall is ok I don't know what the problem
kerem commented 2026-03-03 19:49:20 +03:00
Author
Owner
Copy link

@NghiaTranUIT commented on GitHub (May 15, 2023):

You can simply do Factory Reset in the Help menu -> Advance.

From what you've provided, it seems that Proxyman listens on a wrong IP. It should listen on LAN instead of vEthernet.

I will open this ticket and investigate it 👍

<!-- gh-comment-id:1547167479 --> @NghiaTranUIT commented on GitHub (May 15, 2023): You can simply do Factory Reset in the Help menu -> Advance. From what you've provided, it seems that Proxyman listens on a wrong IP. It should listen on LAN instead of vEthernet. I will open this ticket and investigate it 👍
kerem commented 2026-03-03 19:49:21 +03:00
Author
Owner
Copy link

@jlorber commented on GitHub (May 15, 2023):

I experience this same issue when using a VPN. There should be an option to bind Proxyman to the correct IP address.

<!-- gh-comment-id:1547432613 --> @jlorber commented on GitHub (May 15, 2023): I experience this same issue when using a VPN. There should be an option to bind Proxyman to the correct IP address.
kerem commented 2026-03-03 19:49:21 +03:00
Author
Owner
Copy link

@jlorber commented on GitHub (Jun 28, 2023):

Can we reopen this issue?

<!-- gh-comment-id:1611235592 --> @jlorber commented on GitHub (Jun 28, 2023): Can we reopen this issue?
kerem commented 2026-03-03 19:49:21 +03:00
Author
Owner
Copy link

@kics223w1 commented on GitHub (Jun 28, 2023):

I've moved it to the To-do list

<!-- gh-comment-id:1611240563 --> @kics223w1 commented on GitHub (Jun 28, 2023): I've moved it to the To-do list
kerem commented 2026-03-03 19:49:21 +03:00
Author
Owner
Copy link

@Zhen-Bo commented on GitHub (Dec 31, 2024):

I am experiencing the same issue.
Proxyman keeps using my vEthernet (WSL - Hyper-V Firewall) as the proxy IP.
This issue persists even after performing a factory reset.

Using proxyman 2.19.0

<!-- gh-comment-id:2566653552 --> @Zhen-Bo commented on GitHub (Dec 31, 2024): I am experiencing the same issue. Proxyman keeps using my vEthernet (WSL - Hyper-V Firewall) as the proxy IP. This issue persists even after performing a factory reset. Using proxyman 2.19.0
kerem commented 2026-03-03 19:49:21 +03:00
Author
Owner
Copy link

@PhilTdr commented on GitHub (Feb 28, 2025):

Same issue here.

I am currently testing the switch from Charles to Proxyman and Charls automatically listens to all IP addresses of all network adapters. Proxyman always seems to automatically listen to the IP of the VPN network adapter and not (additionally) to the local IP of the ethernet or wifi adapter.

I think Proxyman should at least have the possibility to listen to all IP addresses of all network adapters automatically.

<!-- gh-comment-id:2690263149 --> @PhilTdr commented on GitHub (Feb 28, 2025): Same issue here. I am currently testing the switch from Charles to Proxyman and Charls automatically listens to all IP addresses of all network adapters. Proxyman always seems to automatically listen to the IP of the VPN network adapter and not (additionally) to the local IP of the ethernet or wifi adapter. I think Proxyman should at least have the possibility to listen to all IP addresses of all network adapters automatically.
kerem commented 2026-03-03 19:49:21 +03:00
Author
Owner
Copy link

@NghiaTranUIT commented on GitHub (Feb 28, 2025):

@PhilTdr Proxyman listens on 0.0.0.0 and 127.0.0.1 at port 9090.

If you mean the IP address which is displayed on the menu bar -> It could be a bug. Let's me find a solution to fix it 👍

<!-- gh-comment-id:2690320511 --> @NghiaTranUIT commented on GitHub (Feb 28, 2025): @PhilTdr Proxyman listens on 0.0.0.0 and 127.0.0.1 at port 9090. If you mean the IP address which is displayed on the menu bar -> It could be a bug. Let's me find a solution to fix it 👍
kerem commented 2026-03-03 19:49:21 +03:00
Author
Owner
Copy link

@NghiaTranUIT commented on GitHub (Feb 28, 2025):

I'm working on the fix @PhilTdr 👍

<!-- gh-comment-id:2690384134 --> @NghiaTranUIT commented on GitHub (Feb 28, 2025): I'm working on the fix @PhilTdr 👍
kerem commented 2026-03-03 19:49:21 +03:00
Author
Owner
Copy link

@PhilTdr commented on GitHub (Feb 28, 2025):

@PhilTdr Proxyman listens on 0.0.0.0 and 127.0.0.1 at port 9090.

If you mean the IP address which is displayed on the menu bar -> It could be a bug. Let's me find a solution to fix it 👍

It wasn't just a visual problem.
I have Charls (port 8888) and Proxyman (port 9090) running and with my smartphone no traffic came through Proxyman but through Charls with the same configuration except the port.

I have now tried closing the VPN client once. After restarting Proxyman, the correct local IP was now displayed and the smartphone was able to connect to Proxyman.

I then started the VPN client again and reconnected and restarted Proxyman. Proxyman displayed the VPN IP again, but I was still able to connect with the smartphone. Strangely enough, it is now only a visual thing and restarting the VPN client has solved the problem. Strangely enough, this was not a problem for Charls.

<!-- gh-comment-id:2690476086 --> @PhilTdr commented on GitHub (Feb 28, 2025): > [@PhilTdr](https://github.com/PhilTdr) Proxyman listens on 0.0.0.0 and 127.0.0.1 at port 9090. > > If you mean the IP address which is displayed on the menu bar -> It could be a bug. Let's me find a solution to fix it 👍 It wasn't just a visual problem. I have Charls (port 8888) and Proxyman (port 9090) running and with my smartphone no traffic came through Proxyman but through Charls with the same configuration except the port. I have now tried closing the VPN client once. After restarting Proxyman, the correct local IP was now displayed and the smartphone was able to connect to Proxyman. I then started the VPN client again and reconnected and restarted Proxyman. Proxyman displayed the VPN IP again, but I was still able to connect with the smartphone. Strangely enough, it is now only a visual thing and restarting the VPN client has solved the problem. Strangely enough, this was not a problem for Charls.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
feat/new-version
3.12.0
3.11.0
3.10.0
3.4.0
3.5.0
3.6.0
3.7.0
3.8.0
3.9.0
3.3.0
2.25.0
2.24.0
3.2.0
3.0.0
3.1.0
2.26.0
2.27.0
2.23.0
2.22.0
2.21.0
2.20.0
2.19.0
2.18.0
2.17.0
2.16.0
2.15.0
2.14.0
2.13.0
2.12.0
2.11.1
2.11.0
2.10.0
2.9.0
2.8.0
2.7.0
2.6.0
2.5.0
2.4.0
2.3.0
1.9.2
2.0.0
1.9.1
1.8.1
1.9.0
1.8.0
1.7.0
1.6.0
1.5.0
1.4.0
1.3.0
1.2.0
1.1.0
1.0.0
0.10.0
0.9.0
0.8.0
0.6.0
0.5.0
0.4.2
0.4.1
0.4.0
0.3.0
0.1.1
0.2.0
0.1.0
Labels
Clear labels   
Linux

   
bug

   
enhancement

   
enhancement

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
✅ Done
No labels
Linux
bug
enhancement
enhancement
pull-request
question
✅ Done
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
starred/proxyman-windows-linux#232
No description provided.