starred/gitea-mirror

Fork 0

mirror of https://github.com/RayLabsHQ/gitea-mirror.git synced 2026-04-25 15:25:55 +03:00

[GH-ISSUE #125] Only placeholders loading forever in dashboard, organizations, repositories and activity log #62

New issue

Closed

opened 2026-02-27 15:54:53 +03:00 by kerem · 5 comments

kerem commented

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

Owner

Originally created by @sylvainadm on GitHub (Oct 23, 2025).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/125

Hello there,

First all - thanks for that great project, I love it!

I’ve successfully set it up (via docker compose) and was able to view all my starred repos yesterday. Started mirroring, and after that the dashboard, organizations, repositories and activity log pages are just showing placeholders and seemingly loading forever.

In the background, the logs show that everything is mirroring as it should (although reaching GitHub’s API query limits).

I’m not sure if there’s anything I need to configure differently in my .env or docker-compose.yml file. The only config I have are the AUTH URL, origins and public URL.

Thanks!

Sylvain

Originally created by @sylvainadm on GitHub (Oct 23, 2025). Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/125 Hello there, First all - thanks for that great project, I love it! I’ve successfully set it up (via docker compose) and was able to view all my starred repos yesterday. Started mirroring, and after that the dashboard, organizations, repositories and activity log pages are just showing placeholders and seemingly loading forever. In the background, the logs show that everything is mirroring as it should (although reaching GitHub’s API query limits). I’m not sure if there’s anything I need to configure differently in my .env or docker-compose.yml file. The only config I have are the AUTH URL, origins and public URL. Thanks! Sylvain

kerem

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

closed this issue
added the
question
label

kerem commented

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

Author

Owner

@arunavo4 commented on GitHub (Oct 23, 2025):

Hi @sylvainadm are you able to view the mirrored repos in gitea? if that works well. when you open the gitea mirror app check console logs that might point us to the problem.

@arunavo4 commented on GitHub (Oct 23, 2025): Hi @sylvainadm are you able to view the mirrored repos in gitea? if that works well. when you open the gitea mirror app check console logs that might point us to the problem.

kerem commented

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

Author

Owner

@sylvainadm commented on GitHub (Oct 23, 2025):

Thanks @arunavo4 !

Here's the Firefox console logs:

Firefox can’t establish a connection to the server at https://XXX/api/sse?userId=YYY. MainLayout.BwlFhBZS.js:295:1473

SSE connection error: 
error { target: EventSource, isTrusted: true, srcElement: EventSource, currentTarget: EventSource, eventPhase: 2, bubbles: false, cancelable: false, returnValue: true, defaultPrevented: false, composed: false, … }
MainLayout.BwlFhBZS.js:295:1786

Attempting to reconnect in 3000ms (attempt 1/5) MainLayout.BwlFhBZS.js:295:1903

The connection to https://XXX/api/events?userId=YYY was interrupted while the page was loading. MainLayout.BwlFhBZS.js:295:3496

The docker compose logs:

gitea-mirror  | Job 94e3fede-d4dc-4760--dbe55ac17 has no log data
gitea-mirror  | Job ab8a3e77-cdad-46dc--7ef0121b3 has no log data
gitea-mirror  | [Scheduler] Processing 1 valid configurations (out of 1 with scheduling enabled)
gitea-mirror  | [Scheduler] Skipping user XXX- next run at 2025-10-24T13:28:47.542Z
gitea-mirror  | Job ab6a90f2-ad57-4bea--f5f5ff858e7c has no log data
gitea-mirror  | Job 6702c9b4-cf79-4347--2efed359f2e5 has no log data
gitea-mirror  | Job cbbbcb8e-ce5b-492b--ac18295f05aa has no log data
gitea-mirror  | Job 7bb7a5be-cbb9-441e--139de4e4823d has no log data
gitea-mirror  | Job 5d9f0712-dc27-4e73--c56dd194ec57 has no log data
gitea-mirror  | Job af9c640d-e3c4-4807--4780950ff374 has no log data
gitea-mirror  | Job ab04f2c3-78c2-4472--c0dafa17d46b has no log data
gitea-mirror  | Job e07fee52-e35f-4a45--623425716072 has no log data
gitea-mirror  | Job 94e3fede-d4dc-4760--955dbe55ac17 has no log data
gitea-mirror  | Job ab8a3e77-cdad-46dc--5247ef0121b3 has no log data

No error specifically in the docker compose logs (I removed some characters and the user ID although it doesn't really matter).

On the network tab, I have this:

sse:userId=XXX -> NS_BINDING_ABORTED
events?userId=XXX -> NS_BINDING_ABORTED

The application runs behind an Nginx Proxy Manager, with Websocket support enabled.

I have the repos showing properly in my Gitea instance.

@sylvainadm commented on GitHub (Oct 23, 2025): Thanks @arunavo4 ! Here's the Firefox console logs: ``` Firefox can’t establish a connection to the server at https://XXX/api/sse?userId=YYY. MainLayout.BwlFhBZS.js:295:1473 SSE connection error: error { target: EventSource, isTrusted: true, srcElement: EventSource, currentTarget: EventSource, eventPhase: 2, bubbles: false, cancelable: false, returnValue: true, defaultPrevented: false, composed: false, … } MainLayout.BwlFhBZS.js:295:1786 Attempting to reconnect in 3000ms (attempt 1/5) MainLayout.BwlFhBZS.js:295:1903 The connection to https://XXX/api/events?userId=YYY was interrupted while the page was loading. MainLayout.BwlFhBZS.js:295:3496 ``` The docker compose logs: ``` gitea-mirror | Job 94e3fede-d4dc-4760--dbe55ac17 has no log data gitea-mirror | Job ab8a3e77-cdad-46dc--7ef0121b3 has no log data gitea-mirror | [Scheduler] Processing 1 valid configurations (out of 1 with scheduling enabled) gitea-mirror | [Scheduler] Skipping user XXX- next run at 2025-10-24T13:28:47.542Z gitea-mirror | Job ab6a90f2-ad57-4bea--f5f5ff858e7c has no log data gitea-mirror | Job 6702c9b4-cf79-4347--2efed359f2e5 has no log data gitea-mirror | Job cbbbcb8e-ce5b-492b--ac18295f05aa has no log data gitea-mirror | Job 7bb7a5be-cbb9-441e--139de4e4823d has no log data gitea-mirror | Job 5d9f0712-dc27-4e73--c56dd194ec57 has no log data gitea-mirror | Job af9c640d-e3c4-4807--4780950ff374 has no log data gitea-mirror | Job ab04f2c3-78c2-4472--c0dafa17d46b has no log data gitea-mirror | Job e07fee52-e35f-4a45--623425716072 has no log data gitea-mirror | Job 94e3fede-d4dc-4760--955dbe55ac17 has no log data gitea-mirror | Job ab8a3e77-cdad-46dc--5247ef0121b3 has no log data ``` No error specifically in the docker compose logs (I removed some characters and the user ID although it doesn't really matter). On the network tab, I have this: ``` sse:userId=XXX -> NS_BINDING_ABORTED events?userId=XXX -> NS_BINDING_ABORTED ``` The application runs behind an Nginx Proxy Manager, with Websocket support enabled. I have the repos showing properly in my Gitea instance.

kerem commented

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

Author

Owner

@arunavo4 commented on GitHub (Oct 23, 2025):

@sylvainadm so the problem is at the proxy layer (the app is deployed behind Nginx Proxy Manager with only websocket
support enabled).
Try these :

Adjust the NPM/NGINX config for SSE (e.g. disable proxy buffering, increase read timeouts, keep HTTP/1.1, clear Connection header).
Verify the dashboard works when bypassing the proxy or after the updated config.

@arunavo4 commented on GitHub (Oct 23, 2025): @sylvainadm so the problem is at the proxy layer (the app is deployed behind Nginx Proxy Manager with only websocket support enabled). Try these : 1. Adjust the NPM/NGINX config for SSE (e.g. disable proxy buffering, increase read timeouts, keep HTTP/1.1, clear Connection header). 2. Verify the dashboard works when bypassing the proxy or after the updated config.

kerem commented

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

Author

Owner

@sylvainadm commented on GitHub (Oct 23, 2025):

Ah that was it. First time I come across SSE for self hosting (or at least that I could actually resolve).

Changed my Nginx Proxy Manager config and it’s now working like a charm :). Thanks so much for your help!

I used this in my advanced proxy config: https://medium.com/@dsherwin/surviving-sse-behind-nginx-proxy-manager-npm-a-real-world-deep-dive-69c5a6e8b8e5

Here’s an example from that article:

location / {
    proxy_pass $forward_scheme://$server:$port;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

    # SSE Headers
    proxy_buffering off;
    proxy_http_version 1.1;
    proxy_read_timeout 300s;
    proxy_send_timeout 300s;

    # Error Handling
    proxy_intercept_errors on;
    error_page 502 504 = @retry_backend;
}

location @retry_backend {
    add_header 'Access-Control-Allow-Origin' '*';
    add_header 'Content-Type' 'text/event-stream';
    return 200 "retry: 5000\n:\n\n";
}

@sylvainadm commented on GitHub (Oct 23, 2025): Ah that was it. First time I come across SSE for self hosting (or at least that I could actually resolve). Changed my Nginx Proxy Manager config and it’s now working like a charm :). Thanks so much for your help! I used this in my advanced proxy config: https://medium.com/@dsherwin/surviving-sse-behind-nginx-proxy-manager-npm-a-real-world-deep-dive-69c5a6e8b8e5 Here’s an example from that article: ``` location / { proxy_pass $forward_scheme://$server:$port; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; # SSE Headers proxy_buffering off; proxy_http_version 1.1; proxy_read_timeout 300s; proxy_send_timeout 300s; # Error Handling proxy_intercept_errors on; error_page 502 504 = @retry_backend; } location @retry_backend { add_header 'Access-Control-Allow-Origin' '*'; add_header 'Content-Type' 'text/event-stream'; return 200 "retry: 5000\n:\n\n"; } ```

kerem commented

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

Author

Owner

@arunavo4 commented on GitHub (Oct 24, 2025):

@sylvainadm awesome! in future other people with SSE issues will find it helpful.

@arunavo4 commented on GitHub (Oct 24, 2025): @sylvainadm awesome! in future other people with SSE issues will find it helpful.