Foris - 500 Internal Server Error

Turris 1.x hardware Turris HW problems
1

Hello,

I have long lasting Foris problem. After attempt to deploy MOX WiFi AP (Turris MOX network boot) I am not able to use Foris web GUI. Browser response is as: 500 Internal Server Error. By the way I had DHCP and DNS problems before to, solved by Turris forum.

I am using Firefox web browser, latest version, cache cleared. Trying get some help from info@turris.cz went to nothing. Very long responses with no final result. Router and LuCI work fine, but there is no way, how to manage MOX AP and other extra services.

The device is Turris 1.x (blue box), microSD 8GB, Generic MAC80211 802.11abgn (radio1), Qualcomm Atheros QCA9880 802.11bgnac (radio0), new battery on board, Turris ver. 3.11.10.

Is anybody there with similar issue or even solution?

Josef

2

Hi all,
I have same issue after last update to v4.0.3.
First it throws 503 - Service not available , after refresh it’s 500.
I tried install foris-l10n-de and reboot router (Turris OS 4.0 beta3 is now released!) but it doesn’t help.

3

Hi Josef_Veskrna,

did you ever get to solve your issue?

I am experiencing the same issue, but have no idea on how to resolve this, apart from trying to reinstall everything.

On top I also have DNS issues, which stopped my initial attempts to try an update from the command line.

Best regards,
WhiteHatTux

4

Foris is served by “lighty” , so check
/etc/lighttpd/lighttpd.conf– you can validate config without reloading the service lighttpd -t -f <your config> ; some time ago change in syntax for including conf.d files cause Foris not to even start.
/etc/lighttpd/conf.d/*– check if you do not have any *-opkg files there, any leftovers cause lighty to not start correctly or at all.
/etc/lighttpd/modules.d/*– same here, additionally ensure that you do not have similar/same .load files (like 30-proxy.load and 20-proxy.load …) + there might be also replacement of some .load module, while you still have the old one present. (vhost vs simple_vhost, cgi vs fastcgi …)

any issues you can always sort it out using “schnapps” and just rollback to some working snapshot and reboot…

5

Thank you for the hint with lighttpd. It turned out that the mox-otp package was out of date and didn’t provide the command needed by lighttpd.
I don’t know how i got into that situation, but I circumvented my broken dns with a fixed dns entry of repo.turris.cz and was able to run an update that fixed the issue. Thank you again!