search

XavierBerger / RPi-Monitor

Real time monitoring for embedded devices
https://xavierberger.github.io/RPi-Monitor-docs/index.html
GNU General Public License v3.0
1.16k stars 175 forks source link

Can not get information (dynamic.json) from RPi-Monitor server. #344

Open mrblond18 opened 4 years ago

mrblond18 commented 4 years ago

rpi-monitor no information In about 50% of the cases when I open the webpage of the rpi-monitor, I get the proper layout, but no data filled in the fields, with the message: Can not get information (dynamic.json) from RPi-Monitor server. Also see attached screenshot.

It looks like this is from my browser cache. If I refresh I get: Unable to connect Firefox can’t establish a connection to the server at rpi2b0lanmanager.lan:8888.

When I refresh a minute later it works OK with all the data, without restarting the service or doing anything else. It looks like the monitor daeomon or the webpage was "stuck" somehow and cannot serve the data.

How can I investigate further/supply more data...

theWinterDojer commented 4 years ago

I'm experiencing the same exact issue. Happens about half the time I load the web interface. From what I can tell this only started happening when I upgraded to the Pi 4. I don't recall getting this error on Pi 3.

mrblond18 commented 4 years ago

I am experiencing these problems on a RPi2B...

GlynHu commented 3 years ago

Thanks for a terrific app in RPI-Monitor Xavier! :)

I thought it was only me seeing this issue!

I am seeing this on all 3 of my Pi's 4B's...sometimes it connects in an instant other times it sits there for up to 60 seconds or so before it connects and then displays exactly as the screenshot in post 1.

Even then a refresh does not always kick it into life.

If there is anything I can do to help track this down please do not hesitate to ask!

Thanks & kind regards, -=Glyn=-

realestninja commented 5 months ago

Any updates on this?

I have two pis, one of them doesn't have this problem, and on the second one, I just installed it moments ago, following the instructions, and got this problem immediately after install, without changing anything on the config.

Edit: Restarting the pi itself fixed this issue.