Could not save metadata #237

Closed
opened 2026-01-19 18:29:32 +00:00 by michael · 15 comments
Owner

Originally created by @andreasonny83 on GitHub.

$ transfer README.md                                                                                                                                                 
################## 100.0%
Could not save metadata

I understand that the service hosted at https://transfer.sh is separated and not maintained by this repo, however, I don't see another way for reporting this problem directly to @nl5887 .
I would just like to know if the service is still online and alive.
Thanks.

Originally created by @andreasonny83 on GitHub. ```sh $ transfer README.md ################## 100.0% Could not save metadata ``` I understand that the service hosted at https://transfer.sh is separated and not maintained by this repo, however, I don't see another way for reporting this problem directly to @nl5887 . I would just like to know if the service is still online and alive. Thanks.
Author
Owner

@paolafrancesca commented on GitHub:

@andreasonny83 interesting. Where are the file hosted? Is the packaged a client only or a server, like transer-sh? I don't find the source code online

@paolafrancesca commented on GitHub: @andreasonny83 interesting. Where are the file hosted? Is the packaged a client only or a server, like transer-sh? I don't find the source code online
Author
Owner

@sxiii commented on GitHub:

Same for me both from CLI and from browser uploader...

@sxiii commented on GitHub: Same for me both from CLI and from browser uploader...
Author
Owner

@andreasonny83 commented on GitHub:

If you are interested, I have just recently built something similar called transfer-now on: https://www.npmjs.com/package/transfer-now

@andreasonny83 commented on GitHub: If you are interested, I have just recently built something similar called transfer-now on: https://www.npmjs.com/package/transfer-now
Author
Owner

@morrigan commented on GitHub:

This issue still persists.

@morrigan commented on GitHub: This issue still persists.
Author
Owner

@paolafrancesca commented on GitHub:

@andreasonny83 you may want to ping @stefanbenten

@paolafrancesca commented on GitHub: @andreasonny83 you may want to ping @stefanbenten
Author
Owner

@ghost commented on GitHub:

I just took a look at the host and fixed the issue. Every now and then it rans out of memory.

The issue has returned

image

@ghost commented on GitHub: > I just took a look at the host and fixed the issue. Every now and then it rans out of memory. The issue has returned ![image](https://user-images.githubusercontent.com/6278400/72209771-c4755d80-3477-11ea-9e99-643aea0aff17.png)
Author
Owner

@TheLastProject commented on GitHub:

Well, reading through this threat:
ping @stefanbenten, sorry to bother you, but the issue has returned.

(Edit: Shift+Enter / Enter inconsistency between different websites is painful...)

@TheLastProject commented on GitHub: Well, reading through this threat: ping @stefanbenten, sorry to bother you, but the issue has returned. (Edit: Shift+Enter / Enter inconsistency between different websites is painful...)
Author
Owner

@stefanbenten commented on GitHub:

We are in the process of migrating the tool to the Storj network with PR #266 .
Waiting for review and test from @aspacca .

@stefanbenten commented on GitHub: We are in the process of migrating the tool to the Storj network with PR #266 . Waiting for review and test from @aspacca .
Author
Owner

@stefanbenten commented on GitHub:

I just took a look at the host and fixed the issue. Every now and then it rans out of memory.

@stefanbenten commented on GitHub: I just took a look at the host and fixed the issue. Every now and then it rans out of memory.
Author
Owner

@andreasonny83 commented on GitHub:

@aspacca the files are stored on aws s3. the cli is just the client side, the server is actually running on the aws side inside Lambda. The source code is not online. I'm planning to scale that project up and have a proper service with a pro plan eventually

@andreasonny83 commented on GitHub: @aspacca the files are stored on aws s3. the cli is just the client side, the server is actually running on the aws side inside Lambda. The source code is not online. I'm planning to scale that project up and have a proper service with a pro plan eventually
Author
Owner

@Whoffie commented on GitHub:

It has returned on command line uploads for me

@Whoffie commented on GitHub: It has returned on command line uploads for me
Author
Owner

@blightwing commented on GitHub:

The issue has returned.

@blightwing commented on GitHub: The issue has returned.
Author
Owner

@2spirit commented on GitHub:

same issue today...

@2spirit commented on GitHub: same issue today...
Author
Owner

@stefanbenten commented on GitHub:

I checked the current host and it seems to operate fine, besides being very busy.

@stefanbenten commented on GitHub: I checked the current host and it seems to operate fine, besides being very busy.
Author
Owner

@michaeleisel commented on GitHub:

I'm having the same issue

@michaeleisel commented on GitHub: I'm having the same issue
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dutchcoders/transfer.sh#237