Troubleshooting¶
Resolve Gitea startup, connection, repository, and restore problems.
gitea.service is not active¶
Cause: cloud-init has not finished, or the service failed.
Fix:
sudo cloud-init status --wait
sudo -iu ubuntu
sudo systemctl is-active gitea.service
sudo systemctl show gitea.service -p ActiveState -p SubState -p NRestarts
sudo journalctl -u gitea.service --no-pager -n 50
Do not recreate the instance identity to force a retry.
The browser or API cannot reach port 8443¶
Cause: the forward is down, or the certificate is not the one from this instance.
Fix: forward port 8443 and trust server.crt from this instance. Do not
disable verification. On the instance, use sushi-gitea-api so the helper
reads the account file.
A repository or Git push fails¶
Cause: registration, SSH Git hosting, LFS, Actions, and the mailer are disabled. The credential helper must be run by Git, not directly.
Fix: create the repository with the helper as in
Getting started. For clone and push, follow
/opt/sushi/docs/README.md. Do not run the credential helper by hand.
Issues disappear after a move¶
Cause: /var/lib/gitea was restored without /etc/gitea and
/home/ubuntu/.config/sushi/gitea.
Fix: restore those paths together, then reload the issue and the merged pull request. A new Marketplace version does not update a running instance. See Operations.
Last updated November 1, 2026 · Suggest an improvement