FTP stopped working last night ? after latest Big Sur update

[wx-watch]

My website hosted on IONOS has happily been working for several years. Last night WeatherCat stopped uploading anything via FTP. I have changed nothing in WeatherCat and I think looking at the logs this error preceded the last Big Sur update today.

The logs show that the FTP site cannot be found and the FTP upload times out, both AUX and normal - nothing has changed on my website and I have contacted IONOS and they say nothing has changed their end. I can contact my Website via FileZilla both via FTP on port 21 and SFTP via port 22. I know WeatherCat does not support SFTP.

Any suggestions? I have tried the FTPS option in WeatherCat but this does not work.

Any suggestions - it has been working perfectly up until last night!

[wx-watch]

**UPDATE*

It has suddenly started working again! No idea why - go figure - lets hope it stays working!!

https://www.wx-watch.co.uk

[wx-watch]

And it’s stopped again!!

If I reboot it seems to work for half an hour then stop.

I run Cumulus MX and PWS Dashboard on different devices and these work with the same credentials and these are working fine so I presume it id not an internet problem but a WeatherCat/Big Sur problem!

[ColdnFrosty]

No issues here with FTP
WC 3.1.2 and Big Sur 11.2.2

[elagache]

Dear wx-watch, ColdnFrosty, and WeatherCat troubleshooters,

My website hosted on IONOS has happily been working for several years. Last night WeatherCat stopped uploading anything via FTP.
. . . .

I am observing something somewhat similar with GoDaddy hosting.  I haven't changed my setup at all so the problem has to be in their end.  In the WeatherCat log I am seeing FTP errors like this:

Code: [Select]

2:50:39 PM 26-Feb-2021: FTP: curl: (28) FTP response timeout
curl: (18) server did not report OK, got 451
curl: (55) Send failure: Broken pipe
There is a list of all FTP error codes on Wikipedia:

https://en.wikipedia.org/wiki/List_of_FTP_server_return_codes

According to that error code 451 means: " Requested action aborted. Local error in processing."

According to the same Wikipedia article all errors in the 4xx range share this overall error condition:  'The command was not accepted and the requested action did not take place, but the error condition is temporary and the action may be requested again.'
 

Other web sources also suggest that this should be a transient error that will go away quickly.  However, I have been struggling with this for several days.  I gave up trying to contact GoDaddy about it because their technical support system is also swamped.  My suspicion is that there was an update to the open-source hosting framework used by many web hosting providers and this has some sort of a bug related to FTP.  Until the bug is fixed we are going to suffer with poor FTP performance.

However, that's just a suspicion.  Has anybody heard anything on the Internet grapevine that might explain this and perhaps overall Internet performance issues?  Perhaps a coordinated denial of service attack of some sort?

Such are da' conditions da' prevail these days on da' Internet . . . . . .

Edouard

[wx-watch]

Well its been working over night - I was feeding Steel Series Gauges from WeatherCat and uploading a realtimegaugesWC.txt every 20 seconds for this. I stopped that and all seems well.

I am feeding a Cumulus MX site https://longsuttonweather.co.uk and its realtime.txt file is updated every 20 seconds and it seems to be ok

https://longsuttonweather.co.uk/gauges.htm

So still not sure if its an internet problem or a WeatherCat/Big Sur/FTP Upload problem!

I also have a PWS Dashboard site at https://longsutton-weather.co.uk fed by Cumulus MX and again a realtime.txt file is being uploaded every 20seconds for this and it seems fine!

[wx-watch]

Further update.

It's still up - so it looks like WeatherCat uploading something in real time was too much - or the internet fixed itself.

I will leave it for a day or two and then perhaps add back in the every 20 second upload to see if it goes down again.

[Blicj11]

This is very weird behaviour. Not sure what to tell you. If it recurs, trying changing your 20-second feed to SteelSeries Gauges to 30 seconds.

[wx-watch]

I have increased the realtime update to one minute and turned off Wunderground Rapid Fire and it seems ok (for the moment)

As I said before the Big Sur Update and the latest WeatherCt update it was fine.