iOS 17+
Orka supports iPhone and iPad running iOS 17 or later.
Orka / Support
Let’s get you
connected.
Find setup requirements and fixes for common connection problems, or send a direct support request.
Email supporthi@didac.devHTTPS
Your Coolify installation must use a certificate trusted by iOS.
API token
Use a Coolify token with the permissions required for your workflows.
Quick start
Connect in
three steps.
-
01
Create an API token
In your Coolify dashboard, create an API token under Security. Grant only the read, write, deploy,
read:sensitive, or root permissions you intend to use. -
02
Add your installation
Open Orka and enter a name, the root HTTPS URL of the Coolify installation, and the API token. Do not include
/api/v1, credentials, a query string, or a fragment in the URL. -
03
Test the connection
Orka verifies server health, the Coolify version, team access, and safely detectable permissions before saving the connection.
Troubleshooting
Common fixes.
Orka cannot reach my server
Confirm the URL opens on the same device and starts with https://. Plain HTTP is not supported. For a private certificate authority, install and trust that CA in iOS before connecting.
An action says permission is required
Coolify controls access through token permissions and team roles. Create a replacement token with the required permission, then edit the active installation in Orka and save the new token.
A feature is unavailable on my Coolify version
Orka targets the current Coolify v4 API with v4.1.2 as its compatibility baseline. Older releases and endpoints that differ between versions are supported on a best-effort basis. Update Coolify where practical.
Removing a connection did not revoke its token
Removing an installation deletes Orka's local metadata and Keychain token, but it cannot revoke server-side credentials. Revoke the token from Coolify to invalidate it completely.
What should I include in a support email?
Include your Orka version and build, iOS version, Coolify version, the action you attempted, and the exact error message. Diagnostics can help if you review them first. Never email API tokens, private keys, provider credentials, environment secrets, or unreviewed logs.
Still stuck?
Talk to a human.
Describe what you expected, what happened instead, and the troubleshooting steps you already tried.