gyokuro

FAQ & Troubleshooting

General questions

Which servers does gyokuro support?
Gitea and Forgejo — self-hosted, with any number of instances at the same time.
Does gyokuro work with self-signed certificates or behind a proxy?
Yes. gyokuro supports self-signed certificates, mTLS, HTTP/SOCKS proxies, custom HTTP headers and Basic Auth — built for exactly these homelab setups.
How do I get push notifications?
Through your own ntfy or Gotify instance — self-hosted all the way. There are also local notifications and an optional weekly report.
Are my credentials uploaded anywhere?
No. Tokens and credentials live exclusively in the iOS Keychain on your device. No cloud, no tracking.

Troubleshooting

Sign-in fails
The live login log records every step of the connection check — you’ll see right away whether the URL, certificate or token is the problem. Also make sure the token has the required permissions.
My server requires authentication for the API
Servers that only allow authenticated API access are supported since version 2.1 — please update the app.
Actions runs or logs don't show up
Gitea Actions must be enabled on the server (in the server configuration and in the repository itself). Without Actions enabled, the section stays empty.
Push via ntfy/Gotify doesn't arrive
Check the URL and topic of your instance in Settings, and take a look at the notification filters — they can be restricted per repository and per type.
Certificate errors when connecting
For self-signed certificates you need to explicitly allow the certificate in the app’s server settings, or configure mTLS/custom headers accordingly.

Go to Support →