Hello everyone and happy holidays!
I just received my Pironman5 yesterday, and today I’m making sure it’s properly setup.
I used the 32GB SD Card provided with the starter kit, the installation was fine, no errors. When opening the dashboard on localhost:34001 , all I see is the top blue toolbar, and the button to change the theme (light/dark). There is no other UI element at all.
Looking at the console of the dev tools, I see some errors:
Failed to load resource: net::ERR_CONNECTION_TIMED_OUT
192.168.4.1:34001/api/v1.0/test?:1
Trying to load this URL in the browser also fails.
This strikes me as /api being proxied to a backend that simply isn’t turned on, but I have no knowledge of how your system is setup so I can’t really debug this on my own.
Note that I did move the OS to an NVME SSD, and this problem still occurs. What can I do here?
Apparently someone else had this issue ( Pironman 5 Dashboard blank - General - Sunfounder Forum ) , and the solution is to use the IP address of the device rather than localhost. While this is a good workaround for the dashboard to actually work, the code itself should probably be fixed so that the binding of the backend also happens on localhost/127.0.0.1 for the future…
LOL… I signed up for the forums to come here and say the same thing…
instead of:
localhost:34001
enter:
[your IP]:34001 (no brackets)
192.168.0.0:34001 or whatever it is…
its at the top of your OLED display…
Right. Our tutorial also explains that by going to your browser and visiting http://:34001
https://docs.sunfounder.com/projects/pironman5/en/latest/control/control_with%20dashboard.html
The IP is the network that the PI5 is configured for, and it will be displayed on the OLED screen once you install the pironman5 software.
If our tutorial is misleading, please feel free to give your personal suggestions here, we will consider your suggestions one by one and improve the tutorial. We will consider your suggestions one by one and improve the tutorial!
Not to disparage your developer team, but honestly, I’m very curious to know why the dashboard doesn’t work on localhost/127.0.0.1. Or rather, why the dashboard works but the API doesn’t. It feels like a bug, not a feature, what reason would there be to force the use of a local network IP rather than the loopback? What if I’m not actually connected to a network, that means I can’t access the dashboard?
Seems… odd.
We’re very sorry, we’ve received your feedback, this is indeed the issue and we’ll fix it for the next release.
For now it is recommended that you use an IP for accessing the dashboard first. Once we fix the issue and update the software, we will notify you here.
