Crashes/502 error when act runner is running

[NadeemSadiq]

Description

If i have a act runner connected to my gitea, the gitea (or cloudflare, not 100% sure tbh) returns a 502 error. I am unable to pull any packages while act runner is connected and the webpage randomly crashes a few seconds. Below is the full list of all the info i can think of.

Logs from Gitea Monitor/stack page:
gitea-diagnosis-20250303-112721.zip

Logs from console output:
console-log-output.txt

View on resources on kubernetes:

Gitea Version

1.23.4

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

1.23.4

Operating System

Arm64-Kubernetes (k3s)-Linux

How are you running Gitea?

Environment:

• Kubernetes Version:k3s Kubernetes
• Arm64 CPU Arch

Version:

• Gitea-1.23.4
• Act runner-v0.2.11
• DockerInDocker-docker:20.10-dind

Deployment YAML for Gita:
deployment-yaml.txt

Database

SQLite

[wxiaoguang]

Is it a public instance?

[NadeemSadiq]

Its technically private but It is exposed. You can view it here:
https://git.areaq.xyz/

You can just refresh the page couple times to see it 502. Don't need to even sign up to see the problem

[wxiaoguang]

From your log, I didn't see any "ERROR" log. And Gitea itself doesn't respond 502 (it only responds 500 if internal error occurs)

Could you try to curl your server directly without cloudflare to see whether there would be still any errors?

[wxiaoguang]

And, is it 100% related to "when act runner is running"? For example: when no runner, no 502, when runner starts, then randomly 502?

[NadeemSadiq]

Yes, when i stop the git runner, it works fine. Been using it for a long while now and wanted to include act runner now which is why i'm getting this issue. I did get this issue on an older version, upgrade since i assumed it was a version issue which was not the case. I can disable it now if you want to view the site with the 502?

[wxiaoguang]

Hmm, that's quite strange. If it is surely related to the runner, then maybe we need to figure more details. So let's keep the runner running:

• Did you see any ERROR logs in Gitea's log when the 502 error occurs? Or other reverse proxies?
• Could you try to curl your server directly without cloudflare to see whether there would be still any errors?

I can see that even some simple static files are also responded as 502 randomly (for example: https://git.areaq.xyz/assets/img/favicon.png, it only serves a static file, no git/db operation but it could also be 502), I guess it's somewhat related to the HTTP reverse proxy or the Gitea's builtin HTTP server?

[NadeemSadiq]

Odd, i redirected the webpage in Kubernetes to expose it directly as well and it seems to not be crashing at all now only when talking directly with it. I am a bit confused since i do see events show up in Gitea when it crashes when going through the cloudflare link. I think the issue may be on my ingress possibly but not 100% sure. Will investigate a bit further to make sure the act runner is still connected while i changed the service since this may not be connected correctly (hence the lack of crashing)
.