extern/frp
1
1
Fork 0
mirror of https://github.com/fatedier/frp.git synced 2024-12-04 22:01:43 +01:00
Code Issues Packages Projects Releases Wiki Activity

mentioned antivirus detection in installation instructions, added recommendation to whitelist client binaries in antivirus (#3647)

Browse Source
This commit is contained in:
ZeroVocabulary 2023-10-09 03:05:03 -04:00 committed by GitHub
parent 5e70d5bee0
commit 21d8e674f0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -117,6 +117,8 @@ Next, place the `frps` binary and `frps.ini` configuration file on Server A, whi
Finally, place the `frpc` binary and `frpc.ini` configuration file on Server B, which is located on a LAN that cannot be directly accessed from the public internet.
Some antiviruses improperly mark frpc as malware and delete it. This is due to frp being a networking tool capable of creating reverse proxies. Antiviruses sometimes flag reverse proxies due to their ability to bypass firewall port restrictions. If you are using antivirus, then you may need to whitelist/exclude frpc in your antivirus settings to avoid accidental quarantine/deletion. See [issue 3637](https://github.com/fatedier/frp/issues/3637) for more details.
### Access your computer in a LAN network via SSH
1. Modify `frps.ini` on server A by setting the `bind_port` for frp clients to connect to: