Transfer operation stuck

drakedev · April 22, 2023, 2:16pm

Hello, I am trying for the first time to use the Transfer feature to pull data from the server to my local environment.

I followed the documentation, created the Transfer tokens, and started the process.
After I click to proceed the process is stuck with no messages or errors. I waited more than 30 minutes and nothing happened.

Both instances are updated to the latest version 4.9.2 and use PostgreSQL as database. The production is hosted on Render.

How can I debug the issue to understand where it is stuck and why?

Boegie19 · April 22, 2023, 2:18pm

see

github.com/strapi/strapi

Transfer feature hangs on asset transfer

opened 09:30PM - 21 Apr 23 UTC

bolg55

issue: bug severity: medium status: confirmed source: core:data-transfer

## Bug report ### Required System information - Node.js version: 16+ - NPM version: 8+ - Strapi version: 4.9.2 - Is your project Javascript or Typescript: JS ### Describe the bug A clear and concise description of what the bug is. Edit: Based on issue #16437 this does not seem to be limited to cloud. When attempting to transfer from a local Strapi instance to a Strapi Cloud project, using: `yarn strapi transfer --to <url> --to-token <token> ` or `npm run strapi transfer --to <url> --to-token <token>` The transfer hangs when it gets to the `assets` transfer. Only killing the process will stop it, which then produces an error. ### Steps to reproduce the behavior 1. Go to a local Strapi project, running on 4.8+ 2. Login to Strapi Cloud and ensure both local and cloud projects have same schema 3. Try to transfer from local to cloud using either: `yarn strapi transfer --to <url> --to-token <token> ` or `npm run strapi transfer --to<url> --to-token <token>` 4. See error ### Expected behavior That the transfer would go through successfully. ### Screenshots ![image](https://user-images.githubusercontent.com/43022248/233736666-ecf70540-3e09-4a3f-8efb-082d7468a279.png) ![image](https://user-images.githubusercontent.com/43022248/233736788-4105482f-aa10-4642-bbf9-2a829a6adc61.png)

drakedev · April 22, 2023, 2:23pm

Thank you I checked that, but in my case, I don’t even see the first CLI message that is visible in the screenshot added to that GitHub issue.

Starting transfer...

it just stays there and nothing happens.

My development env is on Windows and npm version is 9.3.0

boriskamp · April 22, 2023, 3:16pm

Following this as I have the exact same issue, the way @drakedev describes it is happening to me as well:

from remote to local
running Strapi 4.9.2 on both locations
After The transfer will delete all the local Strapi assets and its database. Are you sure you want to proceed? Yes nothing happens.

There is definitely something off here and needs the dev’s attention, can someone from Strapi jump in here?

nachoogomez · April 25, 2023, 9:18pm

The same here from remote to local with 4.8.2 on both locations. After response with Yes, nothing happens

setcooki · May 4, 2023, 8:24pm

Same here! useless feature has it not even a verbose mode for any debugging

RafidMuhymin · May 11, 2023, 7:42pm

I am facing the same issue. But it was working even a few days ago. I don’t know why but today when the running the command I’m getting the exact same issue. The only difference is that I have the DRAG AND DROP CONTENT TYPE PLUGIN installed. The command gets stuck after this message REGISTERED DRAG AND DROP CONTENT TYPE PLUGIN.

RafidMuhymin · May 11, 2023, 8:03pm

Downgrading to v4.9.0 from v4.10.2 (and upwards) fixed the issue for both pulling and pushing (I didn’t test if pushing was working in v4.10.2+).

Chinmay_kumar_Dey · September 6, 2023, 12:01pm

Same issue for me also. I am using 4.12.7

Shah · March 8, 2025, 11:41am

I get the same issue, last verbose messages on local env are:
. [local-destination-provider] creating assets write stream
. ⠧ assets: 0 transfered (size: 0) (elapsed: 0 ms)

On the production server, the errors are:
. GET /admin/transfer/runner/pull (8 ms) 200
[Data transfer] Restoring http timeouts
[Data transfer] Restoring lifecycle hooks

Nothing much to go on here. I think its a bug…unfortunately…help