[GH-ISSUE #2709] win10下运行frpc,提示拒绝访问,是什么原因? #2163

Closed
opened 2026-05-05 13:23:31 -06:00 by gitea-mirror · 3 comments
Owner

Originally created by @huangzhuohua on GitHub (Dec 19, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2709

Bug Description

D:\frp_0.38.0_windows_amd64>frpc -c frpc.ini
拒绝访问。

frpc Version

0.38.0

frps Version

0.38.0

System Architecture

windows/amd64

Configurations

[common]
server_addr = X.X.X.X
server_port = 7000

[RDP]
type = tcp
local_ip = 127.0.0.1
local_port = 3389
remote_port = 6000

Logs

No response

Steps to reproduce

...

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @huangzhuohua on GitHub (Dec 19, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2709 ### Bug Description D:\frp_0.38.0_windows_amd64>frpc -c frpc.ini 拒绝访问。 ### frpc Version 0.38.0 ### frps Version 0.38.0 ### System Architecture windows/amd64 ### Configurations [common] server_addr = X.X.X.X server_port = 7000 [RDP] type = tcp local_ip = 127.0.0.1 local_port = 3389 remote_port = 6000 ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### 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 13:23:31 -06:00
Author
Owner

@aorosora commented on GitHub (Dec 26, 2021):

被 Defender 攔截了。。。。。

<!-- gh-comment-id:1001253729 --> @aorosora commented on GitHub (Dec 26, 2021): 被 Defender 攔截了。。。。。
Author
Owner

@Wronthyou-Emme commented on GitHub (Jan 6, 2022):

首先检查是否被windows Defender 拦截,添加进信任区。然后检查文件是否只读,只读关掉。

<!-- gh-comment-id:1006600712 --> @Wronthyou-Emme commented on GitHub (Jan 6, 2022): 首先检查是否被windows Defender 拦截,添加进信任区。然后检查文件是否只读,只读关掉。
Author
Owner

@github-actions[bot] commented on GitHub (Feb 6, 2022):

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

<!-- gh-comment-id:1030721300 --> @github-actions[bot] commented on GitHub (Feb 6, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
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: github-starred/frp#2163
No description provided.