Mudi v2 cannot be configured anymore

I'm using my mudi v2 in an overseas trip. I need constant vpn connection to my server at home. I have already been using the setup for 2 weeks with no major issues (nothing that a reboot wouldn't fix).

Today the cellular connection suddenly dropped. The display showed "No service" while within the configuration portal it was saying "Connecting". I left it for a few minutes to see if it would fix on its own boy seeing that nothing changed, I decided to reboot from the web interface.

However while the connection (cellular + vpn) restablished, I noticed that the display would not show any mobile connection info (signal bars and carrier name). When I headed to the web interface, I noticed that it would not open (my browser would download a file with the filename 'download'). Since the connection was solid, I didn't bother and carried on.

A few hours later, I decided to power cycle the router. However, the behavior described above reproduced: no cellular info on display and no access to the web interface. SSH to the router still works and other than the fact I cannot access the web interface, everything works normally.

The problem, as you can imagine, is that I can't change any settings anyone. For instance I'm now in a hotel room and could connect to the hotel wifi as a repeater but cannot do it.

What troubleshooting steps I could take? Factory reset could be an option, but I would leave that as a last resort.

Update: the 'download' file contains the following text:

#!/usr/bin/lua
require "luci.cacheloader"
require "luci.sgi.cgi"
luci.dispatcher.indexcache = "/tmp/luci-indexcache"
luci.sgi.cgi.run()

Use ssh to enter the router terminal and enter this command

logread

Could you send me these logs?

It seems that the web server is down.

What was your firmware version?

It was the latest version (updated 2 weeks ago)

To be honest: It will be the fastest way to get the device working again; if it's not an hardware issue - which I doubt so far.

I factory reset and set it up again. All works now again.

A bit of a bummer that the device can't be a bit more reliable...