mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #2435] need help with frps.service and frpc.service for auto starting #1938
Labels
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/frp#1938
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @aliakbar-bsr on GitHub (Jun 4, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2435
hi i have a problem with systemd (frp version 0.37.0) i moved frps.service on a vps with non root user to /etc/systemd/system and give it permission by chmod u+x and on client side with a pi4 i did the same but with frpc.service on both i got error when i checked the status and here it is
$ sudo systemctl status frpc.service
Warning: The unit file, source configuration file or drop-ins of frpc.service changed on disk. Run 'systemctl daemon-re
● frpc.service - Frp Client Service
Loaded: loaded (/etc/systemd/system/frpc.service; disabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2021-06-04 16:59:55 BST; 2s ago
Process: 8013 ExecStart=/home/pi/frp_0.37.0_linux_arm/frpc -c /home/pi/frp_0.37.0_linux_arm/frpc.ini (code=exited, st
Main PID: 8013 (code=exited, status=1/FAILURE)
on frps.service file i used Execstart={/home/directory to frps -c /home/directory to frps.ini} and on pi4 when i entered the directory of frpc it didnt do anything but when i move to frp directory and i entered same directory it started frpc connecting to server
sorry about bad english and wish to find the solution with your helps
@github-actions[bot] commented on GitHub (Jul 20, 2021):
Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.