Meteobridge Pro (Orange Front/Back) Stuck at FW1.4 landing page after factory reset

[JPB]

I plan to donate this Meteobridge as I have a newer one, so I did a typical "Before giving to someone else" factory reset. I wanted to see if it would start up again before I donated it, and it is stuck at the 1.4 Landing Page (it has not been used in years!).

It seems it is not downloading anything, I ssh'ed into it, and the only thing in the /var/log files is a solitary "Meteobridge started" message, and here is the output of the web page.

Any help is appreciated!

------------------

Meteobridge Landing Page (FW 1.4)
You got here, because Meteobridge application stack you wanted to access could not be loaded from the Internet. Most common reason for that is a bad network configuration of the Meteobridge device, that keeps the unit in endless fast blinking LED mode. From here you can do one of the following:

Wait: May be Meteobridge is still in the process of loading application stack from the Internet and it just needs a bit more time. You can give it a second try by this link
Cloud Simulator: You can setup a new network configuration for your device via this configurator in the cloud. You find details how to use this servive in the Meteobridge wiki, here.
Back to Defaults: When you have your Meteobridge in a cabled LAN environent with a DHCP server (mostly the router) up and running, you might be able to solve your networking issue by bringing your device back to standard network setup, by pressing the button until LED lights up for the first time. Unit will reboot in standard LAN DHCP client mode.
OpenWrt: As OpenWrt is fully operational in your device's flash storage and does not need to load an application stack from the Internet, you can start OpenWrt operation by this link. As OpenWrt is a very complex router setup, this is only recommended for experts, who are familar with OpenWrt and might be able to solve networking issues on that level.

To give you insight what your current networking setup is, you'll find some more networking details below. If you are not that deep into networking, just ignore.

IFCONFIG:
br-lan Link encap:Ethernet HWaddr C4:93:00:06:79:33
inet addr:192.168.0.102 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::c693:ff:fe06:7933/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12046 errors:0 dropped:0 overruns:0 frame:0
TX packets:1272 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:755812 (738.0 KiB) TX bytes:247601 (241.7 KiB)

eth0 Link encap:Ethernet HWaddr C4:93:00:06:79:33
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16582 errors:0 dropped:0 overruns:0 frame:0
TX packets:1325 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1772232 (1.6 MiB) TX bytes:252119 (246.2 KiB)
Interrupt:5

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:4248 errors:0 dropped:0 overruns:0 frame:0
TX packets:4248 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:225965 (220.6 KiB) TX bytes:225965 (220.6 KiB)


RESOLV.CONF:
search lan
nameserver 127.0.0.1

ROUTE:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.0.1 0.0.0.0 UG 0 0 0 br-lan
192.168.0.0 * 255.255.255.0 U 0 0 0 br-lan

NSLOOKUP:
Server: 127.0.0.1
Address 1: 127.0.0.1 localhost

Name: connect.meteobridge.com
Address 1: 2a01:4f9:6b:5423:6496::1 tau.meteobridge.com
Address 2: 65.108.64.96 tau.meteobridge.com

[admin]

I can't see any suspicious in the log. Does the problem still exist?