Unable to access webinterface Meteobridge pro. <solved?>

[denbolle]

Hi Forum,

I'm unable to access the webinterface of the meteobridge pro if I'm using the http://<meteobridge-ip> or http://<meteobridge-ip>/cgi-bin/meteobridge.cgi. The first sometime produces the "Meteobridge (Click to start manually)" link but after clicking the page keeps waiting.
I found this post in the forum (viewtopic.php?p=34271&hilit=webinterface#p34271) but there was no solution.

Device has been working since oct 2020 with 2 weatherstations.

The meteobridge seems to work :
Links that more or less work are

• http://<meteobridge-ip>/cgi-bin/livedate.cgi - produces current values consistent with the sensors after login.

• http://<meteobridge-ip>/cgi-bin/downloads.cgi - produces a list of templates after login. Clicking on one of the templates causes long waiting of the page without any action / reaction.

• After a reboot I see on the screen the templates working as I set them up. (temp, humidity, rain etc. are shown) Data is gathered and transferred to the different weather services.

Troubleshooting executed :

• - I can (sometimes) access via ssh to the meteobridge: then either I can execute one command or after the logon the screen stays black and no prompt is shown. Getting a login takes up to 1 minute. After that minute the logon won't be shown at all. For the Kubuntu nuc I had to update the SSH config to get access.

• Reset via the reset hole the passwords of the meteobridge webinterface and ssh back to defaults.

• Verified and hardcodes the network speed settings: fixed the port on the connected switch to 100Mb/fdx.

• Used different browsers (Edge / Firefox / Safari) on different systems (lockeddown Windows 10 work pc / private win 10 pc / Kubuntu 20 nuc) : all show the same behaviour: the link with meteobridge.cgi stalls and does not show the interface, the two others show (sometime after long waiting) the data or the download section.

• ping external site works : so dns / resolver etc. have no issues.

• ssh/top shows a load of max. 20%, so it's basically relaxed.

• ssh cat meteobridge.conf shows some output and then the process freezes.

So 'm stuck here. What commands can I give to kick start the meteobridge interface ? Can I "re-image" the unit? Do I have a hardware issue, and if so how to check ? I'm what reluctant to set the MB back to factory default because if there is a hardware defect I assume a risk of bricking the MB.

Any tips or remarks are welcome!
Please bear with me if I don't react directly, I'm working abroad and don't have always access to the MB.

[slrpwr]

It appears I have the same / similar issue. I can ssh into the RPi running Meteobridge, but can't access the web interface. It is updating sites correctly.

When I log in using an anonymous browser, it asks for my username / password and then is stuck displaying "Meteobridge" while attempting to load http://meteobridge.bollar.com/cgi-bin/meteobridge

[admin]

Please share "df -h" output, if you have SSH access. An accidentially filled up flash system can have similar side effects (just guessing). Giving me remote access will allow me to investigate deeper.

[denbolle]

Currently I've solved this issue so I'll list my steps I've done and my assumptions whats going on. Your mileage (will /may) vary. Data-loss will occur. Basically the MB will be forced to update to the latest version, without using the webinterface.

Assumption : corruption of meteobridge.cgi and/or other files used to display the interface.

Start situation :

• • Device is a MB - pro (red): updates weather sites, but internal interface shows nothing, stays either blank or only asks for user and id but then shows nothing.
  • Other encountered behavior after logon is the display of "Bad gateway" .
  • Device is connected with a cable. Wireless has never been used.
  • MB reacts on ping and (sometimes) on ssh access.
  • Reading from files show either content of the file or shows part of the file, the ssh process then stalls / hangs.
  • Device has not the most recent firmware (auto update disabled in the gui initially when it was still working.)
  • File system is not full.

Steps used :

• • Remove all cables.
  • Attach antenna.
  • Power device on.
  • Wait till boot is done: showing message "use SSID XXXXX to configure ip 192.168.1.1" on display.
  • Use 'reset' hole to select "set to factory default" on display - wait until this starts.
    • Important : this is the moment of the data-loss - history on the device.
  • Wait till boot is done: showing message "use SSID XXXXX to configure ip 192.168.1.1" on display.
  • Use wireless device to connect to MB wireless connection.
  • In browser of wireless device go to http://MB-IP/cgi-bin/luci This can also been shown in the default page shown stating that there is no internet connection.
  • Popup logon with default id / pw : meteobridge[
  • <hopefully> LuCi interface is shown: logon with root / meteobridge.
  • Select top Tab "Network"
  • Select sub tab "Wifi"
  • Use the "scan" button on the right to scan for networks.
    • ( --> eventually based on the wifi mac address assign a fixed ip for the MB in your dhcp server.)
  • Select your wifi network and select connect. Use known info to setup connection.
  • (--> I had to do this step several times as for unknown reason the MD didn't connect / stored the credentials. )

• • Reboot MB
  • Wait until boot is done, check if MB has wireless connection to normal network. (ping ip MB)
  • (--> her I waited : MB has been auto rebooting several times. )

After (all) reboots have been done and leds show some kind of "rest" try to open http://MB-IP/cgi-bin/luci.
If http://MB-IP/cgi-bin/luci can be opened try to open http://MB-IP/cgi-bin/meteobridge.cgi
(--> in my case this worked and I could reconfigure the MB after accepting the licence.)

Since the last config the MB has been working as normal (and ssh shows even faster response than before).

Steps above have been distilled from a lot of strange things I encountered, so the assumptions were a broken flashstorage, hardware defect, NIC defect etc.

[Gyvate]

What about a database backup before the factory reset (and a backup of the configuration) ?
Then the data loss will be minimised to the downtime of the system.

After clean restart restore configuration and backup ....

If the database was also corrupted one way or the other, this may be remedied by doing an export and re-import (rebuild), or, if necessary, using SQL commands to correct or eliminate faulty records...