[GH-ISSUE #43] Gitea-mirror behind proxy requires http/2 support #19

New issue

Closed

opened 2026-02-27 15:54:35 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 15:54:35 +03:00

Owner

Originally created by @MadsBen on GitHub (Jul 15, 2025).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/43

Originally assigned to: @arunavo4 on GitHub.

This is not a bug, so this is just for information.

When using a reverse proxy like nginx proxy manager, remember to enable http/2 support on the configured proxy host, in SSL settings.

If not, the gitea-mirror website will not load properly (specifically the MainLayout.*.js file).

Originally created by @MadsBen on GitHub (Jul 15, 2025). Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/43 Originally assigned to: @arunavo4 on GitHub. This is not a bug, so this is just for information. When using a reverse proxy like nginx proxy manager, remember to enable http/2 support on the configured proxy host, in SSL settings. If not, the gitea-mirror website will not load properly (specifically the MainLayout.*.js file).

kerem

2026-02-27 15:54:35 +03:00

closed this issue
added the
documentation
label

kerem commented

2026-02-27 15:54:36 +03:00

Author

Owner

@arunavo4 commented on GitHub (Jul 16, 2025):

Hey @MadsBen, thanks for reporting this!

I've investigated the codebase and confirmed that Gitea Mirror doesn't actually require HTTP/2 - it works perfectly fine with HTTP/1.1. The issue you
experienced with MainLayout.*.js not loading is likely related to how nginx proxy manager handles HTTP/1.1 connections (possibly buffering, chunking, or
timeout settings).

Enabling HTTP/2 resolves it because of better connection handling and multiplexing that HTTP/2 provides, which seems to work around whatever issue the proxy
was having with HTTP/1.1.

I've added a troubleshooting section to our README to the v3 branch to help future users who might encounter this. Thanks for sharing the solution - it will definitely help
others!

For reference, the application:

Uses standard HTTP/1.1 compatible asset loading
Has no HTTP/2 specific dependencies or requirements
Works with any modern reverse proxy configuration

Your workaround of enabling HTTP/2 is a great solution, and I'd recommend it for performance benefits anyway. Thanks again for the helpful feedback!

@arunavo4 commented on GitHub (Jul 16, 2025): Hey @MadsBen, thanks for reporting this! I've investigated the codebase and confirmed that Gitea Mirror doesn't actually require HTTP/2 - it works perfectly fine with HTTP/1.1. The issue you experienced with MainLayout.*.js not loading is likely related to how nginx proxy manager handles HTTP/1.1 connections (possibly buffering, chunking, or timeout settings). Enabling HTTP/2 resolves it because of better connection handling and multiplexing that HTTP/2 provides, which seems to work around whatever issue the proxy was having with HTTP/1.1. I've added a troubleshooting section to our README to the `v3` branch to help future users who might encounter this. Thanks for sharing the solution - it will definitely help others! For reference, the application: - Uses standard HTTP/1.1 compatible asset loading - Has no HTTP/2 specific dependencies or requirements - Works with any modern reverse proxy configuration Your workaround of enabling HTTP/2 is a great solution, and I'd recommend it for performance benefits anyway. Thanks again for the helpful feedback!