I rebooted the one that was on 514 and now it’s boot looping again so I’ll let it keep rebooting I guess. I didn’t press update button just reboot in advanced page. It’s still showing up during its reboot as 514 in a devices listing but only if I catch it just before it reboots…it’s still not getting http ntp or normal ntp
looks like 2 units are jost hosed up so bad I need to reflash them.
The biggest issue is they are both displays so means complete disassebly. Im only going to sacrifice stand alone RPi from now on…but this should not be happening in stable systems updates.
I have four Raspberry PI4s running 2022.08.01. All still require in excess of 5 minutes to boot, likely due to time sync issues. But, when I attempt to send a report from the Advanced tab, RoPieee reports failure indicating a firewall or internet problem. Is there any guide summarizing how a firewall must be configured to permit RoPiee access to send reports to the internet? For example, am I expected to configure NAT entries in order to allow RoPieee access to the internet?
On other PI-based applications such as ezBeq, I’ve found it necessary to disable IP6 by editing the /etc/sysctl.conf file. But, I can’t ssh into RoPieee to try that.
On a related note, I have one Raspberry PI running the prior Stable release. No matter how long it remains active, it never indicates that an updated version is available. Again, could this be a firewall -related issue?
I dont’ believe the older 4017/44019 builds will every indicate there is an update, but I think it did say now and then there is a new release version that is available - ie the NG builds we are on now.
Most firewalls should have some rule that allows for internally initiated requests should be allowed out and the responses returned to the requesting device.
Maybe Harry can detail what ports should need to be opened for a Ropieee device to communicate with base, and any other services NTP etc.