Support Options
NOTE: When asking for support, it may be a good idea to have the following available so that the person helping has all the info they need:
Your
app.ini
(with any sensitive data scrubbed as necessary).The Gitea logs, and any other appropriate log files for the situation.
- When using systemd, use
journalctl --lines 1000 --unit gitea
to collect logs. - When using docker, use
docker logs --tail 1000 <gitea-container>
to collect logs. - By default, the logs are outputted to console. If you need to collect logs from files,
you could copy the following config into your
app.ini
(remove all other[log]
sections), then you can find the*.log
files in Gitea's log directory (default:%(GITEA_WORK_DIR)/log
).
; To show all SQL logs, you can also set LOG_SQL=true in the [database] section
[log]
LEVEL=debug
MODE=console,file
ROUTER=console,file
XORM=console,file
ENABLE_XORM_LOG=true
FILE_NAME=gitea.log
[log.file.router]
FILE_NAME=router.log
[log.file.xorm]
FILE_NAME=xorm.log- When using systemd, use
Any error messages you are seeing.
When possible, try to replicate the issue on try.gitea.io and include steps so that others can reproduce the issue.
- This will greatly improve the chance that the root of the issue can be quickly discovered and resolved.
If you meet slow/hanging/deadlock problems, please report the stack trace when the problem occurs:
Enable pprof in
app.ini
and restart Gitea[server]
ENABLE_PPROF = trueTrigger the bug, when Gitea gets stuck, use curl or browser to visit:
http://127.0.0.1:6060/debug/pprof/goroutine?debug=1
(IP must be127.0.0.1
and port must be6060
).If you are using Docker, please use
docker exec -it <container-name> curl "http://127.0.0.1:6060/debug/pprof/goroutine?debug=1"
.Report the output (the stack trace doesn't contain sensitive data)
Bugs
If you found a bug, please create an issue on GitHub.
Chinese Support
Support for the Chinese language is provided at Our discourse or QQ Group 328432459.