Sensor FTP

Hi,

We are experiencing exactly the same issue. All our FTP sensors on several Remote Probes stopped working after the update to 22.2.77.2204+.

Hi Florian and Gilian,

This is a known issue in the mentioned release. We are already working on a solution for this.
Disabling TLS and use the option "Do not use transport-level security" would be the workaround. I can understand that this might be not an option for you but this is the only thing I can offer right now. Besides of a downgrade to the older version.

This issue occurs from a change regarding StartTLS connectivity which we mentioned in the release notes for this version.

Kind regards

Felix Wiesneth - Team Technical Support

Hello Felix Wiesneth [Paessler Support],

Thank you for your answer, I think I'll wait for you to fix the problem in a future update.

I tried the settings you recommended but it didn't work and I haven't downgraded yet.

Same for our PRTG instance. No working FTP sensor anymore running 22.2.77.2204+

Hi there,

We plan to fix this within version 22.x.78.

Kind regards

Felix Wiesneth - Team Technical Support

Hello Felix,

thanks for the update. Is there an ETA for this version?

Hi there,

We plan to release the stable version somewhere beginning of August. Since we need to do extensive testing in before, I can't give you a date exactly.

Kind regards

Felix Wiesneth - Team Tech Support

The ftp endpoint we are monitoring does not support ssl or tls, so I changed the configuration to "Do not use transport-level security" instead of "Use transport-level security if available" but this work around isn't working. It is still failing with the error message, "Start SSL negotiation command failed. (SSL/TLS not available)".

Hi Jason,

I'm afraid you will need to wait until the release of the next version. We are planning to release this version soon.

Kind regards

Felix Wiesneth - Team Technical Support

Hi. I've been having the same issue. I just updated to version 22.x.78 but the FTP sensors are still down. One is saying Login or password incorrect! (SSL/TLS not available) and the others are saying Login incorrect. (SSL/TLS not available). I've tried changing to Do not use transport-level security but that did not solve the issue.

Same here. After the update to 22.3.78.1873 the ftpsensor remains down with message: Log on attempt by user ANONYMOUS rejected. (SSL/TLS not available). I also tried with both settings "Use transport-level security if available" and "Do not use transport-level security" enabled.

Hi.

Same issue of mkurbel.I update my PRTG 22.3.78.1873+ but I have an error on my Sensor Login incorrect. (SSL/TLS not available) .

We wait next update maybe ?

Hello,
We are still facing some problems with these sensors. We are currently on the way to releasing a hotfix while we wait for version .79 Please stay tuned for this release, and feel free to open a ticket in case you want more follow-up.

Hello Craw
I'm sorry for the inconvenience. As mentioned before, We are currently on the way to releasing a hotfix while we wait for version .79 Please stay tuned for this release, and feel free to open a ticket in case you want more follow-up.

Hello Tic
I'm sorry for the inconvenience this issue has caused you.
As mentioned before, we hope to fix this issue by the next release that should come out this month. Please stay tuned for this release, and feel free to open a ticket if you want more follow-up.

Yes same issue here. FTP Permission denied. (SSL/TLS not available)

Version PRTG Version PRTG Network Monitor 22.3.78.1873 x64

Would this be the same issue with Sensors for HTTPS Responding with HTTP/1.1 500 Internal Server Error sensor since upgrading to 22.3.78.1873?

Hi Leonard,

Did you already tried to use Do not use transport-level security? Regarding the other error you are experiencing, this should be a different issue. The error message 500 usually means an issue on your target device.

Kind regards

Felix Wiesneth - Team Tech Support.

Getting the same "Login incorrect. (SSL/TLS not available)" error on a few FTP sensors after updating over the weekend, with them working fine before then.

Updated from 22.2.76.1705 to 22.3.78.1873.

In case it's relevant, in our case none of those sensors were set to actually login to the destination FTP servers, just confirm they were responding, and that worked fine, with no password set and just the default pre-filed "anonymous" username.

Look forward to the hotfix / update coming out.

Hi Keith,

Thank you for the input. We will try to work on this sensor for the next release(s).

Kind regards

Felix Wiesneth - Team Tech Support

Same situation as Keith: We're using the sensors to monitor if FTP is running/responding on the servers with the user "anonymous". Getting different error messages now:

- Login incorrect. (SSL/TLS not available)

- Permission denied. (SSL/TLS not available)

Further tests/information:

- This worekd fine until the upgrade to 22.3.78.1873+

- "Transport-Level Security" doesn't matter

- "FTP Mode" (active or passive) doesn't matter

Latest version fix this problem. Thanks

Thanks for the heads up, I can confirm that it works with 22.3.79.2108 on our end as well.

Hi Everyone.

I confirm it works with 22.3.79.2108 thank you for the update.