Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
From build 3044 the development baton passed to Mark Crossley. Mark has been responsible for all the Builds since. He has made the code available on GitHub. It is Mark's hope that others will join in this development, but at the very least he welcomes your ideas for future developments (see Cumulus MX Development suggestions).
PaulMy wrote: ↑Mon 13 Nov 2023 1:02 am
Hi again,
Just saw your capture after I posted, and you should remove the public_html/ from your Destination filename. And the same in NOAA settings if you upload those.
Enjoy,
Paul
I'm sure I need something else other than what you suggest for the path. Perhaps this below will help you advise me what I need to do with the extra files set up.
My directory setup is:
All files for my Saratoga site are contained in the public_html folder on the server.
All files for my Cumulus site are contained in a folder named cumx in the public_html folder.
Similarly, all files for my Cumulus MX UI site are contained in a folder named mxtestv2 in the public_html folder.
Similarly, all files for my Cumulus HWS site are contained in a folder named pwsWD in the public_html folder.
griffo42 wrote: ↑Mon 13 Nov 2023 7:01 am
My directory setup is:
All files for my Saratoga site are contained in the public_html folder on the server.
All files for my Cumulus site are contained in a folder named cumx in the public_html folder.
Similarly, all files for my Cumulus MX UI site are contained in a folder named mxtestv2 in the public_html folder.
Similarly, all files for my Cumulus HWS site are contained in a folder named pwsWD in the public_html folder.
Cumulus site works perfectly: the other 3 do not.
The question is: where is your upload.php located?
griffo42 wrote: ↑Mon 13 Nov 2023 7:01 am
My directory setup is:
All files for my Saratoga site are contained in the public_html folder on the server.
All files for my Cumulus site are contained in a folder named cumx in the public_html folder.
Similarly, all files for my Cumulus MX UI site are contained in a folder named mxtestv2 in the public_html folder.
Similarly, all files for my Cumulus HWS site are contained in a folder named pwsWD in the public_html folder.
Cumulus site works perfectly: the other 3 do not.
The question is: where is your upload.php located?
My upload.php is located in the cumx folder cited above.
griffo42 wrote: ↑Mon 13 Nov 2023 7:01 am
My directory setup is:
All files for my Saratoga site are contained in the public_html folder on the server.
All files for my Cumulus site are contained in a folder named cumx in the public_html folder.
Similarly, all files for my Cumulus MX UI site are contained in a folder named mxtestv2 in the public_html folder.
Similarly, all files for my Cumulus HWS site are contained in a folder named pwsWD in the public_html folder.
Cumulus site works perfectly: the other 3 do not.
The question is: where is your upload.php located?
My upload.php is located in the cumx folder cited above.
OK, that's the issue.
From there you define all your uploads relative to that directory. So if you want to upload a file to the webroot (public_html) you tell CMX to upload it to ../ so your CUtags-new.php upload destination becomes
NOTE if the PHP upload procedure complains you step out of the permitted directory structure I would advise to put upload.php in the public_html and upload everything from there. Since all directories are under public_html you stay withing the permitted tree. In that case your upload for CUtags would become:
@HansR
After, what I thought was following your advice very carefully, i have been unable to get the PHP uploads working, I have now reverted to FTP uploads.
2023-12-09 01:51:47.087 PHP[83]: Sending via GET
2023-12-09 01:51:47.097 PHP[83]: Uploading to realtimegauges.txt
2023-12-09 01:51:47.097 PHP[83]: Sending via GET
2023-12-09 01:51:47.097 PHP[83]: Uploading to realtime.xml
2023-12-09 01:51:47.097 PHP[83]: Sending via POST
2023-12-09 01:51:47.097 PHP[83]: Upload to realtime.txt: Response code = 422: 422
2023-12-09 01:51:47.097 PHP[83]: Upload to realtime.txt: Response text follows:
Error: TimeStamp is out of date
Data TS = 1702086707
Server TS = 1702083845
2023-12-09 01:51:47.108 PHP[83]: Upload to realtimegauges.txt: Response code = 422: 422
2023-12-09 01:51:47.108 PHP[83]: Upload to realtimegauges.txt: Response text follows:
Error: TimeStamp is out of date
Data TS = 1702086707
Server TS = 1702083845
2023-12-09 01:51:47.162 PHP[83]: Upload to realtime.xml: Response code = 422: 422
2023-12-09 01:51:47.162 PHP[83]: Upload to realtime.xml: Response text follows:
Error: TimeStamp is out of date
Data TS = 1702086707
Server TS = 1702083845
Stop using the GET for small files by disabling it in the Advanced settings, worked for me on my site. Makes no difference that I can see to the upload, but the occasional Get failures disappeared.
mcrossley wrote: ↑Sat 09 Dec 2023 11:45 am
Your server time is 138 seconds ahead of your MX time. One of them is not synchronising it's clock.
I contacted my host and told them it stopped working at 01:25. I got this back..
I have switched the PHP version to 7.4 and also disabled the following code in the php.ini file which did the trick.
zlib.output_compression = On
zlib.output_handler = ob_gzhandler
It was already on PHP 7.4 and I hadn't changed any settings
mcrossley wrote: ↑Sat 09 Dec 2023 11:45 am
Your server time is 138 seconds ahead of your MX time. One of them is not synchronising it's clock.
I contacted my host and told them it stopped working at 01:25. I got this back..
I have switched the PHP version to 7.4 and also disabled the following code in the php.ini file which did the trick.
zlib.output_compression = On
zlib.output_handler = ob_gzhandler
It was already on PHP 7.4 and I hadn't changed any settings
Totally irrelevant afaics, the error messages are clear, the script had compared the time stamp from MX and the server time and found them adrift - nothing to do with compression.