Gitea Problems & Issues
Real user-reported problems, complaints, and limitations for Gitea. Based on analysis of 13 signals.
Overall score: 72/100
Issues by Category
Gitea Actions is not fully GitHub Actions compatible
Gitea's own docs list GitHub Actions features that are ignored or unsupported, such as timeout-minutes and continue-on-error at job level, only simple runs-on values and limited expressions. Copy-pasted GitHub workflows often need edits.
Gitea webhooks blocked to local network addresses
By default webhooks can only call external hosts, so CI tools or services on private IPs fail with an allowed-host-list error until ALLOWED_HOST_LIST is set. Even then, some users find the setting not honoured when passed the wrong way in containers.
Migrating repositories into Gitea fails or times out
Large GitHub imports hit API rate limits, clones get killed on low-memory servers, and a migration can show Failed even after files copied. Multiple tokens help with rate limits.
Gitea Actions jobs stuck in waiting with no runner
Workflows sit in Waiting when runs-on labels do not match a registered runner, or the runner is registered to the wrong instance. Some users also report runners fetching only one task at a time on specific versions.
Gitea upgrades can fail or break pushes
Users report failed upgrades between minor versions, pre-receive hook errors after upgrade tied to LOCAL_ROOT_URL, and config overridden by environment variables. Backups before upgrading are essential.
Why is Gitea using so much memory or CPU?
Reports include memory growing with the code indexer enabled on 1.22, higher CPU and memory after 1.23 upgrades, and memory not shrinking after repository mirroring. Usually fixable by tuning or disabling the indexer.
Large pushes and LFS uploads fail with 413
Default nginx body-size limits, Gitea's own LFS_MAX_FILE_SIZE, or Cloudflare in front can each return 413 on big pushes and LFS objects. Finding which layer rejects it is the hard part.
Gitea vs Forgejo: which fork should you run?
Gitea became a company in late 2022 and Forgejo was created as a community soft fork under Codeberg e.V., later diverging. Forgejo is no longer a guaranteed drop-in replacement, so choosing early avoids a harder migration later. Some users find the governance dispute overstated.
Gitea Enterprise and Cloud pricing is unclear
The pricing page shows $9.5 next to $19 per user per month with a one-year commitment for online payment, but Gitea Cloud shows no price and the pricing FAQ answers are not visible. Buyers must contact sales.
Gitea SSH clone and push fails in Docker (permission denied / connection refused)
Docker installs expose SSH on a non-standard host port, and the clone URL, port mapping, username (git) or registered key often disagree. Forum threads on this are among the most frequent setup complaints.
Gitea shows wrong URLs or 500 errors behind a reverse proxy
A ROOT_URL that does not match the public URL, or a proxy not forwarding Host and X-Forwarded-Proto, produces http links, redirect loops and some 500 errors. Subpath setups need extra care.
Gitea email notifications not sending
Test email works but notifications do not, TLS handshake errors from wrong port/protocol pairing, and SMTP EOF errors on newer versions are common mailer complaints.
No official support unless you buy Enterprise
The free edition relies on a community forum and GitHub issues, where many threads end without a confirmed fix. Priority email support with an SLA is part of the paid Enterprise plan.
Regret Patterns
Common reasons users regret choosing Gitea.
Underestimating the admin work
Teams pick Gitea because it is free, then spend time on proxies, SSH ports, runners and upgrades.
Expecting full GitHub Actions parity
Workflows copied from GitHub hit unsupported features and need rewrites.
Choosing Gitea then wanting Forgejo
Governance concerns or divergence make later migration harder.
Skipping backups before an upgrade
Failed upgrades are painful without a dump of database and config.
Running SQLite for a growing team
Maintainers advise MySQL/PostgreSQL after database-locked errors under load.
When Gitea Breaks Down
Specific scenarios where Gitea fails or underperforms.
Running behind a reverse proxy
Wrong ROOT_URL or missing forwarded headers cause bad links and redirect loops.
SSH in Docker on a non-standard port
Port mapping and clone URL mismatches lead to connection refused.
Large LFS files
413 errors from nginx, Gitea or Cloudflare.
Webhooks to internal services
Blocked by the default allowed host list.
Version upgrades
Database migrations or LOCAL_ROOT_URL issues can break pushes.
Heavy code search indexing
Memory growth with the repo indexer on large instances.