github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-16 04:42:51 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Failed sending HTTP2 data #7200

New Issue
Closed
opened 2025-11-02 07:19:14 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-02 07:19:14 -06:00
Owner
Copy Link

Originally created by @MrksHfmn on GitHub (Apr 17, 2021).

  • Gitea version (or commit ref): docker image gitea:latest (Gitea version 1.15.0+dev-156-gb1e138511 built with GNU Make 4.3, go1.16.3 : bindata, timetzdata, sqlite, sqlite_unlock_notify)
  • Git version: git version 2.29.2
  • Operating system: Debian Buster (with backports)
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite

Description

I am trying to push/pull code into a repo, however i always get the following error message:
fatal: konnte nicht auf 'https://git.domain.de/user/repo.git/' zugreifen: Failed sending HTTP2 data

The commits are not successfull.

Docker-compose.yaml

---
version: '3.8'

services:
  gitea-db:
    image: mariadb
    container_name: gitea-db
    command: --transaction-isolation=READ-COMMITTED --log-bin=ROW
    restart: unless-stopped
    volumes:
      - /opt/docker/gitea/db:/var/lib/mysql
    environment:
      MYSQL_ROOT_PASSWORD_FILE: /run/secrets/gitea_db_root_password
      MYSQL_PASSWORD_FILE: /run/secrets/gitea_db_user_password
      MYSQL_DATABASE: gitea
      MYSQL_USER: gitea
      MYSQL_INITDB_SKIP_TZINFO: 1
    secrets:
      - gitea_db_root_password
      - gitea_db_user_password
    networks:
      - gitea

  gitea:
    image: gitea/gitea:latest
    container_name: gitea
    restart: unless-stopped
    volumes:
      - /opt/docker/gitea/data:/data
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
    environment:
      - USER_UID=1000
      - USER_GID=1000
      - DB_TYPE=mysql
    labels:
      - "traefik.enable=true"
      - "traefik.docker.network=traefik"
      - "traefik.http.middlewares.gitea-https.redirectscheme.scheme=https"
      - "traefik.http.routers.gitea-http.entrypoints=http"
      - "traefik.http.routers.gitea-http.rule=Host(`git.domain.de`)"
      - "traefik.http.routers.gitea-http.middlewares=gitea-https@docker"
      - "traefik.http.routers.gitea.entrypoints=https"
      - "traefik.http.routers.gitea.rule=Host(`git.domain.de`)"
      - "traefik.http.routers.gitea.tls=true"
      - "traefik.http.routers.gitea.tls.certresolver=http"
      - "traefik.http.routers.gitea.middlewares=secHeaders@file"
      - "traefik.http.services.gitea.loadbalancer.server.port=3000"
    depends_on:
      - gitea-db
    networks:
      - traefik
      - gitea

secrets:
  gitea_db_root_password:
    file: /opt/docker/_secrets/gitea_db_root_password
  gitea_db_user_password:
    file: /opt/docker/_secrets/gitea_db_user_password

networks:
  traefik:
    external: true
  gitea:
    driver: bridge
    name: gitea
Originally created by @MrksHfmn on GitHub (Apr 17, 2021). - Gitea version (or commit ref): docker image gitea:latest (Gitea version 1.15.0+dev-156-gb1e138511 built with GNU Make 4.3, go1.16.3 : bindata, timetzdata, sqlite, sqlite_unlock_notify) - Git version: git version 2.29.2 - Operating system: Debian Buster (with backports) - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite ## Description I am trying to push/pull code into a repo, however i always get the following error message: `fatal: konnte nicht auf 'https://git.domain.de/user/repo.git/' zugreifen: Failed sending HTTP2 data` The commits are not successfull. ## Docker-compose.yaml ``` --- version: '3.8' services: gitea-db: image: mariadb container_name: gitea-db command: --transaction-isolation=READ-COMMITTED --log-bin=ROW restart: unless-stopped volumes: - /opt/docker/gitea/db:/var/lib/mysql environment: MYSQL_ROOT_PASSWORD_FILE: /run/secrets/gitea_db_root_password MYSQL_PASSWORD_FILE: /run/secrets/gitea_db_user_password MYSQL_DATABASE: gitea MYSQL_USER: gitea MYSQL_INITDB_SKIP_TZINFO: 1 secrets: - gitea_db_root_password - gitea_db_user_password networks: - gitea gitea: image: gitea/gitea:latest container_name: gitea restart: unless-stopped volumes: - /opt/docker/gitea/data:/data - /etc/timezone:/etc/timezone:ro - /etc/localtime:/etc/localtime:ro environment: - USER_UID=1000 - USER_GID=1000 - DB_TYPE=mysql labels: - "traefik.enable=true" - "traefik.docker.network=traefik" - "traefik.http.middlewares.gitea-https.redirectscheme.scheme=https" - "traefik.http.routers.gitea-http.entrypoints=http" - "traefik.http.routers.gitea-http.rule=Host(`git.domain.de`)" - "traefik.http.routers.gitea-http.middlewares=gitea-https@docker" - "traefik.http.routers.gitea.entrypoints=https" - "traefik.http.routers.gitea.rule=Host(`git.domain.de`)" - "traefik.http.routers.gitea.tls=true" - "traefik.http.routers.gitea.tls.certresolver=http" - "traefik.http.routers.gitea.middlewares=secHeaders@file" - "traefik.http.services.gitea.loadbalancer.server.port=3000" depends_on: - gitea-db networks: - traefik - gitea secrets: gitea_db_root_password: file: /opt/docker/_secrets/gitea_db_root_password gitea_db_user_password: file: /opt/docker/_secrets/gitea_db_user_password networks: traefik: external: true gitea: driver: bridge name: gitea ```
GiteaMirror added the type/upstream label 2025-11-02 07:19:14 -06:00
GiteaMirror commented 2025-11-02 07:19:15 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Apr 17, 2021):

Could you visit the web ui? Which protocol did you push? HTTP or SSH?

@lunny commented on GitHub (Apr 17, 2021): Could you visit the web ui? Which protocol did you push? HTTP or SSH?
GiteaMirror commented 2025-11-02 07:19:15 -06:00
Author
Owner
Copy Link

@MrksHfmn commented on GitHub (Apr 17, 2021):

Could you visit the web ui? Which protocol did you push? HTTP or SSH?

Web UI works without any problems. I'm pushing/pulling over https

@MrksHfmn commented on GitHub (Apr 17, 2021): > > > Could you visit the web ui? Which protocol did you push? HTTP or SSH? Web UI works without any problems. I'm pushing/pulling over https
GiteaMirror commented 2025-11-02 07:19:15 -06:00
Author
Owner
Copy Link

@Rilgamon commented on GitHub (Apr 17, 2021):

Same error when I try to fetch any git repo ... so this is not a gitea problem but a debian I'd guess?

root:/opt/gitea# git fetch
fatal: konnte nicht auf 'https://github.com/go-gitea/gitea/' zugreifen: Failed sending HTTP2 data

root@grml:/opt/pixelfed# git fetch
fatal: konnte nicht auf 'https://github.com/pixelfed/pixelfed.git/' zugreifen: Failed sending HTTP2 data

Edit: After building own git from source its back to working.
Edit2: Might be related to https://daniel.haxx.se/blog/2021/04/14/curl-7-76-1-h2-works-again/

@Rilgamon commented on GitHub (Apr 17, 2021): Same error when I try to fetch any git repo ... so this is not a gitea problem but a debian I'd guess? ``` root:/opt/gitea# git fetch fatal: konnte nicht auf 'https://github.com/go-gitea/gitea/' zugreifen: Failed sending HTTP2 data ``` ``` root@grml:/opt/pixelfed# git fetch fatal: konnte nicht auf 'https://github.com/pixelfed/pixelfed.git/' zugreifen: Failed sending HTTP2 data ``` Edit: After building own git from source its back to working. Edit2: Might be related to https://daniel.haxx.se/blog/2021/04/14/curl-7-76-1-h2-works-again/
GiteaMirror commented 2025-11-02 07:19:16 -06:00
Author
Owner
Copy Link

@MrksHfmn commented on GitHub (Apr 18, 2021):

Same error when I try to fetch any git repo ... so this is not a gitea problem but a debian I'd guess?

root:/opt/gitea# git fetch
fatal: konnte nicht auf 'https://github.com/go-gitea/gitea/' zugreifen: Failed sending HTTP2 data

root@grml:/opt/pixelfed# git fetch
fatal: konnte nicht auf 'https://github.com/pixelfed/pixelfed.git/' zugreifen: Failed sending HTTP2 data

Edit: After building own git from source its back to working.
Edit2: Might be related to https://daniel.haxx.se/blog/2021/04/14/curl-7-76-1-h2-works-again/

Thank you for your tests! I already thought this was curl related. "Failed sending HTTP2 data" is a curl error message.
Buster Backports has curl 7.74.0. The bug seems to be fixed in 7.76.1

@MrksHfmn commented on GitHub (Apr 18, 2021): > > > Same error when I try to fetch any git repo ... so this is not a gitea problem but a debian I'd guess? > > ``` > root:/opt/gitea# git fetch > fatal: konnte nicht auf 'https://github.com/go-gitea/gitea/' zugreifen: Failed sending HTTP2 data > ``` > > ``` > root@grml:/opt/pixelfed# git fetch > fatal: konnte nicht auf 'https://github.com/pixelfed/pixelfed.git/' zugreifen: Failed sending HTTP2 data > ``` > > Edit: After building own git from source its back to working. > Edit2: Might be related to https://daniel.haxx.se/blog/2021/04/14/curl-7-76-1-h2-works-again/ Thank you for your tests! I already thought this was curl related. "Failed sending HTTP2 data" is a curl error message. Buster Backports has curl 7.74.0. The bug seems to be fixed in 7.76.1
GiteaMirror commented 2025-11-02 07:19:16 -06:00
Author
Owner
Copy Link

@Rilgamon commented on GitHub (Apr 18, 2021):

My first test was going back to stable which did not work either.
The strange thing is that the "bug" was introduced with 7.76.0.
And while compiling own curl first did not work but after compiling git too it worked.
Since I've no real clue about programming and even compiling I'd guess that git from backports and stable was/is compiled with curl 7.76.0 not using libcurl while the included libcurl in stable/backports still was/is older?

@Rilgamon commented on GitHub (Apr 18, 2021): My first test was going back to stable which did not work either. The strange thing is that the "bug" was introduced with 7.76.0. And while compiling own curl first did not work but after compiling git too it worked. Since I've no real clue about programming and even compiling I'd guess that git from backports and stable was/is compiled with curl 7.76.0 not using libcurl while the included libcurl in stable/backports still was/is older?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/upstream
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#7200
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?