Skip to main content
Version: 1.19.4

Support Options


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:

  1. Your app.ini (with any sensitive data scrubbed as necessary).

  2. 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
  3. Any error messages you are seeing.

  4. When possible, try to replicate the issue on 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.
  5. If you meet slow/hanging/deadlock problems, please report the stack trace when the problem occurs:

    1. Enable pprof in app.ini and restart Gitea

      ENABLE_PPROF = true
    2. Trigger the bug, when Gitea gets stuck, use curl or browser to visit: (IP must be and port must be 6060).

    3. If you are using Docker, please use docker exec -it <container-name> curl "".

    4. Report the output (the stack trace doesn't contain sensitive data)


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.