Fix

We fixed a bug that caused the webhook signature to be generated incorrectly by Pipe in cases where the custom payload parameter value contained a + character.

New

Our FTP implementation has been updated with support for Explicit FTP over SSL/TLS. The recording files can now be securely pushed to your storage through FTPS.

Details in the blog post @ https://blog.addpipe.com/ftps/ .

Improvement

We have expanded our Amazon S3 Storage with three more regions:

1. Zurich (eu-central-2)
2. Jakarta (ap-southeast-3)
3. UAE (me-central-1)

Improvement

The object URLs for files pushed to your S3 storage will be available regardless of the canned ACL used in the upload process. These URLs are visible in the account dashboard's s3_logs page and are sent with the videocopieds3 webhook.

The blog post goes into detail.

https://blog.addpipe.com/s3-object-urls/

New

Improvement

We have aligned the FTP behavior between the FTP test and the actual FTP push attempts with various FTP folder values (empty string, /, or any other folder value).

Changes to Dashboard FTP test

• More descriptive log messages.
• We stopped trying to make active FTP connections.
• We now print the connection timeout and connection established times.
• The file which is uploaded during the test is now removed from your FTP server at the end of the test.
• The FTP test's timeout value is now aligned with the actual FTP push attempt's timeout (10 seconds instead of 20 seconds).

Changes to actual FTP push attempt

• We stopped trying to make active FTP connections.
• As a result, we have stopped pushing the addpipe-ftp-test.test file with every group of recording files. The file was pushed in an attempt to test if the passive connection mode succeeded.
• We added e new error code, FTP_PASV_FAILED.

New

You can now test your SFTP connection and credentials from the Pipe Account Dashboard.

Now you will be able to test if the connection goes through, if the credentials are correct, if the folder provided exists and if the user has write permission.

The test will also print the timeout value and the working folder and warns you if the user has shell access.

The test will upload a file named addpipe-sftp-test.test.

For the SFTP test to succeed, the port 22 needs to be opened for our account dashboard IP (116.203.232.162).

Improvement

We finally separated FTP and SFTP storage options. You will see the separation in the Pipe Account Dashboard (credentials and logs) and the documentation.

FTP (File Transfer Protocol) and SFTP (SSH File Transfer Protocol) are 2 diferent protocols.

Moving forward, we expect to deprecate FTP because it is inherently insecure. We plan to add support for FTPS (FTP over TLS). This separation will clear the way for that effort.

New

Improvement

The embed code generated in the account dashboard now enforces HTTPS for the two main assets: pipe.js and pipe.css. Previously it inherited the protocol used to deliver the page in which the code was embedded.

Separately, the Pipe recording client also enforces HTTPS for POST communication and asset loading. Previously it inherited the protocol used to deliver the page in which the code was embedded. This is important for kiosk-like applications where the pages are usually delivered over HTTP/localhost.

Fix

We have fixed an issue where when saving the SFTP credentials, the SFTP folder value was not prepended with a /.

New

Improvement

We've implemented multipart upload for Amazon S3 object storage and compatible services (Google Cloud, Digital Ocean Spaces). This applies to both the Pipe storage and to your own storage for recordings larger than 100 MiB in size.

What this means for you:

1. This method ensures improved throughput, which means that you will experience faster uploads for large files, especially visible if the upload happens between different geographical regions, for example, if the recording is uploaded from our EU2 region towards your S3 object storage located in the US or Asia. From our limited testing, we've observed as much as a 3x increase in upload speeds.
2. Another benefit is that you will be able to upload recordings that are larger than 5 GiB in size.
3. On choppy connections, parts that failed to upload will be retried (up to 3 times) instead of retrying the entire file.