github-starred/frp

Fork 0

mirror of https://github.com/fatedier/frp.git synced 2026-05-15 08:05:49 -06:00

[GH-ISSUE #2257] HTTP_PROXY on Windows 10 #1794

New issue

Closed

opened 2026-05-05 13:09:32 -06:00 by gitea-mirror · 9 comments

gitea-mirror commented

2026-05-05 13:09:32 -06:00

Owner

Originally created by @tuqu0 on GitHub (Feb 25, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2257

I am running frpc on Windows 10 x64 and set http_proxy=http://127.0.0.1:8080 from the configuration file.
Then I start Burp (local proxy interceptor) to see if it works but it didn't. I got the error : "session shutdown".

Without the http_proxy line I can connect to my frps server without any problem.
So does use of http_proxy works on Windows ?

Thx

Originally created by @tuqu0 on GitHub (Feb 25, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2257 Hi I am running frpc on Windows 10 x64 and set http_proxy=http://127.0.0.1:8080 from the configuration file. Then I start Burp (local proxy interceptor) to see if it works but it didn't. I got the error : "session shutdown". Without the http_proxy line I can connect to my frps server without any problem. So does use of http_proxy works on Windows ? Thx

gitea-mirror

2026-05-05 13:09:32 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:09:36 -06:00

Author

Owner

@fatedier commented on GitHub (Feb 26, 2021):

It should work on any os.

Make sure you don't set any other system proxies?

@fatedier commented on GitHub (Feb 26, 2021): It should work on any os. Make sure you don't set any other system proxies?

gitea-mirror commented

2026-05-05 13:09:37 -06:00

Author

Owner

@tuqu0 commented on GitHub (Feb 26, 2021):

No, I have not other system proxy.

Config:

frps.ini

[common]
bind_port = 8888

frpc.ini

[common]
server_addr = <public_ip>
server_port = 8888
http_proxy = http://127.0.0.1:8080

[socks5]
type = tcp
remote_port = 1080
plugin = socks5

Message error on frpc side:

2021/02/26 15:31:40 [W] [service.go:104] login to server failed: write tcp 127.0.0.1:55738->127.0.0.1:8080: wsasend: An established connection was aborted by the software in your host machine.
write tcp 127.0.0.1:55738->127.0.0.1:8080: wsasend: An established connection was aborted by the software in your host machine.

@tuqu0 commented on GitHub (Feb 26, 2021): No, I have not other system proxy. Config: frps.ini ``` [common] bind_port = 8888 ``` frpc.ini ``` [common] server_addr = <public_ip> server_port = 8888 http_proxy = http://127.0.0.1:8080 [socks5] type = tcp remote_port = 1080 plugin = socks5 ``` Message error on frpc side: ``` 2021/02/26 15:31:40 [W] [service.go:104] login to server failed: write tcp 127.0.0.1:55738->127.0.0.1:8080: wsasend: An established connection was aborted by the software in your host machine. write tcp 127.0.0.1:55738->127.0.0.1:8080: wsasend: An established connection was aborted by the software in your host machine. ```

gitea-mirror commented

2026-05-05 13:09:38 -06:00

Author

Owner

@fatedier commented on GitHub (Mar 1, 2021):

It seems connection to 127.0.0.1:8080 was aborted by your service.

@fatedier commented on GitHub (Mar 1, 2021): It seems connection to `127.0.0.1:8080` was aborted by your service.

gitea-mirror commented

2026-05-05 13:09:38 -06:00

Author

Owner

@tuqu0 commented on GitHub (Mar 1, 2021):

Yes but it doesn't make sense, it is my local proxy (Burp) running on this port so I should see the request from it.

@tuqu0 commented on GitHub (Mar 1, 2021): Yes but it doesn't make sense, it is my local proxy (Burp) running on this port so I should see the request from it.

gitea-mirror commented

2026-05-05 13:09:39 -06:00

Author

Owner

@tuqu0 commented on GitHub (Mar 3, 2021):

I set up a VM A, with the firewall blocking everything except TCP port 8080 where frpc is running.
On a VM B, I set up a proxy running on port 8080, so VM A can go reach Internet through VM B proxy and finally join VM C where frps is running.

Using the configuration above in this scenario, does not work. FRPC on VM A is not sending any request to the proxy server running on VM B (they are on the same network, so that's not a network issue).

On VM A, if the firewall is allowing all connections and if I remove the http_proxy from FRPC configuration file, I can connect to the FRPS server. So it does not seem a configuration issue, but that the http_proxy option is not working.

@tuqu0 commented on GitHub (Mar 3, 2021): I set up a VM A, with the firewall blocking everything except TCP port 8080 where frpc is running. On a VM B, I set up a proxy running on port 8080, so VM A can go reach Internet through VM B proxy and finally join VM C where frps is running. Using the configuration above in this scenario, does not work. FRPC on VM A is not sending any request to the proxy server running on VM B (they are on the same network, so that's not a network issue). On VM A, if the firewall is allowing all connections and if I remove the http_proxy from FRPC configuration file, I can connect to the FRPS server. So it does not seem a configuration issue, but that the http_proxy option is not working.

gitea-mirror commented

2026-05-05 13:09:39 -06:00

Author

Owner

@fatedier commented on GitHub (Mar 3, 2021):

Captura packages to 127.0.0.1:8080 by tcpdump?

@fatedier commented on GitHub (Mar 3, 2021): Captura packages to `127.0.0.1:8080` by tcpdump?

gitea-mirror commented

2026-05-05 13:09:39 -06:00

Author

Owner

@tuqu0 commented on GitHub (Mar 3, 2021):

Okay, I ran Wireshark and packets are sent to the VM B where the proxy is running.
Somehow, the proxy (Burp) says : "Unsuported or unrecognized SSL message".

However, if I look at the packets captured with wireshark I can see the data with info about the FRPC host.

I tried with a public HTTP proxy available online and it works.

Any idea about this SSL issue ?

Thank you

@tuqu0 commented on GitHub (Mar 3, 2021): Okay, I ran Wireshark and packets are sent to the VM B where the proxy is running. Somehow, the proxy (Burp) says : "Unsuported or unrecognized SSL message". However, if I look at the packets captured with wireshark I can see the data with info about the FRPC host. I tried with a public HTTP proxy available online and it works. Any idea about this SSL issue ? Thank you

gitea-mirror commented

2026-05-05 13:09:40 -06:00

Author

Owner

@fatedier commented on GitHub (Mar 3, 2021):

I'm not familiar with Burp. I'm not sure if it supports HTTP PROXY? Maybe you have not used it in a correct way.

@fatedier commented on GitHub (Mar 3, 2021): I'm not familiar with Burp. I'm not sure if it supports HTTP PROXY? Maybe you have not used it in a correct way.

gitea-mirror commented

2026-05-05 13:09:40 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 18, 2021):

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 (Apr 18, 2021): Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.

gitea-mirror referenced this issue

2026-05-05 14:42:27 -06:00

[PR #1794] [MERGED] feat: Support user specify udp packet size in config #4455

gitea-mirror referenced this issue

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

[PR #1990] [MERGED] bump version to v0.34.0 #4486