Can't access Allsky System Configuration

[WEdward2]

Good morning,
I have the latest version of Allsky running on a Raspberry Pi 4B, which has been running now for months.
This morning (following a power failure), I can NOT connect to the Allsky System/configuration settings page.
The software is running and I can view the Camera output from "http://allsky.local/allsky/index.php", I just can't connect to the settings page without getting:
"Hmmm… can't reach this page"
"allsky.local refused to connect."

Ideas to try?
Thanks
Bill

[EricClaeys]

The "Hmmm" message is not from Allsky but I assume from your browser.
Just to be clear, you get an error if you go to the WebUI at http://allsky.local but when going to http://allsky.local/allsky you see the local Allsky Website? Do the links on the Allsky Website work?

If the above is true, there might be some disk corruption since the WebUI and the local Website use that same web server.

Does /var/log/lighttpd/error.log contain anything?

[WEdward2]

Correct the 2nd URL works and all the links work just fine. But the URL HTTP://allsky.local gives the browser error I posted earlier.

The error.log does show some entries, but I don't know how to interpret them:
<date / time>: (Connections.c.714) invalid request - line -> sending Status 400 (with an IP address displayed that I think is my Desktop PC)
<date / time>: (Connection.s.c.714) unexpected TLS ClientHello on clear port (with an IP address displayed)

I did have a power failure this morning and the Raspberry Pi system is NOT on a UPS yet. So I'm sure the Raspberry Pi system crashed when the power failed, that may have caused file corruption.

Ideas?

[EricClaeys]

Please do the following:

sudo truncate -s 0 /var/log/lighttpd/error.log

then try accessing the WebUI and press F12 and in the area that pops up on the right side, go to the "Network" tab and press SHIFT-F5 which will force the browser to refresh the page. Assuming it fails, attach a screenshot of the browser window showing the URL, the error message, and the right side of the browser window.

One of the entries in the right side will have a 404 code and be in red.
See the example from my Pi:

Click on the red entry and you should see something like this:

Please attach a screenshot of the right side. Also, attach, do not copy/paste, /var/log/lighttpd/error.log.

There should be two screenshots and a file in your reply.

There is nothing private or secure in any of the information I'm requesting so please don't try to hide anything.

Whatever is causing this is likely related to the power failure. An HTML "400" status code means "bad request" which happens if a browser sends an invalid request.

[WEdward2]

For some reason hitting F12 in my copy of Microsoft Edge is not working, even though the setting option for Debugging is toggled on.

BUT I tried launching Google Chrome and entering the allsky URL and it launched fine from there. So the problem appears to be a Browser issue and not Allsky. I'll figure out how to force a browser page reset.

Thanks for the assistance!
Bill

[EricClaeys]

SHIFT-F5 should force a browser refresh. Try it in Edge to see if it helps.

[WEdward2]

Shift-F5 didn’t appear to do anything and I still can not access AllSky System via Edge Browser. FYI I did try rebooting everything (Windows and Raspberry Pi) earlier, which had no effect. William R. EdwardsOn Jun 30, 2025, at 6:02 AM, Eric Claeys ***@***.***> wrote: SHIFT-F5 should force a browser refresh. Try it in Edge to see if it helps. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[WEdward2]

error.log

[EricClaeys]

Try http://allsky.local/.
Unless you added a security certificate to your Pi, https won't work.

You can also try using the IP address of the Pi instead of its name: http://192.168.1.227

[WEdward2]

Yep I had already all three versions, none work. William R. EdwardsOn Jun 30, 2025, at 7:19 PM, Eric Claeys ***@***.***> wrote: Try http://allsky.local/. Unless you added a security certificate to your Pi, https won't work. You can also try using the IP address of the Pi instead of its name: http://192.168.1.227 —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[EricClaeys]

I assume you mean you tried http, https, and the IP address?
Can you send me an F12 screenshot where you used http, and that shows the request headers?

[WEdward2]

Correct, I had tried all three yesterday (http, https and IP address) and they all failed.
However, this morning when I attempted it works. I still had the browser session open from last night. Whatever the problem was, it cleared on its own. So this issue is resolved (whatever it was).

Thanks again for your assistance!
Bill