Home Assistant Remote access 2024.1.4（aliyun vps server+ frp+raspberry pi 3B+）How to install Raspberry Pi OS Lite (64-bit)

[Unit]
Description=Frp Client Service
After=network.target

[Service]
Type=simple
User=nobody
Restart=on-failure
RestartSec=5s
ExecStart=/usr/local/frp/frpc -c /usr/local/frp/frpc.ini

[Install]
WantedBy=multi-user.target

sudo systemctl daemon-reload
sudo systemctl enable frpc.service
sudo systemctl start frpc.service
sudo systemctl restart frpc.service
sudo systemctl stop frpc.service
sudo systemctl status frpc.service

sudo journalctl -fu frpc.service --since today

root@raspberrypi:~# sudo systemctl daemon-reload
root@raspberrypi:~# sudo systemctl status frpc.service
○ frpc.service - Frp Client Service
     Loaded: loaded (/etc/systemd/system/frpc.service; disabled; preset: enabled)
     Active: inactive (dead)

Feb 06 15:50:27 raspberrypi systemd[1]: [🡕] /etc/systemd/system/frpc.service:7: Special user nobody config>

root@raspberrypi:~# sudo systemctl status frpc.service
○ frpc.service - Frp Client Service
     Loaded: loaded (/etc/systemd/system/frpc.service; disabled; preset: enabled)
     Active: inactive (dead)

Feb 06 15:50:27 raspberrypi systemd[1]: [🡕] /etc/systemd/system/frpc.service:7: Special user nobody config>
Feb 06 15:50:55 raspberrypi systemd[1]: [🡕] /etc/systemd/system/frpc.service:7: Special user nobody config>

root@raspberrypi:~# sudo systemctl start frpc.service
root@raspberrypi:~# sudo systemctl status frpc.service
● frpc.service - Frp Client Service
     Loaded: loaded (/etc/systemd/system/frpc.service; disabled; preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Tue 2024-02-06 15:51:17 GMT; 3s ago
    Process: 6622 ExecStart=/usr/local/frp/frpc -c /usr/local/frp/frpc.ini (code=exited, status=1/FAILURE)
   Main PID: 6622 (code=exited, status=1/FAILURE)
        CPU: 52ms

400: Bad Request

WebSocket connection to 'wss://ha.matterxiaomi.com/api/websocket' failed: Error during WebSocket handshake: Unexpected response code: 400

Enable parsing of the X-Forwarded-For header, passing on the client’s correct IP address in proxied setups. You must also whitelist trusted proxies using the trusted_proxies setting for this to work. Non-whitelisted requests with this header will be considered IP spoofing attacks, and the header will, therefore, be ignored.

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 127.0.0.1      # Add the IP address of the proxy server
    - 127.0.0.0/24  # You may also provide the subnet mask

/data/frpc# ls -l

-rwxr-xr-x 1 root root 1681 Jun  3 21:06 restart-frpc.sh

[Unit]
Description=Script Frp Client Service
After=network.target network-online.target
Requires=network-online.target

[Service]
ExecStart=/data/frpc/restart-frpc.sh
Restart=always
RestartSec=1min

[Install]
WantedBy=multi-user.target

sudo systemctl daemon-reload
sudo systemctl enable frpc_auto_run_script.service
sudo systemctl start frpc_auto_run_script.service
sudo systemctl restart frpc_auto_run_script.service
sudo systemctl stop frpc_auto_run_script.service
sudo systemctl status frpc_auto_run_script.service

sudo journalctl -fu frpc_auto_run_script.service --since today