[GH-ISSUE #1355] HTTP service makes systemctl unable. #1075

New issue

Closed

opened 2026-05-05 12:41:25 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 12:41:25 -06:00

Owner

Originally created by @xiaoxin2016 on GitHub (Aug 3, 2019).
Original GitHub issue: https://github.com/fatedier/frp/issues/1355

Issue is only used for submiting bug report and documents typo. If there are same issues or answers can be found in documents, we will close it directly.
(为了节约时间，提高处理问题的效率，不按照格式填写的 issue 将会直接关闭。)
(请不要在 issue 评论中出现无意义的加1，我也是 等内容，将会被直接删除。)
(由于个人精力有限，和系统环境，网络环境等相关的求助问题请转至其他论坛或社交平台。)

Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST

What version of frp are you using (./frpc -v or ./frps -v)?
frpc: 0.27.1
frpc: 0.28.0

What operating system and processor architecture are you using (go env)?
both CentOS 7

Configures you used:
server:

[common]
bind_port = 7000
vhost_http_port = 80

client:

[common]
server_addr = omit it.
server_port = 7000

 [web]
type = http
local_port = 80
custom_domains = omit it

Steps to reproduce the issue:

running ./frps -c frps.ini without problems.
ln -s /usr/local/frp/systemd/frps.service /lib/systemd/system/ #Add systemd unit
use systemctl start frps to start it but failed.

Describe the results you received:

Describe the results you expected:

Additional information you deem important (e.g. issue happens only occasionally):
Note: if there is no HTTP service, it works.
and just run it directly, it works.

Can you point out what caused this issue (optional)

Originally created by @xiaoxin2016 on GitHub (Aug 3, 2019). Original GitHub issue: https://github.com/fatedier/frp/issues/1355 Issue is only used for submiting bug report and documents typo. If there are same issues or answers can be found in documents, we will close it directly. (为了节约时间，提高处理问题的效率，不按照格式填写的 issue 将会直接关闭。) (请不要在 issue 评论中出现无意义的 **加1**，**我也是** 等内容，将会被直接删除。) (由于个人精力有限，和系统环境，网络环境等相关的求助问题请转至其他论坛或社交平台。) Use the commands below to provide key information from your environment: You do NOT have to include this information if this is a FEATURE REQUEST **What version of frp are you using (./frpc -v or ./frps -v)?** frpc: 0.27.1 frpc: 0.28.0 **What operating system and processor architecture are you using (`go env`)?** both CentOS 7 **Configures you used:** server: ``` [common] bind_port = 7000 vhost_http_port = 80 ``` client: ``` [common] server_addr = omit it. server_port = 7000 [web] type = http local_port = 80 custom_domains = omit it ``` **Steps to reproduce the issue:** 1. running ./frps -c frps.ini without problems. 2. `ln -s /usr/local/frp/systemd/frps.service /lib/systemd/system/ #Add systemd unit` 3. use `systemctl start frps` to start it but failed. **Describe the results you received:** ![dir](https://user-images.githubusercontent.com/24978668/62415425-27a6cc80-b65c-11e9-9834-a58736969c3d.png) ![systemd](https://user-images.githubusercontent.com/24978668/62415427-29709000-b65c-11e9-9e6a-8f9ea7a275fb.png) **Describe the results you expected:** **Additional information you deem important (e.g. issue happens only occasionally):** Note: if there is no HTTP service, it works. and just run it directly, it works. **Can you point out what caused this issue (optional)**

gitea-mirror closed this issue

2026-05-05 12:41:27 -06:00

gitea-mirror commented

2026-05-05 12:41:29 -06:00

Author

Owner

@wwqgtxx commented on GitHub (Aug 19, 2019):

you can try to edit the frps.service's [Service] section and add those line before Restart=on-failure

CapabilityBoundingSet=
CapabilityBoundingSet=CAP_NET_BIND_SERVICE
AmbientCapabilities=
AmbientCapabilities=CAP_NET_BIND_SERVICE

@wwqgtxx commented on GitHub (Aug 19, 2019): you can try to edit the `frps.service`'s `[Service]` section and add those line before `Restart=on-failure` ```ini CapabilityBoundingSet= CapabilityBoundingSet=CAP_NET_BIND_SERVICE AmbientCapabilities= AmbientCapabilities=CAP_NET_BIND_SERVICE ```