Weather station website not updating

[geoffw]

http://www.winterman.org.uk/weather/index.htm

I’ve been using Cumulus MX for a number of years but haven’t upgraded to the latest version.

After a major update on the Windows 10 laptop that is linked to my weather station, on Wednesday evening, the station’s data ceased to update Cumulus on my website.
For the first time since I set up MX I have had to try to run the built in web interface by running the URL http://localhost:8998/ on the laptop linked to the weather station.

Unfortunately, I am getting the error message: “HTTP error 403: The service is not available!”

So, I’m stuck at the moment. Suggestions would be appreciated!

[HansR]

And what if you use the ip address of the RPi iso localhost?

[ExperiMentor]

Agree with Hans. But that's just the start of your investigations.

Explanation: 'localhost' means 'on this machine', so you've asked your laptop to look for the Cumulus web interface on itself. Is this laptop the computer that is running CumulusMX (you haven't quite said that). It is better to write "http://192.168.1.XXX:8998" or similar, ie spelling out the IP address of the computer that is running Cumulus

Another possibility is that you didn't ever turn on the webserver on the computer running Cumulus.
Or that you set it to use a port other than the default 8998.

If you need more help, please tell us:
What weather station?
What device is CumulusMX running on? (I see from your webpage that it is running Cumulus build 3043, which is the last version before Steve took over updates ... very old)
How are weather station and computer connected?
What do you mean by 'major update on the Windows 10 laptop'? (something you did, or the usual monthly Microsoft Windows update, or the 6-monthly Windows version update?)

[HansR]

@ExperiMentor:
Yes, that RPi was indeed quite an unreasonable, I'd even say irrational, assumption

[geoffw]

Hi All

Many thanks. the problems was nothing to do with CumulusMX, thank goodness. Localhost would not work, but as suggested finding and using the IP address showed that Cumulus was communicating with the weather station - though not to my website.

I have recently changed my website host and what I didn't realise was I needed to "unlock" the FTB manually in the sites control panel - and it can be left unlocked for up to 28 days. It is now reading "FTP is currently unlocked and will be automatically locked in 27 days, 23 hours, 48 minutes." Looks like I've got to remember to do this once a month!!!

One more thought: To view MX in another machine on my home network I should be able to do this my typing "http://192.168.1.XXX:8998" into my browser - "XXX" in the IP address of the machine connected to the weather station. That isn't working for me.

[HansR]

Good. Not sure what you mean by unlock.

So that would be a Win10 to a Win10 machine? Or some Android tablet to Win10. Anyway, you will have to give a machine permission that other machines can see it and talk to it. Not sure that would be standard on. Anyway, yours to find out and deal with your own network. At least CMX is doing fine

[mcrossley]

I have recently changed my website host and what I didn't realise was I needed to "unlock" the FTB manually in the sites control panel - and it can be left unlocked for up to 28 days. It is now reading "FTP is currently unlocked and will be automatically locked in 27 days, 23 hours, 48 minutes." Looks like I've got to remember to do this once a month!!!

That is unusual, can you tell us the web hosting company so that other people who start using it can be made aaware.

One more thought: To view MX in another machine on my home network I should be able to do this my typing "http://192.168.1.XXX:8998" into my browser - "XXX" in the IP address of the machine connected to the weather station. That isn't working for me.

Normally a firewall/threat protection software issue somewhere. Either on the machine running Cumulus, or your router would be favourite, but check the client machine too, for port 8998 being blocked.