github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-11 17:46:29 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1) #14831

New Issue
Closed
opened 2025-11-02 11:23:56 -06:00 by GiteaMirror · 8 comments
GiteaMirror commented 2025-11-02 11:23:56 -06:00
Owner
Copy Link

Originally created by @andrewhamili on GitHub (Aug 3, 2025).

Description

Image

Been experiencing this error recently when I switched from Gitea Binary installation to Gitea Docker.

This is currently hosted via Apache. Proxied port 3333 to my domain Under cloudflare

However, I tried tunneling the port (3333) and pulling the repository and it works fine.

Image

Let me know if you need more details about this issue that I am currently experiencing

Gitea Version

1.24.3

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

2.49.1

Operating System

Ubuntu 20.04.6 LTS

How are you running Gitea?

version: '3.3'
volumes:
gitea_repositories:
gitea_data:
repos:
driver: local
driver_opts:
type: none
device: /mnt/gitea
o: bind
networks:
gitea:
external: false
services:
server:
image: docker.gitea.com/gitea:latest
tty: true
container_name: gitea_server
environment:
- USER_UID=1000
- USER_GID=1000
- GITEA__database__DB_TYPE=postgres
- GITEA__database__HOST=db:5432
- GITEA__database__NAME=gitea
- GITEA__database__USER=postgres
- GITEA__database__PASSWD=p0stgr3s
- GITEA_actions_ENABLED=true
restart: always
networks:
- gitea
volumes:
- /mnt/gitea/data:/data
- ./dump:/dump
- /etc/timezone:/etc/timezone:ro
- /etc/localtime:/etc/localtime:ro
ports:
- "3333:3000"
- "222:22"
depends_on:
- db
db:
container_name: gitea_postgres
image: docker.io/library/postgres:14
tty: true
restart: always
environment:
- POSTGRES_USER=postgres
- POSTGRES_PASSWORD=p0stgr3s
- POSTGRES_DB=gitea
- ./postgres:/var/lib/postgresql/data
networks:
- gitea
volumes:
- ./postgres:/var/lib/postgresql/data
runner:
container_name: gitea-act-runner
depends_on:
- server
volumes:
- ./runner:/data
- /var/run/docker.sock:/var/run/docker.sock
networks:
- gitea
image: gitea/act_runner
privileged: true
tty: true
environment:
- GITEA_INSTANCE_URL=https://git.andrewhamili.com
- GITEA_RUNNER_NAME=Runner
- GITEA_RUNNER_REGISTRATION_TOKEN=bNfvCb3TudlgeMY0f3CJnKEkJC19gra5ypTHazRW
- GITEA_RUNNER_LABELS=ubuntu-latest:docker://node:16-buster`

Database

PostgreSQL

Originally created by @andrewhamili on GitHub (Aug 3, 2025). ### Description <img width="1206" height="42" alt="Image" src="https://github.com/user-attachments/assets/4f31ed7b-1e6c-4b82-aa4f-5195ac966d98" /> Been experiencing this error recently when I switched from Gitea Binary installation to Gitea Docker. This is currently hosted via Apache. Proxied port 3333 to my domain Under cloudflare However, I tried tunneling the port (3333) and pulling the repository and it works fine. <img width="529" height="134" alt="Image" src="https://github.com/user-attachments/assets/86f555b6-5654-4a4b-ab15-ba6a3ef57362" /> Let me know if you need more details about this issue that I am currently experiencing ### Gitea Version 1.24.3 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version 2.49.1 ### Operating System Ubuntu 20.04.6 LTS ### How are you running Gitea? version: '3.3' volumes: gitea_repositories: gitea_data: repos: driver: local driver_opts: type: none device: /mnt/gitea o: bind networks: gitea: external: false services: server: image: docker.gitea.com/gitea:latest tty: true container_name: gitea_server environment: - USER_UID=1000 - USER_GID=1000 - GITEA__database__DB_TYPE=postgres - GITEA__database__HOST=db:5432 - GITEA__database__NAME=gitea - GITEA__database__USER=postgres - GITEA__database__PASSWD=p0stgr3s - GITEA_actions_ENABLED=true restart: always networks: - gitea volumes: - /mnt/gitea/data:/data - ./dump:/dump - /etc/timezone:/etc/timezone:ro - /etc/localtime:/etc/localtime:ro ports: - "3333:3000" - "222:22" depends_on: - db db: container_name: gitea_postgres image: docker.io/library/postgres:14 tty: true restart: always environment: - POSTGRES_USER=postgres - POSTGRES_PASSWORD=p0stgr3s - POSTGRES_DB=gitea - ./postgres:/var/lib/postgresql/data networks: - gitea volumes: - ./postgres:/var/lib/postgresql/data runner: container_name: gitea-act-runner depends_on: - server volumes: - ./runner:/data - /var/run/docker.sock:/var/run/docker.sock networks: - gitea image: gitea/act_runner privileged: true tty: true environment: - GITEA_INSTANCE_URL=https://git.andrewhamili.com - GITEA_RUNNER_NAME=Runner - GITEA_RUNNER_REGISTRATION_TOKEN=bNfvCb3TudlgeMY0f3CJnKEkJC19gra5ypTHazRW - GITEA_RUNNER_LABELS=ubuntu-latest:docker://node:16-buster` ### Database PostgreSQL
GiteaMirror added the issue/needs-feedbackissue/not-a-bug labels 2025-11-02 11:23:56 -06:00
GiteaMirror commented 2025-11-02 11:23:57 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Aug 5, 2025):

I don't think it's a bug. It seems it's a CDN/reverse proxy configuration problem.

@lunny commented on GitHub (Aug 5, 2025): I don't think it's a bug. It seems it's a CDN/reverse proxy configuration problem.
GiteaMirror commented 2025-11-02 11:23:57 -06:00
Author
Owner
Copy Link

@andrewhamili commented on GitHub (Aug 5, 2025):

Image

Hi @lunny what do you think the problem is? This is proxied using Apache2. I used to host a gitea server that is not on docker here. Just recycled my Apache vshost

@andrewhamili commented on GitHub (Aug 5, 2025): <img width="466" height="121" alt="Image" src="https://github.com/user-attachments/assets/a50979a3-a7c0-43da-bf96-84eb6f5250d0" /> Hi @lunny what do you think the problem is? This is proxied using Apache2. I used to host a gitea server that is not on docker here. Just recycled my Apache vshost
GiteaMirror commented 2025-11-02 11:23:57 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Aug 5, 2025):

Sorry, I’m not very familiar with Apache2.

@lunny commented on GitHub (Aug 5, 2025): Sorry, I’m not very familiar with Apache2.
GiteaMirror commented 2025-11-02 11:23:57 -06:00
Author
Owner
Copy Link

@andrewhamili commented on GitHub (Aug 8, 2025):

Hi @lunny so if I would use something you are familiar with, what is it and what configuration should I use? I already mentioned that it used to work on a binary installation of Gitea, but it does not work on a docker installed Gitea now.

@andrewhamili commented on GitHub (Aug 8, 2025): Hi @lunny so if I would use something you are familiar with, what is it and what configuration should I use? I already mentioned that it used to work on a binary installation of Gitea, but it does not work on a docker installed Gitea now.
GiteaMirror commented 2025-11-02 11:23:57 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Aug 8, 2025):

Does it work if you access the port exposed by the Docker container directly?

@lunny commented on GitHub (Aug 8, 2025): Does it work if you access the port exposed by the Docker container directly?
GiteaMirror commented 2025-11-02 11:23:57 -06:00
Author
Owner
Copy Link

@andrewhamili commented on GitHub (Aug 9, 2025):

Does it work if you access the port exposed by the Docker container directly?

Yes. I can do everything using HTTP through the port exposed (http://localhost:3333)

@andrewhamili commented on GitHub (Aug 9, 2025): > Does it work if you access the port exposed by the Docker container directly? Yes. I can do everything using HTTP through the port exposed (http://localhost:3333)
GiteaMirror commented 2025-11-02 11:23:58 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Aug 9, 2025):

You can try to add Protocols h2 http/1.1 on your apache2 configuration.

@lunny commented on GitHub (Aug 9, 2025): You can try to add `Protocols h2 http/1.1` on your apache2 configuration.
GiteaMirror commented 2025-11-02 11:23:58 -06:00
Author
Owner
Copy Link

@GiteaBot commented on GitHub (Sep 9, 2025):

We close issues that need feedback from the author if there were no new comments for a month. 🍵

@GiteaBot commented on GitHub (Sep 9, 2025): We close issues that need feedback from the author if there were no new comments for a month. :tea:
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 issue/needs-feedback issue/not-a-bug
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#14831
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?