Welcome to the Cumulus Support forum.
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Cumulus MX V4 beta test release 4.0.0 (build 4019) - 03 April 2024
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
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Cumulus MX V4 beta test release 4.0.0 (build 4019) - 03 April 2024
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
running old standard website and the new MX website together
Moderator: daj
-
- Posts: 3
- Joined: Wed 11 Nov 2015 11:44 am
- Weather Station: ecowitt
- Operating System: win8.1
- Location: Naas
- Contact:
running old standard website and the new MX website together
Hi,
I updated Cumulus MX and t the moment i'm running the old website from cumulus 1.
My question is how can i run the old website and in the meantime have the new MX to update as well so i can change / develop it?
Regards,
Felix.
I updated Cumulus MX and t the moment i'm running the old website from cumulus 1.
My question is how can i run the old website and in the meantime have the new MX to update as well so i can change / develop it?
Regards,
Felix.
-
- Posts: 3254
- Joined: Sat 13 Aug 2011 9:33 am
- Weather Station: Ecowitt HP2551
- Operating System: Windows 10 64bit
- Location: Burnham-on-Sea
- Contact:
Re: running old standard website and the new MX website together
Set up a sub directory in your web server i.e. cumulusmx so that the web address is http://your webaddress/cumulusmx/index.html and the follow the instructions on setting up a new CumulusMX website in the Wiki. The FTP for CumulusMX will point to whatever your Cumulus 1 FTP points to plus /cumulusmx
That way you will have two websites
http://your webaddress/index.html and
http://your webaddress/cumulusmx/index.html
That way you will have two websites
http://your webaddress/index.html and
http://your webaddress/cumulusmx/index.html
-
- Posts: 884
- Joined: Sat 16 Jul 2016 11:59 pm
- Weather Station: Davis VP2+ & GW1000 (Standalone)
- Operating System: Win10 Pro / rPi Buster
- Location: Australia
Re: running old standard website and the new MX website together
I'm doing something similar here,
Existing site is http://weather.inverellit.com/index.htm
and new site is http://weather.inverellit.com/new/index.htm
On the existing site I've also pointed "Now" on the index.htm to the new site with <a href="new/index.htm" target="_blank">now</a>,
So if I click on "Now" at the main page it opens the new site in a new tab.
I've also put a .htaccess file in the /new directory, so I don't need to upload all the data files to /new as well as the level above.
Not sure if that's to complex for what you want.
.htaccess looks like this.....
(In /new not the folder above).
Cheers.
Existing site is http://weather.inverellit.com/index.htm
and new site is http://weather.inverellit.com/new/index.htm
On the existing site I've also pointed "Now" on the index.htm to the new site with <a href="new/index.htm" target="_blank">now</a>,
So if I click on "Now" at the main page it opens the new site in a new tab.
I've also put a .htaccess file in the /new directory, so I don't need to upload all the data files to /new as well as the level above.
Not sure if that's to complex for what you want.
.htaccess looks like this.....
(In /new not the folder above).
Code: Select all
# This prevents web browsers or spiders from seeing your .htaccess directives:
<Files .htaccess>
deny from all
</Files>
RewriteEngine On
RewriteRule ^realtimegauges.txt$ http://weather.inverellit.com/realtimegauges.txt [NC,L]
RewriteRule ^airquality.json$ http://weather.inverellit.com/airquality.json [NC,L]
RewriteRule ^alldailydegdaydata.json$ http://weather.inverellit.com/alldailydegdaydata.json [NC,L]
RewriteRule ^alldailyhumdata.json$ http://weather.inverellit.com/alldailyhumdata.json [NC,L]
RewriteRule ^alldailypressdata.json$ http://weather.inverellit.com/alldailypressdata.json [NC,L]
RewriteRule ^alldailyraindata.json$ http://weather.inverellit.com/alldailyraindata.json [NC,L]
RewriteRule ^alldailysolardata.json$ http://weather.inverellit.com/alldailysolardata.json [NC,L]
RewriteRule ^alldailytempdata.json$ http://weather.inverellit.com/alldailytempdata.json [NC,L]
RewriteRule ^alldailywinddata.json$ http://weather.inverellit.com/alldailywinddata.json [NC,L]
RewriteRule ^alltempsumdata.json$ http://weather.inverellit.com/alltempsumdata.json [NC,L]
RewriteRule ^availabledata.json$ http://weather.inverellit.com/availabledata.json [NC,L]
RewriteRule ^dailyrain.json$ http://weather.inverellit.com/dailyrain.json [NC,L]
RewriteRule ^dailytemp.json$ http://weather.inverellit.com/dailytemp.json [NC,L]
RewriteRule ^graphconfig.json$ http://weather.inverellit.com/graphconfig.json [NC,L]
RewriteRule ^humdata.json$ http://weather.inverellit.com/humdata.json [NC,L]
RewriteRule ^pressdata.json$ http://weather.inverellit.com/pressdata.json [NC,L]
RewriteRule ^raindata.json$ http://weather.inverellit.com/raindata.json [NC,L]
RewriteRule ^solardata.json$ http://weather.inverellit.com/solardata.json [NC,L]
RewriteRule ^sunhours.json$ http://weather.inverellit.com/sunhours.json [NC,L]
RewriteRule ^tempdata.json$ http://weather.inverellit.com/tempdata.json [NC,L]
RewriteRule ^wdirdata.json$ http://weather.inverellit.com/wdirdata.json [NC,L]
RewriteRule ^websitedata.json$ http://weather.inverellit.com/websitedata.json [NC,L]
RewriteRule ^winddata.json$ http://weather.inverellit.com/winddata.json [NC,L]
:Now: :Today/Yesterday:
Main Station Davis VP2+ Running Via Win10 Pro.
Secondary Stations, Ecowitt HP2551/GW1000 Via rPi 3 & 4 Running Buster GUI.
:Local Inverell Ecowitt Station: :Remote Ashford Ecowitt Station:
Main Station Davis VP2+ Running Via Win10 Pro.
Secondary Stations, Ecowitt HP2551/GW1000 Via rPi 3 & 4 Running Buster GUI.
:Local Inverell Ecowitt Station: :Remote Ashford Ecowitt Station:
-
- Posts: 3
- Joined: Wed 11 Nov 2015 11:44 am
- Weather Station: ecowitt
- Operating System: win8.1
- Location: Naas
- Contact:
Re: running old standard website and the new MX website together
Thank you All,
It is all working now, i have both websites running simultaneously as per all your instructions.
New: https://prosperousweather.wbt-pc.com/cu ... /index.htm
Old: https://prosperousweather.wbt-pc.com/
It is all working now, i have both websites running simultaneously as per all your instructions.
New: https://prosperousweather.wbt-pc.com/cu ... /index.htm
Old: https://prosperousweather.wbt-pc.com/
- HansR
- Posts: 5965
- Joined: Sat 20 Oct 2012 6:53 am
- Weather Station: GW1100 (WS80/WH40)
- Operating System: Raspberry OS/Bookworm
- Location: Wagenborgen (NL)
- Contact:
Re: running old standard website and the new MX website together
But you have https in the URL and apparently no certificate: Secure Connection Failedfelixd74 wrote: ↑Fri 25 Feb 2022 1:10 pm Thank you All,
It is all working now, i have both websites running simultaneously as per all your instructions.
New: https://prosperousweather.wbt-pc.com/cu ... /index.htm
Old: https://prosperousweather.wbt-pc.com/
Code: Select all
An error occurred during a connection to prosperousweather.wbt-pc.com. A required TLS feature is missing.
Error code: MOZILLA_PKIX_ERROR_REQUIRED_TLS_FEATURE_MISSING
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the web site owners to inform them of this problem.
Hans
https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
-
- Posts: 3254
- Joined: Sat 13 Aug 2011 9:33 am
- Weather Station: Ecowitt HP2551
- Operating System: Windows 10 64bit
- Location: Burnham-on-Sea
- Contact:
Re: running old standard website and the new MX website together
Hans I am not getting that in Edge, both sites are displaying the lock and the detail shows the certificate.
This site has a valid certificate, issued by a trusted authority.
- HansR
- Posts: 5965
- Joined: Sat 20 Oct 2012 6:53 am
- Weather Station: GW1100 (WS80/WH40)
- Operating System: Raspberry OS/Bookworm
- Location: Wagenborgen (NL)
- Contact:
Re: running old standard website and the new MX website together
Hmm... indeed seems to be a FF problem. Chrome is working fine.
[EDIT:]
For anybody having the same issue with FF, the following worked for me:
Code: Select all
(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful.
(2) In the search box above the list, type or paste ocsp and pause while the list is filtered
(3) Double-click the security.ssl.enable_ocsp_must_staple preference to switch the value from true to false
Hans
https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
-
- Posts: 129
- Joined: Sun 21 Aug 2011 2:26 am
- Weather Station: Davis Vantage Vue
- Operating System: Windows 10
- Location: Sydney. Australia
- Contact:
Re: running old standard website and the new MX website together
I thought I wold try this rather than using Extra web Files. I put the .htaccess file in C1 the subdirectory weatherMX without any success using this code sample.Phil23 wrote: ↑Fri 25 Feb 2022 1:33 am I'm doing something similar here,
Existing site is http://weather.inverellit.com/index.htm
and new site is http://weather.inverellit.com/new/index.htm
On the existing site I've also pointed "Now" on the index.htm to the new site with <a href="new/index.htm" target="_blank">now</a>,
So if I click on "Now" at the main page it opens the new site in a new tab.
I've also put a .htaccess file in the /new directory, so I don't need to upload all the data files to /new as well as the level above.
Not sure if that's to complex for what you want.
.htaccess looks like this.....
(In /new not the folder above).
Cheers.Code: Select all
# This prevents web browsers or spiders from seeing your .htaccess directives: <Files .htaccess> deny from all </Files> RewriteEngine On RewriteRule ^realtimegauges.txt$ http://weather.inverellit.com/realtimegauges.txt [NC,L] RewriteRule ^airquality.json$ http://weather.inverellit.com/airquality.json [NC,L] RewriteRule ^alldailydegdaydata.json$ http://weather.inverellit.com/alldailydegdaydata.json [NC,L] RewriteRule ^alldailyhumdata.json$ http://weather.inverellit.com/alldailyhumdata.json [NC,L] RewriteRule ^alldailypressdata.json$ http://weather.inverellit.com/alldailypressdata.json [NC,L] RewriteRule ^alldailyraindata.json$ http://weather.inverellit.com/alldailyraindata.json [NC,L] RewriteRule ^alldailysolardata.json$ http://weather.inverellit.com/alldailysolardata.json [NC,L] RewriteRule ^alldailytempdata.json$ http://weather.inverellit.com/alldailytempdata.json [NC,L] RewriteRule ^alldailywinddata.json$ http://weather.inverellit.com/alldailywinddata.json [NC,L] RewriteRule ^alltempsumdata.json$ http://weather.inverellit.com/alltempsumdata.json [NC,L] RewriteRule ^availabledata.json$ http://weather.inverellit.com/availabledata.json [NC,L] RewriteRule ^dailyrain.json$ http://weather.inverellit.com/dailyrain.json [NC,L] RewriteRule ^dailytemp.json$ http://weather.inverellit.com/dailytemp.json [NC,L] RewriteRule ^graphconfig.json$ http://weather.inverellit.com/graphconfig.json [NC,L] RewriteRule ^humdata.json$ http://weather.inverellit.com/humdata.json [NC,L] RewriteRule ^pressdata.json$ http://weather.inverellit.com/pressdata.json [NC,L] RewriteRule ^raindata.json$ http://weather.inverellit.com/raindata.json [NC,L] RewriteRule ^solardata.json$ http://weather.inverellit.com/solardata.json [NC,L] RewriteRule ^sunhours.json$ http://weather.inverellit.com/sunhours.json [NC,L] RewriteRule ^tempdata.json$ http://weather.inverellit.com/tempdata.json [NC,L] RewriteRule ^wdirdata.json$ http://weather.inverellit.com/wdirdata.json [NC,L] RewriteRule ^websitedata.json$ http://weather.inverellit.com/websitedata.json [NC,L] RewriteRule ^winddata.json$ http://weather.inverellit.com/winddata.json [NC,L]
Code: Select all
# This prevents web browsers or spiders from seeing your .htaccess directives:
<Files .htaccess>
deny from all
</Files>
RewriteEngine On
RewriteRule ^realtimegauges.txt$ https://blazingcomet.com/weatherMX/realtimegauges.txt [NC,L]
RewriteRule ^airquality.json$ https://blazingcomet.com/weatherMX/airquality.json [NC,L]
RewriteRule ^alldailydegdaydata.json$ https://blazingcomet.com/weatherMX/alldailydegdaydata.json [NC,L]
RewriteRule ^alldailyhumdata.json$ https://blazingcomet.com/weatherMX/alldailyhumdata.json [NC,L]
RewriteRule ^alldailypressdata.json$ https://blazingcomet.com/weatherMX/alldailypressdata.json [NC,L]
RewriteRule ^alldailyraindata.json$ https://blazingcomet.com/weatherMX/alldailyraindata.json [NC,L]/code]
-
- Posts: 884
- Joined: Sat 16 Jul 2016 11:59 pm
- Weather Station: Davis VP2+ & GW1000 (Standalone)
- Operating System: Win10 Pro / rPi Buster
- Location: Australia
Re: running old standard website and the new MX website together
Did you ultimately get the rewrites to work?
In my case the simple test I used to see if it was working was to attempt to open:-
http://weather.inverellit.com/new/realtimegauges.txt which does not exist,
but redirects & opens http://weather.inverellit.com/realtimegauges.txt
Should be able to duplicate that in your case.
In my case the simple test I used to see if it was working was to attempt to open:-
http://weather.inverellit.com/new/realtimegauges.txt which does not exist,
but redirects & opens http://weather.inverellit.com/realtimegauges.txt
Should be able to duplicate that in your case.
:Now: :Today/Yesterday:
Main Station Davis VP2+ Running Via Win10 Pro.
Secondary Stations, Ecowitt HP2551/GW1000 Via rPi 3 & 4 Running Buster GUI.
:Local Inverell Ecowitt Station: :Remote Ashford Ecowitt Station:
Main Station Davis VP2+ Running Via Win10 Pro.
Secondary Stations, Ecowitt HP2551/GW1000 Via rPi 3 & 4 Running Buster GUI.
:Local Inverell Ecowitt Station: :Remote Ashford Ecowitt Station:
-
- Posts: 129
- Joined: Sun 21 Aug 2011 2:26 am
- Weather Station: Davis Vantage Vue
- Operating System: Windows 10
- Location: Sydney. Australia
- Contact:
Re: running old standard website and the new MX website together
Not as yet. I may not have it right though, obviously.
From my understanding in my case, the .htaccess file is in the same directory that MX sends the files to which is the parent directory "weatherMX" and the .htaccess file rewrites the file to the subdirectory "C1" with as an example:
I also tried using the full address with out success.
I'm also not clear on what triggers the .htaccess to do its thing.
From my understanding in my case, the .htaccess file is in the same directory that MX sends the files to which is the parent directory "weatherMX" and the .htaccess file rewrites the file to the subdirectory "C1" with as an example:
Code: Select all
RewriteRule ^realtimegauges.txt$ /C1/realtimegauges.txt [NC,L]
Code: Select all
RewriteRule ^realtimegauges.txt$ https://blazingcomet.com/weatherMX/C1/realtimegauges.txt [NC,L]
- mcrossley
- Posts: 12766
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: running old standard website and the new MX website together
I've not followed this closely, but don't you want the htaccess in the new folder pointing back to root folder where you say the file is being uploaded to?
-
- Posts: 129
- Joined: Sun 21 Aug 2011 2:26 am
- Weather Station: Davis Vantage Vue
- Operating System: Windows 10
- Location: Sydney. Australia
- Contact:
Re: running old standard website and the new MX website together
I not sure I tried that way in an earlier post with a number of variations without success
Code: Select all
RewriteRule ^realtimegauges.txt$ https://blazingcomet.com/weatherMX/realtimegauges.txt [NC,L]
- mcrossley
- Posts: 12766
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: running old standard website and the new MX website together
Do you have rewrite rules enabled on your web server? The mod_rewrite module needs to be enabled in the web server config. (details vary depending on the web server software)
-
- Posts: 2477
- Joined: Wed 08 Jun 2011 11:19 am
- Weather Station: Davis Vantage Pro 2 + Ecowitt
- Operating System: GNU/Linux Ubuntu 22.04 LXC
- Location: Alcaston, Shropshire, UK
- Contact:
Re: running old standard website and the new MX website together
If it wasn't enabled then I'm sure the web server would refuse to start. It could be the case that the setting that enables use of .htaccess files isn't correct/disabled. If that was the case then the .htaccess file instructions would be ignored. It would be useful to look in the server log file to see what response was logged for the request for realtimegauges.txt. If it was a 404 response code then the .htaccess file is likely being ignored.
-
- Posts: 129
- Joined: Sun 21 Aug 2011 2:26 am
- Weather Station: Davis Vantage Vue
- Operating System: Windows 10
- Location: Sydney. Australia
- Contact:
Re: running old standard website and the new MX website together
OK, in CPanel Error logs when I change the name of the .htaccess file I get:
I'm guessing from that the htaccess is enabled?
Code: Select all
2022-08-04 10:37:37.890081 [INFO] [597543] [T0] [HTAccess] Configuration file [/home/blazingc/public_html/weatherMX/C1/.htaccess] has been removed.