[GH-ISSUE #4791] 请问有人试过visual studio远程调试吗？（remote debugger）

gitea-mirror commented

2026-05-05 14:25:23 -06:00

Owner

Copy link

Originally created by @860git on GitHub (May 7, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4791

Bug Description

跨公网，部署文件可以，但是无法调试程序，提示：
Unable to start debugging.
The Visual Studio 2022 Remote Debugger (MSVSMON.EXE) does not appear to be running on the remote computer. This may be because a firewall is preventing communication to the remote computer. Please see Help for assistance on configuring remote debugging.

frpc Version

frp_0.62.0_windows_amd64

frps Version

frp_0.62.0_windows_amd64

System Architecture

windows/amd64

Configurations

server：
bindPort = 8001

client：
serverAddr = "x.x.x.x"
serverPort = 8001

proxies
name = "test-tcp"
type = "tcp"
localIP = "127.0.0.1"
localPort = 4026
remotePort = 8002

Logs

No response

Steps to reproduce

run frps.exe -c frps.toml on vps
run frpc.exe -c frpc.toml on custom pc
run remote debugger on custom pc
start debugging on dev pc
...

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @860git on GitHub (May 7, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4791 ### Bug Description 跨公网，部署文件可以，但是无法调试程序，提示： Unable to start debugging. The Visual Studio 2022 Remote Debugger (MSVSMON.EXE) does not appear to be running on the remote computer. This may be because a firewall is preventing communication to the remote computer. Please see Help for assistance on configuring remote debugging. ### frpc Version frp_0.62.0_windows_amd64 ### frps Version frp_0.62.0_windows_amd64 ### System Architecture windows/amd64 ### Configurations server： bindPort = 8001 ------------------------------------ client： serverAddr = "x.x.x.x" serverPort = 8001 [[proxies]] name = "test-tcp" type = "tcp" localIP = "127.0.0.1" localPort = 4026 remotePort = 8002 ### Logs _No response_ ### Steps to reproduce 1. run frps.exe -c frps.toml on vps 2. run frpc.exe -c frpc.toml on custom pc 3. run remote debugger on custom pc 4. start debugging on dev pc ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:25:24 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

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

Author

Owner

Copy link

@mbj2014 commented on GitHub (May 21, 2025):

Visual Studio 远程调试器可作为应用程序或后台服务运行。当它作为应用程序运行时，它将使用默认分配的端口，如下所示：

Visual Studio 2022：4026

Visual Studio 2019：4024

Visual Studio 2017：4022

Visual Studio 2015：4020

Visual Studio 2013：4018

Visual Studio 2012：4016

你要让remoteport也是4026，这样VS2022才能通过默认的端口穿过frp访问到内网的调试器。

@mbj2014 commented on GitHub (May 21, 2025): Visual Studio 远程调试器可作为应用程序或后台服务运行。当它作为应用程序运行时，它将使用默认分配的端口，如下所示： Visual Studio 2022：4026 Visual Studio 2019：4024 Visual Studio 2017：4022 Visual Studio 2015：4020 Visual Studio 2013：4018 Visual Studio 2012：4016 你要让remoteport也是4026，这样VS2022才能通过默认的端口穿过frp访问到内网的调试器。

gitea-mirror commented

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

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Jun 5, 2025):

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

@github-actions[bot] commented on GitHub (Jun 5, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

gitea-mirror commented

2026-05-05 14:25:28 -06:00

Author

Owner

Copy link

@860git commented on GitHub (Aug 7, 2025):

@mbj2014 非常感谢你的提示

@860git commented on GitHub (Aug 7, 2025): @mbj2014 非常感谢你的提示

No Branch/Tag specified