Domains and SSL
The Domains section. A domain is the host campaign links point to. The panel also works without domains, by the server IP: http://<ip>/admin.php.
Adding
- Add domain β one or several, comma-separated (
http(s)://is stripped automatically). The list is added in the background, one request per domain; rows appear in the table as they are added, no need to wait for the dialog. - Point the domain's A record at the server IP (shown at the top of the page). If the domain's DNS is managed by a connected Cloudflare, Namecheap or Dynadot, the record is written automatically.
- The tracker checks DNS and issues the certificate automatically.
The server IP is detected automatically. If the server is behind NAT or has no outgoing HTTP, set it manually in Settings β General β both the DNS check and SSL issuance use it.
Domain settings
| Field | Meaning |
|---|---|
| Index page | The campaign that opens when the domain is visited without an alias |
| Catch 404 | Nonexistent paths of the domain also open the Index campaign instead of a 404 |
| Search robots | Disallow (default: noindex and a robots.txt with Disallow: /) or allow indexing |
| HTTPS-only | 301 from HTTP to HTTPS |
| Admin panel | "Disallow" β the panel and api.php on this domain respond with 404, tracking keeps working. The panel stays available on other domains and by IP |
| Status | "Disabled" β the domain answers 404 to everything, including tracking |
| SSL mode | Let's Encrypt, Cloudflare, your own certificate, or self-signed. Not selected β Cloudflare for proxied domains, otherwise Let's Encrypt |
| Cloudflare proxy | The orange cloud: TLS for the visitor is terminated by Cloudflare; the server still answers over HTTPS on 443 (Orbitra configures this itself) |
| Manage DNS via | Which Cloudflare / Namecheap / Dynadot account parks this domain's A record |
| Group | For sorting; groups can be renamed right in the list |
| PWA | The domain can be bound to a PWA landing β it will serve the app from the root (PWA and Web Push) |
SSL
Let's Encrypt
Certificates are issued by the background worker cli/ssl_installer.php (a cron every 5 minutes, installed by the installer) through the root helper orbitra-issue-cert with fixed arguments. Issuance uses the webroot method; the nginx config is rebuilt from the database. The Issue SSL button starts the worker immediately.
The statuses in the SSL column explain what is missing: the domain does not point at the server yet (the certificate will be issued by itself once the A record propagates), certbot is not installed, the web user cannot run the helper via sudo, the certificate is issued but nginx is not serving it yet, the file is missing the intermediate certificate (Chrome will refuse to open β reissue), and so on.
If the panel says the web user cannot run the helper, run this once:
sudo bash /var/www/orbitra/cli/server_setup.sh
Full SSL diagnostics on the server: sudo bash /var/www/orbitra/cli/ssl_diagnose.sh.
Cloudflare
With the Cloudflare proxy, the visitor's certificate is served by Cloudflare, and a self-signed one is installed on the server for the Full mode. For Full (Strict), enter the paths to the Cloudflare Origin CA certificate and key in the "Custom certificate" field. The modes are covered in detail in Cloudflare Full Strict SSL (in English).
Custom certificate
Paths to the certificate and key files on the server. Paths are validated for allowed characters before being written to the nginx config.
Panel by IP
https://<ip>/admin.php works with a self-signed certificate (Let's Encrypt does not issue certificates for IPs). If the nginx config was edited by hand and the panel stopped responding, rebuild it from the database: sudo php /var/www/orbitra/cli/nginx_sync.php.
Registrars and DNS providers
Connected under β β Integrations, in the "Domains and SSL" group. Each provider can have several accounts; for each domain you choose which account manages it.
| Provider | What it can do |
|---|---|
| Cloudflare | An A record to the server when a domain is added (the zone is looked up by parent: sub.example.com β example.com), extra A/AAAA records of that name are removed; the zone's SSL mode; proxy; Import & Auto-DNS β pull an account's zones into the tracker; rewrite all of an account's A records to a new IP. For details, see Cloudflare |
| Namecheap | Balance, domain import, purchase with parking (contact from Address Book, one-year registration price from the account's price list), A records when a domain is added |
| Dynadot | Accounts by API key with balance, domain import, purchase with parking, A records on adding. Domains on custom NS (for example, Cloudflare) are not touched; in Dynadot's DNS zone the remaining records (MX, TXT) are preserved. Requests to one key run sequentially β Dynadot bans parallel ones |
Backorder
β β Backorder β monitoring of domains you want to catch: a list of domains with "free / taken" checks, notes, and TXT/CSV export. Auto-checking works while the page is open; around the clock β via the cron in Settings β Automation (every 3 minutes, backorder_cron.php).
Quick start: your first campaign
The short path: install the tracker, create a campaign, and get your first clicks and conversions in under an hour.
Read guide βDocsInstallation and updates
Install Orbitra on a fresh Ubuntu or Debian server with one command, and update to new versions safely.
Read guide βDocsMigrating from Keitaro
Move campaigns, offers, sources and domains from Keitaro to Orbitra in one click β what transfers and what to check.
Read guide βDocsMigrating from Binom
Move campaigns and streams from Binom to Orbitra: what transfers automatically and what to set up by hand.
Read guide βDocsFeature overview
Everything Orbitra can do: campaigns and streams, cloaking, landings, PWA, postbacks, costs, reports and integrations.
Read guide βDocsCampaigns and streams
The complete reference: campaign settings, stream types, schemas, rotation, filters, test links and every option explained.
Read guide βDocsCloaking
Full cloaking reference: detection layers, global settings, per-stream filters, verdicts and reports.
Read guide βDocsBrowser check
How the JS check catches bots, VMs and emulators through contradictions in the browser environment.
Read guide βDocsLanding pages
Landing types, the {offer} macro, the JS adapter, LeadForge and multi-offer landings β the complete reference.
Read guide βDocsPWA and Web Push
Build installable PWA apps and collect push subscribers: settings, icons, events and notifications.
Read guide βDocsPWA Funnel
A multi-step PWA funnel: install prompts, event tracking and re-engagement notifications.
Read guide βDocsConversion popups
Show real conversion events as on-page popups: setup, triggers and placement.
Read guide βDocsSession recordings and heatmaps
Replay real visits and see click and scroll maps. Storage limits and privacy notes.
Read guide βDocsContent gallery
Central storage for icons, screenshots and creatives used across PWAs and landings.
Read guide βDocsCreatives library
Store creatives with subid tracking and test them across campaigns.
Read guide βDocsExternal PWA and Telegram channels
Publish PWAs to external domains and run Telegram channels as a traffic source.
Read guide βDocsPostbacks and conversions
Incoming postbacks, conversion statuses and types, and outgoing S2S postbacks to your traffic source.
Read guide βDocsCosts
Import spend from Facebook, TikTok and Google Ads, or update it via API and cron β and how the revenue aggregator works.
Read guide βDocsPush and pop networks
Working with push and pop traffic sources: feeds, zone optimization and the zone killer.
Read guide βDocsFacebook / Meta
Cost import from Meta Ads and the Conversions API: server-side events with deduplication.
Read guide βDocsDolphin / Fbtool
Receive Facebook costs through the Dolphin (Fbtool) API in real time.
Read guide βDocsFB comment cleaner
Bulk-moderate comments under Meta ads: hide, delete and filter by keywords.
Read guide βDocsTraffic sources and affiliate networks
Catalog of 50+ traffic sources and 440+ networks: templates, parameters and postback URLs.
Read guide βDocsReports, logs and metrics
The report builder, saved reports, click logs and every metric explained.
Read guide βDocsDomains and SSL
Add domains, DNS, free Let's Encrypt certificates, redirects, parking and every switch on the page.
Read guide βDocsCloudflare
How to run campaign domains through Cloudflare: DNS, SSL modes and what to turn off.
Read guide βDocsAdministration
Users, roles and permissions, security settings, geo databases, updates and system health.
Read guide βDocsTelegram bot
Manage the tracker from Telegram: stats, conversions and alerts in chat.
Read guide βDocsMCP: an AI assistant in the tracker
Connect Claude or any MCP client to Orbitra and manage campaigns with plain-language commands.
Read guide β