FoxESS Community - Owners & Installers Forum

The situation has corrected itself Both the web portal and App are now working as usual. I did nothing to attempt to fix this for fear of making things worse

I noticed this morning that both the web portal and App are not operating correctly. The App gives me no info on the opening page and the web portal shows data on the overview but gives a 41200-Query data failed error when I try to display the inverter details. The datalogger is blinking slowly and shows a 4 bar signal with a green tick. The Energy Stats App takes a while but does display data.

Anyone else having issues or is the problem local? Thanks.

Strange behaviour here too (browser & iPhone app). No devices shown on app home page, need to refresh a few times - once devices are available, clicking the Battery gives me no data for today (despite it being there at around 08:00). Same in browser. Data for last month is available, but not by Day. No other features appear impacted.

I am having exactly the same problem with Web and App not displaying data or being slow to load the little data it can display. Lots of "Time out" messages from the App.

This was working fine yesterday evening.

Rebooted router, now data appears in website, and app followed about 10 mins later.

Update...

It's just come back to life.

Normal service has been resumed.

There have been some issues reported on the Fox cloud services this morning, I gather normal service resumed a few hours later.

Thanks Dave!

I'm just curious why the FoxESS Cloud Status Page (https://monitor.foxesscommunity.com/status/foxess) showed that everything was operational at the time of the problem?

Boots wrote: ↑Mon Nov 03, 2025 3:17 pm Thanks Dave!

I'm just curious why the FoxESS Cloud Status Page (https://monitor.foxesscommunity.com/status/foxess) showed that everything was operational at the time of the problem?

The webpage checks that the Fox web servers are there and responding within a reasonable time, this is one of those frustrating moments where the API was responding, the request was being passed to the data processors and that’s where the problem occurred, and so it responded with a valid response message (albeit to confirm failure)