(Solved) Solar Assistant Internal Server Error

Got a interesting one here, brand new Solar Assistant, Orange PI pre-loaded.
After startup was able to access the device via WiFI and set the SSID and Password.
Was able to access the UI via IP after it obtained a DHCP address, everything was working per normal.
Shutdown the unit to move to its final spot near the inverters.
Powered it up, but receiving "Internal Server Error" from the UI when I open configuration page, this is with no USB devices or cables connected.
Tried plugging in the Ethernet port, obtained successfully a IP on it, and same problem, either Internal Server Error or times out and ERR_CONNECTION_REFUSED.

Connected the HDMI to the unit and rebooted, and seeing same error to 127.0.0.1
Anyone else have this issue or a way to re-image/reset the pre-loaded Orange PI? Not sure what could of triggered this issue, it seems to me the backend might have an error or rolling restarting the service, as it goes from ERR_CONNECTION_REFUSED to sometimes a white screen of Internal Server Error.

Haven't seen that one before.
But contact Pierre, he'll get you fixed up.

timselectric said:

info@solar-assistant.io

Click to expand...

Yup done right before this post, wanted to see if anyone had seen this before.

Mine did the same thing a few days ago. Nothing I did worked. A day later everything was fine

127.0.0.1 is localhost. That means the browser is trying to connect to the machine it's running on ie. your own computer, not solar-assistant.

GregTR said:

127.0.0.1 is localhost. That means the browser is trying to connect to the machine it's running on ie. your own computer, not solar-assistant.

Click to expand...

Hi Greg, that's a screenshot from the monitor attached to the Solar-Assistant via HDMI.

linuxdrake said:

Hi Greg, that's a screenshot from the monitor attached to the Solar-Assistant via HDMI.

Click to expand...

My bad, I have only used mine in a headless config didn't know/assume someone would hook a monitor to one.

connect to it via Bluetooth and check network settings

Troubleshooter said:

connect to it via Bluetooth and check network settings

Accessing SolarAssistant via Bluetooth

How to connect your Android to SolarAssistant via Bluetooth.

solar-assistant.io

Click to expand...

Wish I could, its the Orange Pi, which has no Bluetooth enabled by SA.

Agree with @Troubleshooter. You have a network connection issue. As I recall, SA has it locked down so you can't easily check it. Pierre can likely walk you through some diagnostics though.

EastTexCowboy said:

Agree with @Troubleshooter. You have a network connection issue. As I recall, SA has it locked down so you can't easily check it. Pierre can likely walk you through some diagnostics though.

Click to expand...

I agree, I was able to get a console open from the HDMI input, by right clicking, and was able to view the current IP config, but not much else, cant view /var/log/messages as the "kiosk" user has no access rights.

I can view dmesg, and no HW errors, but via the ETH IP or local on orangePI browser cannot open it, I see the beam service via "top" roll crashing, with different PID's each time..so I think a software issue.

Well some good news and not so good.

In consultation with Pierre, was able to reimage the device using the SD card. Have to use my own SD card vs the embedded eMMC storage, but I think in the long run will be better for endurance, as using a larger SD card class10 of 64GB to give plenty of space for data.

Not 100% sure what corrupted/errored the initial install on the eMMC, but up and running now.

I just had this happen as well. On a trip so no option to reimage until I get back. Anything else I can try or is the only option a reimage?

mine just did this as well, sent an email in. Where can I find the latest image to go the SD card route?