strapi transfer errors with WebSocket is not open: readyState 3

[ngfgrant]

Bug report

I am opening a new issue as requested here

I am consistently experiencing an issue using the strapi transfer ... command in strapi version v4.23.1 Community Edition and node version v18.20.2.

I am attempting to transfer --from our production instance to a local instance

The error I receive locally is

Starting transfer...
[2024-05-13 17:40:12.250] error: [FATAL] WebSocket is not open: readyState 3 (CLOSED)
Transfer process failed.

The logs on the remote production instance are:

[content] [2024-05-13 16:37:51] [2024-05-13 16:37:51.708] info: [Data transfer] Disabling http timeouts
[content] [2024-05-13 16:37:51] [2024-05-13 16:37:51.710] http: GET /admin/transfer/runner/pull (38 ms) 200
[content] [2024-05-13 16:39:31] [2024-05-13 16:39:31.665] info: [Data transfer] Restoring http timeouts

The transfer token has Full Access.

Required System information

• Node.js version: 18.20.2
• NPM version: 10.5.0
• Strapi version: v4.23.1
• Database: postgres 15
• Operating system: MacOS v14.4.1 (darwin-arm64)
• Is your project Javascript or Typescript: Typescript

Describe the bug

Unable to transfer between a production instance and local instance using strapi transfer --from ... with the error error: [FATAL] WebSocket is not open: readyState 3 (CLOSED)

Steps to reproduce the behavior

We have deployed our remote infra on DigitalOcean's App Platform (if that is relevant), backed by DigitalOcean Spaces (S3 provider). We recently sucessfully transferred between remote instances (to our staging instance), although I can't be sure of the exact version used, although it was all within the last 4-6 weeks.

Expected behavior

I expect to be able to transfer between remote and local instances.

Additional context

There doesn't seem to be any additional log or error messages beyond what I have specified in my bug report above.