New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not save metadata #277
Comments
|
Same for me both from CLI and from browser uploader... |
|
@andreasonny83 you may want to ping @stefanbenten |
|
This issue still persists. |
|
If you are interested, I have just recently built something similar called transfer-now on: https://www.npmjs.com/package/transfer-now |
|
@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 |
|
I just took a look at the host and fixed the issue. Every now and then it rans out of memory. |
|
@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 |
|
Well, reading through this threat: (Edit: Shift+Enter / Enter inconsistency between different websites is painful...) |
|
I checked the current host and it seems to operate fine, besides being very busy. |
|
The issue has returned. |
|
same issue today... |

$ transfer README.md ################## 100.0% Could not save metadataI 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.
The text was updated successfully, but these errors were encountered: