[GH-ISSUE #2012] Configuration to disable system proxy #1599

New issue

Closed

opened 2026-05-05 13:01:11 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 13:01:11 -06:00

Owner

Originally created by @zssng on GitHub (Sep 28, 2020).
Original GitHub issue: https://github.com/fatedier/frp/issues/2012

Issue is only used for submiting bug report and documents typo. If there are same issues or answers can be found in documents, we will close it directly.

Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST

What version of frp are you using (./frpc -v or ./frps -v)?
0.34.0

What operating system and processor architecture are you using (go env)?
Windows 10 2004

Configures you used:
[RDP3]
type = tcp
local_ip = 127.0.0.1
local_port = 3389
remote_port = 7002

Steps to reproduce the issue:

start frpc before login
frpc use system proxy but system proxy not start until user logged in

Describe the results you received:
2020/09/28 11:09:43 [W] [service.go:102] login to server failed: dial tcp 127.0.0.1:57890: connectex: No connection coul
d be made because the target machine actively refused it.
dial tcp 127.0.0.1:57890: connectex: No connection could be made because the target machine actively refused it.

Describe the results you expected:
Is there any configuration can ignore system proxy setting ?

Additional information you deem important (e.g. issue happens only occasionally):

Can you point out what caused this issue (optional)

Originally created by @zssng on GitHub (Sep 28, 2020). Original GitHub issue: https://github.com/fatedier/frp/issues/2012 Issue is only used for submiting bug report and documents typo. If there are same issues or answers can be found in documents, we will close it directly. Use the commands below to provide key information from your environment: You do NOT have to include this information if this is a FEATURE REQUEST **What version of frp are you using (./frpc -v or ./frps -v)?** 0.34.0 **What operating system and processor architecture are you using (`go env`)?** Windows 10 2004 **Configures you used:** [RDP3] type = tcp local_ip = 127.0.0.1 local_port = 3389 remote_port = 7002 **Steps to reproduce the issue:** 1. start frpc before login 2. frpc use system proxy but system proxy not start until user logged in **Describe the results you received:** 2020/09/28 11:09:43 [W] [service.go:102] login to server failed: dial tcp 127.0.0.1:57890: connectex: No connection coul d be made because the target machine actively refused it. dial tcp 127.0.0.1:57890: connectex: No connection could be made because the target machine actively refused it. **Describe the results you expected:** Is there any configuration can ignore system proxy setting ? **Additional information you deem important (e.g. issue happens only occasionally):** **Can you point out what caused this issue (optional)**

gitea-mirror

2026-05-05 13:01:11 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:01:14 -06:00

Author

Owner

@blizard863 commented on GitHub (Sep 29, 2020):

you can try to login to server by http_proxy or other proxy, if your system proxy is http_proxy ？

@blizard863 commented on GitHub (Sep 29, 2020): you can try to login to server by http_proxy or other proxy, if your system proxy is http_proxy ？

gitea-mirror commented

2026-05-05 13:01:15 -06:00

Author

Owner

@Becods commented on GitHub (Sep 30, 2020):

#Connecting to frps via HTTP PROXY
Please use the http_proxy that comes with the frpc

@Becods commented on GitHub (Sep 30, 2020): [#Connecting to frps via HTTP PROXY](https://github.com/fatedier/frp#connecting-to-frps-via-http-proxy) Please use the http_proxy that comes with the frpc

gitea-mirror commented

2026-05-05 13:01:16 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Nov 15, 2020):

Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Nov 15, 2020): Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.