Cumulus Support

Started seeing some SFTP errors - I use SFTP with a password

Error connecting sftp - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

https://longsuttonweather.co.uk - running on a Windows 10 Mini PC

This - https://longsutton-weather.co.uk is also powered by Cumulus MX running on a Raspberry Pi and I am seeing no SFTP errors there.

I also run

https://m0xgp.co.uk/weewx/
https://wx-watch.co.uk
https://wx-watch.co.uk/weathercat/custom/steel/
https://wx-watch.co.uk/weathercat/custom/pws/index.php

And no errors here either (PS is this Weather OverKill?)

Hmm, lately it has been Linux/mono causing SFTP problems.

Any Windows update applied when the problems started? Cumulus updated?

Local Windows firewall issue on your mini-pc?

Nothing special installed on the Windows PC - just any routine updates. It has been running perfectly since middle of last year. Firewall not changed. The only thing changed was the 30th December Update

Immediately after a failure I can do a manual SFTP upload and it works perfectly every time.

Odd that the manual FTP works, it calls exactly the same routine as the interval timer.

I am reverting the SFTP component in the next release to the previous version which seems to be more reliable - especially on Linux. It will lose some key file compatibility, but should be better overall.

No more errors since the latest update.

Thanks for letting me know.

SFTP now works for me with latest version (B3100).

I also had to remove the leading "/" character in the remote name of my extra files. FTP and SFTP uses this differently.
Many thanks to mcrossley.

For info - had errors this morning with SFTP which seem to have resolved itself without my intervention. My webhosting company don't show systems issues during the time period and infer its not caused by their network.

I didn't see this kind of error with the previous SFTP version either.
Running MX release 3.9.6 (build 3101)
Copy of MXdiags errors attached.

If there was no problem with the server, then it looks like a network problem. No comms at all from that log snippet.