I have a problem with my Meteotemplate website going off line. I use a Davis Vantage Vue which is hardwired to a Meteobridge TP-Link version. The Meteobridge transfers to website and normally all works well. However on 30th April 26 at 11:35 it just stopped sending for no apparent reason. The normal fix for anything like this is to reboot the Meteobridge but in this instance it did not work.
I got the following error from Meteobridge: 'meteotemplate authorised via website'
Probably against my better judgement I changed the 'Update' password in Meteotemplate and the error changed to 'Meteotemplate'. I am pretty sure from the documentation that this is the correct password for Meteobridge, if it isn't I have probably made things worse.
All of the password checks on Meteotemplate CP work. Meteobridge is working with Wunderground which indicates no error there
The odd thing is that every now and again the website header show data that more or less correlates with the correct weather data. This makes me think that data is getting through to the website but is not being written to the database
So I am at a bit of a loss so I would be grateful for any suggestions
Thank
MartinB
Problem outage
-
martinb978
- Newbie

- Posts: 4
- Joined: Mon Jan 27, 2020 10:38 pm
- Station model: Davis Vantage Vue
- Software: MeteoBridge
-
SteveParry
- Observer

- Posts: 15
- Joined: Thu Dec 26, 2019 7:16 am
- Location: Samford Valley, Australia
- Station model: Davis Vantage Vue
- Software: CumulusMX
- Contact:
Re: Problem outage
Hi Martin.
I have had similar issues with MeteoTemplate 19 for many months, but I use CumulusMX not MeteoBridge.
Offline periods range from less than a minute to several hours. The start trigger and end trigger of the offline periods are unknown, just that the sire disolays Offline (which we know from the code is because no realtime.txt has been received).
No data is uploaded during the offline period (realtime.txt file date/time stamp doesn't change).
Using CumulusMX FTPLogging and from the main error file, the remote host web server returns error 552 - Disk full message.
(For example "2026-05-03 15:42:07 - RealtimeFtpWatchDog: Base exception follows - Code: 552 Message: Disk full - please upload later").
My Hosting provider is still investigating but appears baffled at the moment, as there are no quota constraints apparent.
This may or may not be the same as what you are experiencing, but hope it helps.
Once the site comes back online, MeteoTemplate continues using the latest realtime.txt data, plus what it calculates from its own SQL database, which is why it appears to be OK when it comes back online.
I wish there was a utility for CumulusMX that processed all the local stored data files and uploaded records that were missing from the web SQL database. Finding the missing records and manually uploading them is very tedious.
Cheers
...Steve
I have had similar issues with MeteoTemplate 19 for many months, but I use CumulusMX not MeteoBridge.
Offline periods range from less than a minute to several hours. The start trigger and end trigger of the offline periods are unknown, just that the sire disolays Offline (which we know from the code is because no realtime.txt has been received).
No data is uploaded during the offline period (realtime.txt file date/time stamp doesn't change).
Using CumulusMX FTPLogging and from the main error file, the remote host web server returns error 552 - Disk full message.
(For example "2026-05-03 15:42:07 - RealtimeFtpWatchDog: Base exception follows - Code: 552 Message: Disk full - please upload later").
My Hosting provider is still investigating but appears baffled at the moment, as there are no quota constraints apparent.
This may or may not be the same as what you are experiencing, but hope it helps.
Once the site comes back online, MeteoTemplate continues using the latest realtime.txt data, plus what it calculates from its own SQL database, which is why it appears to be OK when it comes back online.
I wish there was a utility for CumulusMX that processed all the local stored data files and uploaded records that were missing from the web SQL database. Finding the missing records and manually uploading them is very tedious.
Cheers
...Steve
-
martinb978
- Newbie

- Posts: 4
- Joined: Mon Jan 27, 2020 10:38 pm
- Station model: Davis Vantage Vue
- Software: MeteoBridge
Re: Problem outage
Hi Steve
Thanks for getting back to me. It's been a real mystery. All I can say is that I have worked out the following;
api.php is being read as a messages comes back about incorrect use of admin password that is part of the script of that file. Only used that password as a test but the error message is correct
As far as I can see data should be written but does not write to the files apiCache.txt, apiLog.txt,latestApiCache.txt
Data is written to this file meteotemplateLive.txt so am at a complete loss. I have asked my web host to do a restore back to the last known update to see if it kicks in again
Failing that a complete reinstall or see if Jachym has any advice
Thanks for your message and if anyone else has any advice it will be very welcome
Thanks for getting back to me. It's been a real mystery. All I can say is that I have worked out the following;
api.php is being read as a messages comes back about incorrect use of admin password that is part of the script of that file. Only used that password as a test but the error message is correct
As far as I can see data should be written but does not write to the files apiCache.txt, apiLog.txt,latestApiCache.txt
Data is written to this file meteotemplateLive.txt so am at a complete loss. I have asked my web host to do a restore back to the last known update to see if it kicks in again
Failing that a complete reinstall or see if Jachym has any advice
Thanks for your message and if anyone else has any advice it will be very welcome
-
martinb978
- Newbie

- Posts: 4
- Joined: Mon Jan 27, 2020 10:38 pm
- Station model: Davis Vantage Vue
- Software: MeteoBridge
Re: Problem outage
The problem eventually became unsolvable. The people at my web provider were very good but nothing they could suggest fixed the problem. Luckily web page and db is backed up on daily basis so restored from the last good date and it started working. If it happens again with the same symptoms I will do another restore and save the loss of data which this time was 5 days