Skip to content
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

Error downloading minecraft server zip, curl fails #358

Closed
peterswolf opened this issue Oct 11, 2023 · 6 comments · Fixed by #459
Closed

Error downloading minecraft server zip, curl fails #358

peterswolf opened this issue Oct 11, 2023 · 6 comments · Fixed by #459

Comments

@peterswolf
Copy link

Hi,

I'm getting this issue in the logs when running the docker: "curl: (92) HTTP/2 stream 1 was not closed cleanly: PROTOCOL_ERROR (err 1)". What am I doing wrong?

Here's the full debug output:

  • Trying 23.59.177.69:443...
  • Connected to minecraft.azureedge.net (23.59.177.69) port 443 (#0)
  • ALPN: offers h2,http/1.1
    } [5 bytes data]
  • TLSv1.3 (OUT), TLS handshake, Client hello (1):
    } [512 bytes data]
  • CAfile: /etc/ssl/certs/ca-certificates.crt
  • CApath: /etc/ssl/certs
    { [5 bytes data]
  • TLSv1.3 (IN), TLS handshake, Server hello (2):
    { [122 bytes data]
  • TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
    { [29 bytes data]
  • TLSv1.3 (IN), TLS handshake, Certificate (11):
    { [4735 bytes data]
  • TLSv1.3 (IN), TLS handshake, CERT verify (15):
    { [264 bytes data]
  • TLSv1.3 (IN), TLS handshake, Finished (20):
    { [52 bytes data]
  • TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
    } [1 bytes data]
  • TLSv1.3 (OUT), TLS handshake, Finished (20):
    } [52 bytes data]
  • SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
  • ALPN: server accepted h2
  • Server certificate:
  • subject: C=US; ST=WA; L=Redmond; O=Microsoft Corporation; CN=*.azureedge.net
  • start date: May 17 23:32:14 2023 GMT
  • expire date: May 11 23:32:14 2024 GMT
  • subjectAltName: host "minecraft.azureedge.net" matched cert's "*.azureedge.net"
  • issuer: C=US; O=Microsoft Corporation; CN=Microsoft Azure TLS Issuing CA 05
  • SSL certificate verify ok.
    } [5 bytes data]
  • using HTTP/2
  • h2h3 [:method: GET]
  • h2h3 [:path: /bin-linux/bedrock-server-1.20.32.03.zip]
  • h2h3 [:scheme: https]
  • h2h3 [:authority: minecraft.azureedge.net]
  • h2h3 [user-agent: curl/7.88.1]
  • h2h3 [accept: /]
  • Using Stream ID: 1 (easy handle 0x55fd02df0c70)
    } [5 bytes data]

GET /bin-linux/bedrock-server-1.20.32.03.zip HTTP/2
Host: minecraft.azureedge.net
user-agent: curl/7.88.1
accept: /

{ [5 bytes data]

  • TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
    { [265 bytes data]
  • TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
    { [265 bytes data]
  • old SSL session ID is stale, removing
    { [5 bytes data]
    < HTTP/2 200
    < content-length: 91031974
    < content-type: application/octet-stream
    < content-md5: Mz50y2KtwAl9AaFMmac86A==
    < last-modified: Thu, 05 Oct 2023 16:04:34 GMT
    < accept-ranges: bytes
    < etag: "0x8DBC5BCC4AB5F0C"
    < server: Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
    < x-ms-request-id: dec36d49-d01e-002a-5ea8-f74393000000
    < x-ms-version: 2014-02-14
    < x-ms-lease-status: unlocked
    < x-ms-lease-state: available
    < x-ms-blob-type: BlockBlob
    < date: Wed, 11 Oct 2023 18:58:55 GMT
    <
    { [5 bytes data]
  • HTTP/2 stream 1 was not closed cleanly: PROTOCOL_ERROR (err 1)
  • Connection #0 to host minecraft.azureedge.net left intact
    curl: (92) HTTP/2 stream 1 was not closed cleanly: PROTOCOL_ERROR (err 1)
@itzg
Copy link
Owner

itzg commented Oct 11, 2023

Unfortunately this is something unique to your network; however, the most common cause I have heard for odd network connectivity issues is a mismatch in MTU of the docker network vs your LAN network.

@peterswolf
Copy link
Author

Thanks for the quick response itzg, I just checked MTU and seems to be level across the layers at 1500. I'll poke around and some of my other settings.

@xxorde
Copy link

xxorde commented Oct 29, 2023

Same problem here. I would not say my setup is "clean" but all other pods seem to work fine.

# docker logs minecraft-bedrock 
time="2023-10-29T15:23:15Z" level=debug msg="Using /data to match uid and gid"
time="2023-10-29T15:23:15Z" level=debug msg="Resolved UID=1000 from match path"
time="2023-10-29T15:23:15Z" level=debug msg="Resolved GID=1000 from match path"
Looking up latest version...
Downloading Bedrock server version 1.20.40.01 ...
curl: (6) getaddrinfo() thread failed to start

@xxorde
Copy link

xxorde commented Oct 29, 2023

This seams to have good hints: #361.

@xxorde
Copy link

xxorde commented Jan 6, 2024

This is still affecting me, and it is getting more problematic. You can't use an older version of the docker image, for it is no longer supported by the current client.

The best solution seems to use the latest docker release, following this worked on my Debian installation https://docs.docker.com/engine/install/debian/.

@itzg
Copy link
Owner

itzg commented Jan 6, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants