The uploaded file shows 100%, but the file download address is not returned. An error code of 500 is given. Please see the screenshot. #16

Closed
opened 2026-01-19 18:28:38 +00:00 by michael · 2 comments
Owner

Originally created by @ligbyte on GitHub.

https://transfer.sh/

The uploaded file shows 100%, but the file download address is not returned. An error code of 500 is given. Please see the screenshot.
Screenshot from 2024-09-18 15-55-29

Originally created by @ligbyte on GitHub. https://transfer.sh/ The uploaded file shows 100%, but the file download address is not returned. An error code of 500 is given. Please see the screenshot. ![Screenshot from 2024-09-18 15-55-29](https://github.com/user-attachments/assets/18dc9846-45ec-4824-ad4b-ac5720702a54)
Author
Owner

@ozwaldorf commented on GitHub:

Uploading a file via curl also fails with an error 500 and the response Could not save metadata

$ curl -vT a.txt https://transfer.sh

* Host transfer.sh:443 was resolved.
* IPv6: 2a01:4f8:200:1097::2
* IPv4: 144.76.136.153
*   Trying [2a01:4f8:200:1097::2]:443...
* Connected to transfer.sh (2a01:4f8:200:1097::2) port 443
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256 / X25519 / id-ecPublicKey
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=transfer.sh
*  start date: Aug  6 10:07:41 2024 GMT
*  expire date: Nov  4 10:07:40 2024 GMT
*  subjectAltName: host "transfer.sh" matched cert's "transfer.sh"
*  issuer: C=US; O=Let's Encrypt; CN=E6
*  SSL certificate verify ok.
*   Certificate level 0: Public key type EC/prime256v1 (256/128 Bits/secBits), signed using ecdsa-with-SHA384
*   Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://transfer.sh/a.txt
* [HTTP/2] [1] [:method: PUT]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: transfer.sh]
* [HTTP/2] [1] [:path: /a.txt]
* [HTTP/2] [1] [user-agent: curl/8.8.0]
* [HTTP/2] [1] [accept: */*]
* [HTTP/2] [1] [content-length: 7]
> PUT /a.txt HTTP/2
> Host: transfer.sh
> User-Agent: curl/8.8.0
> Accept: */*
> Content-Length: 7
>
* upload completely sent off: 7 bytes
< HTTP/2 500
< content-type: text/plain; charset=utf-8
< server: Transfer.sh HTTP Server
< x-content-type-options: nosniff
< x-made-with: <3 by DutchCoders
< x-served-by: Proudly served by DutchCoders
< content-length: 24
< date: Wed, 25 Sep 2024 17:30:40 GMT
<
Could not save metadata
* Connection #0 to host transfer.sh left intact
@ozwaldorf commented on GitHub: Uploading a file via curl also fails with an error 500 and the response `Could not save metadata` ``` $ curl -vT a.txt https://transfer.sh * Host transfer.sh:443 was resolved. * IPv6: 2a01:4f8:200:1097::2 * IPv4: 144.76.136.153 * Trying [2a01:4f8:200:1097::2]:443... * Connected to transfer.sh (2a01:4f8:200:1097::2) port 443 * ALPN: curl offers h2,http/1.1 * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): * TLSv1.3 (IN), TLS handshake, Certificate (11): * TLSv1.3 (IN), TLS handshake, CERT verify (15): * TLSv1.3 (IN), TLS handshake, Finished (20): * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.3 (OUT), TLS handshake, Finished (20): * SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256 / X25519 / id-ecPublicKey * ALPN: server accepted h2 * Server certificate: * subject: CN=transfer.sh * start date: Aug 6 10:07:41 2024 GMT * expire date: Nov 4 10:07:40 2024 GMT * subjectAltName: host "transfer.sh" matched cert's "transfer.sh" * issuer: C=US; O=Let's Encrypt; CN=E6 * SSL certificate verify ok. * Certificate level 0: Public key type EC/prime256v1 (256/128 Bits/secBits), signed using ecdsa-with-SHA384 * Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using sha256WithRSAEncryption * Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * using HTTP/2 * [HTTP/2] [1] OPENED stream for https://transfer.sh/a.txt * [HTTP/2] [1] [:method: PUT] * [HTTP/2] [1] [:scheme: https] * [HTTP/2] [1] [:authority: transfer.sh] * [HTTP/2] [1] [:path: /a.txt] * [HTTP/2] [1] [user-agent: curl/8.8.0] * [HTTP/2] [1] [accept: */*] * [HTTP/2] [1] [content-length: 7] > PUT /a.txt HTTP/2 > Host: transfer.sh > User-Agent: curl/8.8.0 > Accept: */* > Content-Length: 7 > * upload completely sent off: 7 bytes < HTTP/2 500 < content-type: text/plain; charset=utf-8 < server: Transfer.sh HTTP Server < x-content-type-options: nosniff < x-made-with: <3 by DutchCoders < x-served-by: Proudly served by DutchCoders < content-length: 24 < date: Wed, 25 Sep 2024 17:30:40 GMT < Could not save metadata * Connection #0 to host transfer.sh left intact ```
Author
Owner

@stefanbenten commented on GitHub:

The service is currently unavailable, see #594

@stefanbenten commented on GitHub: The service is currently unavailable, see #594
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dutchcoders/transfer.sh#16