mirror of
https://github.com/RayLabsHQ/gitea-mirror.git
synced 2026-04-25 07:15:57 +03:00
[GH-ISSUE #155] The page failed to display, after configuring various settings. #78
Labels
No labels
bug
documentation
enhancement
help wanted
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/gitea-mirror#78
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @tcitr-chen on GitHub (Nov 19, 2025).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/155
After configuring the GitHub and Gitee connection information, syncing GitHub data fails to load the page. The following URLs are configured:
PUBLIC_URL: "https://mirror.example.com"
BETTER_AUTH_URL: "https://mirror.example.com"
PUBLIC_BETTER_AUTH_URL: "https://mirror.example.com"
BETTER_AUTH_TRUSTED_ORIGINS: "https://mirror.example.com" The website is behind an Nginx Proxy Manager reverse proxy.
@arunavo4 commented on GitHub (Nov 19, 2025):
@tcitr-chen docker logs please and also check browser console logs and network logs also since its behind a proxy can be failing there too.
@tcitr-chen commented on GitHub (Nov 19, 2025):
@tcitr-chen commented on GitHub (Nov 19, 2025):
@arunavo4 The top image shows the Docker logs; the bottom image shows screenshots of Nginx Proxy Manager re-promoting after frp has traversed HTTPS.
@arunavo4 commented on GitHub (Nov 19, 2025):
@tcitr-chen Enable Http/2 support in NPM and hard refresh or try in incognito or private browsing.
@tcitr-chen commented on GitHub (Nov 20, 2025):
@arunavo4 Hello, I have already enabled HTTP/2. Is the problem caused by my internal network tunneling through HTTPS and then reverse proxying it again?
@arunavo4 commented on GitHub (Feb 24, 2026):
This looks very similar to #125 (SSE blocked/interrupted at the proxy layer), especially since backend logs show mirroring continues.
Can you try this in Nginx Proxy Manager advanced config:
Then hard refresh (or incognito) and check DevTools Network:
/api/sse?...should stay open (not abort quickly)/api/events?...should return normallyIf it still fails, share one screenshot of the failing request headers/response for
/api/sse.