Hey folks,
I have an FTP server that I want to use for archiving alert clips. The server definitely works because I can connect to it from FileZilla on my laptop on the same network.
My FTP server only supports FTPS (on purpose, which is FTP over TLS (which is supported by BI), not to be confused with SFTP (not supported)).
I have the server set up correctly in BlueIris (server address, port, username, password, base folder). My FTP server is configured to support passive mode since my BI server is behind a firewall and NAT and won't be addressable for active mode. I've also clicked the "Auth TLS" button, which enables FTP over TLS (its actually the command the FTP client sends to the server). The server uses a valid TLS certificate issued by LetsEncrypt (which is the ISRG X1 Root CA, which is trusted by windows).
I see the following in my FTP logs on the FTP server side:
Mon Jul 24 18:31:32 2023 [pid 2046518] CONNECT: Client "XXX.XXX.XXX.XXX"
Mon Jul 24 18:31:32 2023 [pid 2046518] FTP response: Client "XXX.XXX.XXX.XXX", "220 (vsFTPd 3.0.5)"
Mon Jul 24 18:31:33 2023 [pid 2046518] FTP command: Client "XXX.XXX.XXX.XXX", "AUTH TLS"
Mon Jul 24 18:31:33 2023 [pid 2046518] FTP response: Client "XXX.XXX.XXX.XXX", "234 Proceed with negotiation."
And Blue Iris shows the following when I run a test:
Connecting to <server name>
FTP: 234 Proceed with negotiation. (1)
The FTP server is responding correctly, and then BI looks to be failing. BI does not proceed past the 234 response from the server, and I suspect the (1) is the non-successful status code being returned by the FTP component. I cant find any details in any of the logs on why it might be failing.
I have an FTP server that I want to use for archiving alert clips. The server definitely works because I can connect to it from FileZilla on my laptop on the same network.
My FTP server only supports FTPS (on purpose, which is FTP over TLS (which is supported by BI), not to be confused with SFTP (not supported)).
I have the server set up correctly in BlueIris (server address, port, username, password, base folder). My FTP server is configured to support passive mode since my BI server is behind a firewall and NAT and won't be addressable for active mode. I've also clicked the "Auth TLS" button, which enables FTP over TLS (its actually the command the FTP client sends to the server). The server uses a valid TLS certificate issued by LetsEncrypt (which is the ISRG X1 Root CA, which is trusted by windows).
I see the following in my FTP logs on the FTP server side:
Mon Jul 24 18:31:32 2023 [pid 2046518] CONNECT: Client "XXX.XXX.XXX.XXX"
Mon Jul 24 18:31:32 2023 [pid 2046518] FTP response: Client "XXX.XXX.XXX.XXX", "220 (vsFTPd 3.0.5)"
Mon Jul 24 18:31:33 2023 [pid 2046518] FTP command: Client "XXX.XXX.XXX.XXX", "AUTH TLS"
Mon Jul 24 18:31:33 2023 [pid 2046518] FTP response: Client "XXX.XXX.XXX.XXX", "234 Proceed with negotiation."
And Blue Iris shows the following when I run a test:
Connecting to <server name>
FTP: 234 Proceed with negotiation. (1)
The FTP server is responding correctly, and then BI looks to be failing. BI does not proceed past the 234 response from the server, and I suspect the (1) is the non-successful status code being returned by the FTP component. I cant find any details in any of the logs on why it might be failing.