#problem
-
[security] Gitea < 1.17.2 bypassing URL restrictions during migration explained
Prior to Gitea 1.17.2 a malicious Gitea server could be used to request local files using the migration web interface or the REST API.
-
[security] Gitea < 1.17.3 git option injection explained
Prior to Gitea 1.17.3 the web interface that displays the commit graph could be used to inject git options used by the Gitea server.
-
1.17 breaking changes episode 2: preserving a custom gitconfig
The location of the gitconfig file used by Gitea moved twice, here is a guide to sort out why and how to deal with it.
-
1.17 breaking changes episode 1: preserving a custom gitconfig
The location of the gitconfig file used by Gitea moved and custom modifications must be manually moved as well.
-
[tutorial] A gentle introduction to the gitea doctor
The doctor command is useful to check the health of a running Gitea instance. Specially after performing an upgrade.
-
[solved] Zombies created by Gitea
Gitea can use process groups to kill its children using a negative PID to never create zombies.
-
[diagnostic] Zombies created by Gitea
An increasing number of zombies processes are created by Gitea because it only kills its direct children on timeout.
-
[solved] Gitea 1.15 and up: path not found or permission denied
After migrating from 1.15 or earlier to gitea 1.16 paths are no longer found and files cannot be created because of permission problems because the default example.ini file changed.
-
[solved] Gitea 1.16.[678] error: fatal: unsafe repository is owned by someone else
If Gitea runs as user git, calls a patched Git version and a parent directory of the git repositories is owned by a user other than git, it will fail.
-
[solved] blank or error 500 page after login
After going to production, some Gitea users saw a blank page after login and had to manually type the URL of the project they wanted to see in the browser.