Pironman dashboard is blank

uname -r
6.12.47-v8-16k+
cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Version: 1.2.19

Installation log (and then restart):

~/pironman5 $ sudo python3 install.py
Installing for Pironman 5 Max
Version: 1.2.19

Install build dependencies...
 - Update package list... Done
 - Install build dependencies: python3-pip python3-venv git curl... Done
Run commands before install...
 - Run command before install: Download influxdb key... Done
 - Run command before install: Setup influxdb install source... Done
 - Run command before install: Cleanup influxdata-achive.key... Done
 - Run command before install: Install LGPIO... Done
Install APT dependencies...
 - Install APT dependencies: influxdb python3-gpiozero libfreetype6-dev lsof python3-dev libjpeg-dev kmod i2c-tools libopenjp2-7... Done
Create working directory...
 - Create work directory... Done
 - Change work directory mode... Done
 - Change work directory owner... Done
 - Create log directory... Done
 - Change log directory mode... Done
 - Change log directory owner... Done
 - Remove old virtual environment... Done
 - Create virtual environment... Done
Install PIP dependencies...
 - Install pip... Done
 - Install setuptools... Done
 - Install build... Done
 - Install adafruit-circuitpython-neopixel-spi... Done
 - Install rpi.lgpio... Done
 - Install smbus2... Done
 - Install Pillow... Done
 - Install gpiozero... Done
 - Install Adafruit-Blinka==8.59.0... Done
 - Install gpiod... Done
Install Python source packages...
 - Uninstall pironman5 old package... Done
 - Install pironman5 from source... Done
 - Uninstall pm_auto old package... Done
 - Install pm_auto from source... Done
 - Uninstall pm_dashboard old package... Done
 - Install pm_dashboard from source... Done
 - Uninstall sf_rpi_status old package... Done
 - Install sf_rpi_status from source... Done
Setup auto start...
 - Copy binary file... Done
 - Change binary file mode... Done
 - Copy service file... Done
 - Enable service... Done
 - Reload systemd... Done
Probe modules...
 - add module: i2c-dev... Done
Copy device tree overlay...
 - Copy dtoverlay sunfounder-pironman5.dtbo... Done
Change work directory owner...
 - Change work directory owner... Done
Finished
Cleanup
 - Remove build... Done

service status:

service pironman5 status
● pironman5.service - pironman5 service
     Loaded: loaded (/etc/systemd/system/pironman5.service; enabled; preset: enabled)
     Active: active (running) since Sat 2025-09-20 15:47:54 BST; 13s ago
    Process: 4086 ExecStart=/usr/local/bin/pironman5 start --background (code=exited, status=0/SUCCESS)
   Main PID: 4092 (pironman5-servi)
      Tasks: 14 (limit: 9585)
     Memory: 81.7M
        CPU: 1.760s
     CGroup: /system.slice/pironman5.service
             ├─4092 /opt/pironman5/venv/bin/python3 /opt/pironman5/venv/bin/pironman5-service start
             ├─6299 /bin/sh -c "lsof -i -P -n | grep LISTEN | grep influxd | awk '{print \$9}' | cut -d ':' -f 2"
             ├─6300 lsof -i -P -n
             ├─6301 grep LISTEN
             ├─6302 grep influxd
             ├─6303 awk "{print \$9}"
             └─6304 cut -d : -f 2

Sep 20 15:48:04 home pironman5[4092]: 25/09/20 15:48:04.271 [INFO] Connected to br-099e7cc8e5b4: 172.19.0.1
Sep 20 15:48:04 home pironman5[4092]: 25/09/20 15:48:04.271 [INFO] Connected to br-0f5647f79164: 172.27.0.1
Sep 20 15:48:04 home pironman5[4092]: 25/09/20 15:48:04.348 [INFO] Influxdb is ready
Sep 20 15:48:04 home pironman5[4092]: 25/09/20 15:48:04.365 [INFO] Dashboard Server start
Sep 20 15:48:04 home pironman5[4092]: 25/09/20 15:48:04.368 [INFO] PmDashboard started
Sep 20 15:48:04 home pironman5[4092]: 25/09/20 15:48:04.436 [INFO] PWM Fan is supported, sync all other fan with pwm fan
Sep 20 15:48:04 home pironman5[4092]: 25/09/20 15:48:04.504 [DEBUG] Waiting for InfluxDB to be ready
Sep 20 15:48:04 home pironman5[4092]: 25/09/20 15:48:04.633 [INFO] Influxdb is ready
Sep 20 15:48:04 home pironman5[4092]: 25/09/20 15:48:04.649 [INFO] Data Logger Start
Sep 20 15:48:06 home pironman5[4092]: 25/09/20 15:48:06.610 [INFO] OLED sleep timeout, sleeping

dashboard:

In developer console:

home.jsx:71  GET http://192.168.88.200:34001/api/v1.0/get-data 404 (NOT FOUND)
home.jsx:74 Request failed with status 404

/get-data:

<!doctype html>
<html lang=en>
<title>404 Not Found</title>
<h1>Not Found</h1>
<p>The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.</p>

I am accesing from: http://192.168.88.200:34001/ and I tried ssh tunel to 34001:localhost:34001 and still the same.

Settings from dashboard are working. I can change RGB, OLED, FAN LED etc. But dashboard with stats nothing.

It started work after:

sudo service pironman5 stop
sudo rm -fr /var/lib/influxdb/data/pironman5
sudo rm -fr /var/lib/influxdb/wal/pironman5
sudo service pironman5 start

It seems influxdb is crashing somehow.

Thank you very much for your feedback. We will conduct verification tests based on the system version you provided to see if we can reproduce the issue you encountered and implement a fix.

To help resolve this, we recommend that you avoid updating or upgrading your system for now. Instead, please try directly downloading and installing our Pironman 5 software, then access the dashboard to check if it functions correctly.

If you haven’t upgraded your system, the kernel version should be 6.12.25. However, your current kernel version is 6.12.47, which indicates that the system has been updated.

Everything should be up to date. It happens if I forcibly remove the USB-C power and connect it back. I simulate a power outage by this.

Could you please let us know:

Which method or channel did you use to install the operating system?

We recommend installing the latest version of the system from its official source. If possible, please share the download link or source you used.

It would also be very helpful if you could describe the detailed steps you followed during the successful installation.

This information will allow us to reproduce the process and identify the root cause more efficiently.

Which method or channel did you use to install the operating system?
Raspberry Pi Imager (rpi-imager) > create Raspberry PI OS Lite to NVME disk (booted from USB device)

It would also be very helpful if you could describe the detailed steps you followed during the successful installation.
I did setup steps from: Set Up on Raspberry Pi/Ubuntu/Kali/Homebridge OS — SunFounder Pironman 5 documentation (20 Sep, 2025)

sudo apt-get update
sudo apt-get install git -y
sudo apt-get install python3 python3-pip python3-setuptools -y

and

cd ~
git clone -b max https://github.com/sunfounder/pironman5.git --depth 1
cd ~/pironman5
sudo python3 install.py

last commit which version I have ~/pironman5 :

 $ git log -1
commit cf1b40f11f06b4b83273bed097db589a0d099f9b (grafted, HEAD -> max, tag: 1.2.19, origin/max)
Author: Cavon <cavonxx@gmail.com>
Date:   Tue Sep 16 14:03:58 2025 +0800

    chore: update version from 1.2.19a1 to 1.2.19

We have tested according to your steps. The dashboard is accessible and displays data correctly.It might be a sporadic issue. We will fix it in future updates.

After you ran the following commands:

sudo service pironman5 stop
sudo rm -fr /var/lib/influxdb/data/pironman5
sudo rm -fr /var/lib/influxdb/wal/pironman5
sudo service pironman5 start

Does the problem still occur?

Hi,
I’ve the same problem. Out of the blue the dashboard is no longer working.
I get Request Error: 404
..

After reading @SunFounder_Moderator message:
sudo service pironman5 stop
sudo rm -fr /var/lib/influxdb/data/pironman5
sudo rm -fr /var/lib/influxdb/wal/pironman5
sudo service pironman5 start

After that I got the Dashboard up and running again. It does give me the Request Error: 404 but I see the data flowing again. Perhaps a bug?

Please provide the system version and the browser you used to access the dashboard.
If you can provide more operational details, it will help us reproduce and resolve the issue.