Operations¶
Review the known issues for this version, protect your state and diagnose problems without exposing credentials or customer data.
Known issues and maintenance¶
This guide covers package version 0.1.19. Check the Marketplace offer for the version currently available before launch. Its retained complete 17 October 2026 host scan, recorded at 19:52:31 UTC, reports 104 Critical and 680 High raw matches on the pinned kernel identities. These are scanner matches, not distinct proven exploitable vulnerabilities. No findings are ignored, and the full local security gate has not passed.
The retained runtime scan at 19:52:19 UTC has zero High/Critical matches and one Unknown match. Zero High/Critical runtime matches do not qualify the kernel or prove complete compiled-component coverage; that coverage remains unverified. Review the Ubuntu tracker and your own security requirements before deployment. Successful application tasks or Marketplace review do not certify a clean host.
On a fresh automatic boot, the package completed native Git push and independent clone, issue and pull-request creation in the web interface, diff review and merge. After a real reboot, the same volume retained the merged pull request, automatically closed issue, exact commit and complete file content. These are application-use checks; they do not clear the unresolved security findings. Updates require a new verified image and a protected migration.
4. Protect state and plan upgrades¶
Application state is under /var/lib/gitea; server configuration and private identity are under /etc/gitea. Preserve those together with /home/ubuntu/.config/sushi/gitea and any customer input/output directories. Treat backups containing credentials, documents, audio, metrics or repositories as private data. A single local EBS volume is not a redundant service or a backup.
For a consistent backup, finish active requests, stop the owning services below and take an encrypted EBS snapshot or protected file backup using your approved procedure. Preserve ownership and permissions. Start the same services afterwards and verify readback. Test restoration on a separate instance before replacing the original.
sudo systemctl stop gitea.service
# Take and verify your protected backup while the services are stopped.
sudo systemctl start gitea.service
A new Marketplace version does not update an existing instance. Launch the replacement separately, check state-format compatibility, restore only required customer state and verify your own read/write workflow before cutover. Keep a protected backup until the replacement is confirmed. Never erase a server identity as a routine upgrade step.
The generated self-signed TLS certificate expires after 365 days. Arrange an operator-reviewed certificate replacement before expiry, updating the client trust from the authenticated instance. Public DNS and certificate renewal automation are not included.
5. Diagnose a problem¶
sudo systemctl show gitea.service -p ActiveState -p SubState -p NRestarts
sudo journalctl -u gitea.service --no-pager -n 50
Inspect logs privately. Before sharing a support case, remove credentials, private hostnames and all customer content; include the Marketplace version, failing operation and a small invented reproduction. For connection errors, verify the correct Region/instance, Session Manager permissions, network endpoints and the active forwarding session. For input errors, check the package limits and request schema first. Do not install arbitrary replacement packages or delete customer state to force a retry.
Use the Software Sushi support contact and terms on the purchased Marketplace offer. Gitea documentation explains the upstream project; it is not a support commitment from that project for this package.
Last updated October 17, 2026 · Suggest an improvement