From 21d8e674f0e7a167e2ab40183a512f8d29126cc2 Mon Sep 17 00:00:00 2001 From: ZeroVocabulary Date: Mon, 9 Oct 2023 03:05:03 -0400 Subject: [PATCH] mentioned antivirus detection in installation instructions, added recommendation to whitelist client binaries in antivirus (#3647) --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 0ae9374..5dc8658 100644 --- a/README.md +++ b/README.md @@ -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: