Thank you guys for DietPi, it is a wonderful project!
Creating a bug report/issue
I have searched the existing open and closed issues
System
DietPi v9.8.0 | Bookworm running on a RPi B (armv6l)
Software title: frp (fast reverse proxy)
Steps to reproduce
newly installed headless DietPi (no Desktop Environment, no Webserver), running perfectly fine.
Installed and configured tailscale via dietpi-software, runs fine
Installed frp via dietpi-software as “server only”
Expected behaviour
frps should be available on defined port (default port 7000)
web-based dashboard should be available on port 7500
Actual behaviour
none of the defined ports are open
no web-based dashboard is available
Extra details
Dietpi-services says: frp [enabled], but: state [failed]
systemd log: frps. service: Failed with result 'signal'.
Also: the frp github states that the .ini file format will be deprecated, and .toml should be used. Maybe the dietpi frp install needs a general overhaul?
yes, of course.
I never manually started, stopped or restarted any services.
Nov 26 16:42:43 DietPi systemd[1]: Started frps.service - frp server (DietPi).
Nov 26 16:42:43 DietPi systemd[1]: frps.service: Main process exited, code=killed, status=4/ILL
Nov 26 16:42:43 DietPi systemd[1]: frps.service: Failed with result 'signal'.
Nov 26 16:42:48 DietPi systemd[1]: frps.service: Scheduled restart job, restart counter is at 1.
Nov 26 16:42:48 DietPi systemd[1]: Stopped frps.service - frp server (DietPi).
Nov 26 16:42:48 DietPi systemd[1]: Started frps.service - frp server (DietPi).
Nov 26 16:42:49 DietPi systemd[1]: frps.service: Main process exited, code=killed, status=4/ILL
Nov 26 16:42:49 DietPi systemd[1]: frps.service: Failed with result 'signal'.
Nov 26 16:42:54 DietPi systemd[1]: frps.service: Scheduled restart job, restart counter is at 2.
Nov 26 16:42:54 DietPi systemd[1]: Stopped frps.service - frp server (DietPi).
Nov 26 16:42:54 DietPi systemd[1]: Started frps.service - frp server (DietPi).
Nov 26 16:42:54 DietPi systemd[1]: frps.service: Main process exited, code=killed, status=4/ILL
Nov 26 16:42:54 DietPi systemd[1]: frps.service: Failed with result 'signal'.
Nov 26 16:42:59 DietPi systemd[1]: frps.service: Scheduled restart job, restart counter is at 3.
Nov 26 16:42:59 DietPi systemd[1]: Stopped frps.service - frp server (DietPi).
Nov 26 16:42:59 DietPi systemd[1]: frps.service: Start request repeated too quickly.
Nov 26 16:42:59 DietPi systemd[1]: frps.service: Failed with result 'signal'.
Nov 26 16:42:59 DietPi systemd[1]: Failed to start frps.service - frp server (DietPi).
hmm for me, both frpc and frps are working. I can open dashboard for client & server and ports are LISTEN as well
Nov 27 10:35:48 DietPi5 systemd[1]: Started frpc.service - frp client (DietPi).
Nov 27 10:35:48 DietPi5 frpc[1186]: WARNING: ini format is deprecated and the support will be removed in the future, please use yaml/json/toml format instead!
Nov 27 10:35:48 DietPi5 frpc[1186]: 2024-11-27 10:35:48.479 [I] [sub/root.go:142] start frpc service for config file [/etc/frp/frpc.ini]
Nov 27 10:35:48 DietPi5 frpc[1186]: 2024-11-27 10:35:48.479 [I] [client/service.go:295] try to connect to server...
Nov 27 10:35:48 DietPi5 frpc[1186]: 2024-11-27 10:35:48.479 [I] [client/service.go:174] admin server listen on 0.0.0.0:7400
Nov 27 10:35:48 DietPi5 frpc[1186]: 2024-11-27 10:35:48.488 [I] [client/service.go:287] [5b5535baecd326db] login to server success, get run id [5b5535baecd326db]
Nov 27 10:52:02 DietPi5 systemd[1]: Stopping frpc.service - frp client (DietPi)...
Nov 27 10:52:02 DietPi5 frpc[1186]:
Nov 27 10:52:02 DietPi5 systemd[1]: frpc.service: Deactivated successfully.
Nov 27 10:52:02 DietPi5 systemd[1]: Stopped frpc.service - frp client (DietPi).
Nov 27 10:52:02 DietPi5 systemd[1]: Started frpc.service - frp client (DietPi).
Nov 27 10:52:02 DietPi5 frpc[1230]: WARNING: ini format is deprecated and the support will be removed in the future, please use yaml/json/toml format instead!
Nov 27 10:52:02 DietPi5 frpc[1230]: 2024-11-27 10:52:02.931 [I] [sub/root.go:142] start frpc service for config file [/etc/frp/frpc.ini]
Nov 27 10:52:02 DietPi5 frpc[1230]: 2024-11-27 10:52:02.932 [I] [client/service.go:295] try to connect to server...
Nov 27 10:52:02 DietPi5 frpc[1230]: 2024-11-27 10:52:02.932 [I] [client/service.go:174] admin server listen on 0.0.0.0:7400
Nov 27 10:52:02 DietPi5 frpc[1230]: 2024-11-27 10:52:02.939 [I] [client/service.go:287] [055626b9d5412f50] login to server success, get run id [055626b9d5412f50]
Nov 27 10:35:43 DietPi5 systemd[1]: Started frps.service - frp server (DietPi).
Nov 27 10:35:43 DietPi5 frps[498]: WARNING: ini format is deprecated and the support will be removed in the future, please use yaml/json/toml format instead!
Nov 27 10:35:43 DietPi5 frps[498]: 2024-11-27 10:35:43.210 [I] [frps/root.go:105] frps uses config file: /etc/frp/frps.ini
Nov 27 10:35:43 DietPi5 frps[498]: 2024-11-27 10:35:43.723 [I] [server/service.go:237] frps tcp listen on 0.0.0.0:7000
Nov 27 10:35:43 DietPi5 frps[498]: 2024-11-27 10:35:43.723 [I] [frps/root.go:114] frps started successfully
Nov 27 10:35:43 DietPi5 frps[498]: 2024-11-27 10:35:43.723 [I] [server/service.go:351] dashboard listen on 0.0.0.0:7500
Nov 27 10:35:48 DietPi5 frps[498]: 2024-11-27 10:35:48.488 [I] [server/service.go:576] [5b5535baecd326db] client login info: ip [127.0.0.1:59324] version [0.61.0] hostname [] os [linux] arch [arm64]
Nov 27 10:52:02 DietPi5 frps[498]: 2024-11-27 10:52:02.913 [I] [server/control.go:357] [5b5535baecd326db] client exit success
Nov 27 10:52:02 DietPi5 frps[498]: 2024-11-27 10:52:02.938 [I] [server/service.go:576] [055626b9d5412f50] client login info: ip [127.0.0.1:33602] version [0.61.0] hostname [] os [linux] arch [arm64]
Nov 27 10:52:11 DietPi5 frps[498]: 2024-11-27 10:52:11.928 [I] [server/dashboard_api.go:107] Http request: [/api/serverinfo]
Nov 27 10:52:11 DietPi5 frps[498]: 2024-11-27 10:52:11.928 [I] [server/dashboard_api.go:100] Http response [/api/serverinfo]: code [200]
Nov 27 10:52:13 DietPi5 frps[498]: 2024-11-27 10:52:13.886 [I] [server/dashboard_api.go:227] Http request: [/api/proxy/tcp]
Nov 27 10:52:13 DietPi5 frps[498]: 2024-11-27 10:52:13.887 [I] [server/dashboard_api.go:221] Http response [/api/proxy/tcp]: code [200]
Nov 27 10:52:14 DietPi5 frps[498]: 2024-11-27 10:52:14.529 [I] [server/dashboard_api.go:227] Http request: [/api/proxy/udp]
Nov 27 10:52:14 DietPi5 frps[498]: 2024-11-27 10:52:14.529 [I] [server/dashboard_api.go:221] Http response [/api/proxy/udp]: code [200]
Nov 27 10:52:16 DietPi5 frps[498]: 2024-11-27 10:52:16.547 [I] [server/dashboard_api.go:107] Http request: [/api/serverinfo]
Nov 27 10:52:16 DietPi5 frps[498]: 2024-11-27 10:52:16.547 [I] [server/dashboard_api.go:100] Http response [/api/serverinfo]: code [200]
I followed your suggestion. While trying to stop the service as dietpi user, i got a failed to connect to bus, so I executed with sudo. Here the result:
„Ungültiger Maschinenbefehl“ translates to something like „invalid command“. So far I did not make any changes to the default .ini file, and if opened, the .ini file looks okay.
Also, ss -tulpn | grep frp showed no open ports for frp
Dear @Joulinar
Thanks for your reply and troubleshooting!
If I understand correctly, I have to upgrade my hardware to a newer RPi to get frp to work?
My use case in brief: NAS behind CGNAT. RPi reachable via public IPv4. The goal is to expose a few services/ports from the NAS via the RPi to the public. frp would be a very good choice. Should I get a newer inexpensive RPi or try to achieve this with nginx/lighttpd/rathole or something else?
The same idea with the arm version crossed my mind as well.
I downloaded the arm package from github and was able to start the frp-server without failure! Web-Dashboard is accessible. So the arm package did the trick! Thank you!
From what I figure from a brief google search, arm_hf is supported by armv7+, so in my case (armv6), it wouldn’t work.