Domains

Last updated

/jabali-panel/domains. The domains hosted on the panel under your account.

List

Columns: domain name, PHP version, SSL state, DNSSEC state, listen IP, last modified.

Filter by SSL state, DNSSEC state, or free-text on the name.

Per-domain actions

  • Edit: opens the domain edit page (PHP version, SSL, DNSSEC, redirects, aliases, mail toggle).
  • DNS records: opens DNS Records for the domain.
  • Manage SSL: opens SSL scoped to the domain.

Adding a domain

If your package allows it, Add domain opens a small form: domain name, PHP version, mail (on / off). On submit, the panel:

  1. Creates the Domain row.
  2. Creates the DNS zone with default records pointing to your account’s primary IP.
  3. Schedules the reconciler, which renders the nginx vhost and the FPM pool mapping within 60 seconds.

The domain count is checked against the package limit; if you are at the limit, the form refuses to submit and links you to your administrator’s contact form.

Verifying a new domain

A domain you add stays Unverified until you prove that you control the name. This stops anyone from claiming a name that belongs to someone else. Until the domain is verified:

  • its DNS zone is not published and no mail is accepted for it;
  • it has no trusted certificate;
  • visitors who reach the name get no response;
  • if an administrator sends a verified domain back to Unverified, its mailboxes cannot sign in until it is verified again. Their mail is kept.

To build the site while you wait, turn on Preview URL on the domain’s Overview tab. The site then works through its preview address, even though its real name is not published yet. You can also edit its DNS records in the panel; they are published once the domain is verified.

To verify the domain:

  1. Open the domain. The banner at the top shows a TXT record: a Name (_jabali-challenge.<your domain>) and a Value (jabali-verify=…).
  2. Add that TXT record at the DNS provider your domain uses today (usually your registrar). Records added in this panel do not count while the domain is unverified.
  3. Click Verify now, or wait: the panel checks on its own, every minute at first and less often later. The domain goes live as soon as two public DNS resolvers return the value. You can remove the record after that.

The banner shows what the last check found. If it says your nameservers already point to this server, a DNS record cannot prove the name; ask your administrator to approve it.

A domain that is never verified is removed from your account after 14 days, with a notice 4 days before. Its site files are kept. A subdomain of a domain you already verified (for example blog.example.com under a verified example.com) is verified at once and needs no record.

Removing a domain

Open Edit → Delete. Destructive: the vhost is torn down, the certificate is revoked, the DNS zone is removed, and any mailboxes in the domain are deleted. Asks twice.

Blocking AI crawlers

On the domain’s Overview tab, Block AI crawlers makes the site answer 403 to the crawlers and assistants of AI companies (GPTBot, ClaudeBot, CCBot, PerplexityBot, Bytespider and others). Google’s and Bing’s crawlers are never blocked, Google’s AI fetchers included. It stops only bots that name themselves in their User-Agent header; the server’s CrowdSec protection deals with bots that do not. It takes effect within a minute.

Google’s and Apple’s AI training opt-outs (Google-Extended, Applebot-Extended) are not crawlers of their own: Googlebot and Applebot read them from your robots.txt. To opt out of those, add to robots.txt:

User-agent: Google-Extended
Disallow: /

User-agent: Applebot-Extended
Disallow: /

Subdomains

Subdomains are first-class domains in the panel. Add a subdomain by creating a new domain with the subdomain name (e.g. blog.example.com). The DNS zone for blog.example.com is created independently from example.com, you may need to delegate via NS records if both zones are hosted here.

By default only you (and the administrator) can add a subdomain of a domain you own. If another account on the server needs one — for example a client who runs shop.example.com from their own account — open the domain, and on its Overview tab turn on Allow subdomains by other accounts. Any account on the server can then add subdomains of that domain without asking you. Turning it off stops new ones; subdomains already created by other accounts stay. Each parent domain needs its own consent: allowing it on b.example.com does not let another account create c.b.example.com if example.com belongs to a third account that has not allowed it.

Statistics

A domain’s Statistics tab shows its web traffic for the last 7, 30 or 90 days:

  • Requests and Bandwidth per day, as a chart (switch between the two) and as a table under Daily values. Requests count every request in the site’s access log, and Bandwidth everything the site sent, search engines and other bots included. This is the same figure your package’s monthly bandwidth limit uses.
  • Visitors by country: each country’s requests, its share and its bandwidth, bots included. Unknown / other holds addresses with no known country (for example private networks) and, on a busy site, the countries past the 29 busiest of each day. The country comes from the GeoLite2 database by MaxMind. It appears only on servers that have it (it is installed with CrowdSec); without it the table says there is no country data.

The panel counts each day once, on the day after, from that day’s access log, so today is not in the statistics yet. For today’s traffic, open the Logs tab. The statistics are kept as long as the server’s bandwidth ledger (90 days unless your administrator changed it).

Composer

When your hosting package includes Composer, a domain has a Composer tab. It finds the domain’s composer.json (in the document root or a folder above it, up to domains/<domain>/) and runs Composer there:

  • Install puts in exactly the versions composer.lock lists. With no composer.lock yet, it picks the newest versions composer.json allows and writes one.
  • Update moves packages to newer versions that composer.json allows and rewrites composer.lock. Leave the package list empty to update everything, or name the packages to update.
  • Add package and Remove package add or take out a package (vendor/name, with an optional version such as ^3.0).
  • More has checks that don’t change anything: audit for security advisories, outdated packages, installed packages, validate composer.json, rebuild the autoloader, and diagnose.
  • Production only leaves out the dev packages (--no-dev).

Composer runs as you, in your SSH environment, on the PHP version the domain uses, and the project’s composer.json scripts run too. One run at a time per domain; a run stops after 30 minutes. The tab shows the run’s log as it goes, and keeps a list of past runs with their logs.

Project folder. If your composer.json is somewhere else, click Change next to Project folder and pick Use this folder. The folder is from your home directory: domains/ or a folder inside it, such as domains/shared. Several domains and subdomains can use the same folder, so they share one composer.json, composer.lock and vendor/ instead of each keeping a copy. The tab then looks only in that folder, and every run runs there. A run uses the PHP version of the domain you start it from. Only one run at a time works in a folder, whichever domain starts it. To go back, pick Find composer.json from the document root. Renaming a domain moves its document root; if the project folder is inside the document root, set it again after the rename.

Take a backup before Update or Remove: they change the packages your site runs. Cancel stops a run but doesn’t undo what Composer has already written to composer.json, composer.lock or vendor/; run Install afterwards to bring vendor/ back in line with composer.lock.

Without the tab, ask your administrator: Composer runs are a package setting, off unless they turn it on.

Git

When your hosting package includes Git deploy, a domain has a Git tab. It deploys the domain from a Git repository: GitHub, GitLab, Bitbucket or any Git host, over https://.

Connect a repository. Enter the repository’s https:// URL (not an SSH git@… URL, and no username or token in it) and, optionally, a branch; empty uses the repository’s default branch. For a private repository, add a read-only access token and the username your Git host expects with it (GitHub: your username; Bitbucket: x-token-auth; GitLab: any name). Saving checks the repository first and saves nothing if that fails. The token is never shown again: leave the field empty to keep it, or tick Public repository to remove it.

The deployment settings, also under Edit settings:

  • Web directory: the folder inside the repository that the site serves, public for Laravel. Empty serves the repository’s root. If the repository doesn’t have it, and the deploy commands don’t build it, a deployment creates it, empty.
  • Shared paths: files and folders kept across deployments in domains/<domain>/shared, such as .env or storage.
  • Deploy commands: run in the new release before it goes live, one per line: php artisan migrate --force, php8.3 <file>, or wp …. No shell runs them, so pipes, && and variables don’t work.

Deploy now fetches the branch into a new release in domains/<domain>/releases/, links the shared paths, runs composer install when the project needs it and your package includes Composer, runs the deploy commands, and only then makes the release live. The tab shows the log as it goes. The site keeps serving the current release until then, and after a deployment that fails. Cancel stops a deployment before its release goes live. After the first deployment, the domain’s document root becomes domains/<domain>/current/<web directory>.

Anything the site writes inside a release, such as uploads or caches, is gone after the next deployment unless it is a shared path.

Releases lists the five newest releases. Make live switches the site back to an earlier release a deployment completed, at once; deploy commands don’t run again, so database changes stay as they are. Deployments lists past deployments, whether you or a push started them, with their logs.

Deploy on push. Turn on gives a webhook URL and a secret, shown once: add them on your Git host as a webhook for push events (GitHub and Gitea/Forgejo: content type application/json). To use a secret your Git host made instead, such as GitLab’s signing token, click Use my Git host’s secret. Every push to the branch then deploys it; a push during a deployment waits for it and deploys once it ends. New secret replaces the secret at once. The tab shows when the last delivery came and what it did. The Git host has to reach the panel at the webhook’s URL and accept its certificate. See PHP → Deploying on push for the details.

Disconnect removes the repository settings, the token and the webhook. The site keeps serving its current release, and the releases and shared files stay in domains/<domain>/.

Without the tab, ask your administrator: Git deploy is a package setting, off unless they turn it on.

What you can change vs. what the admin controls

You may change PHP version (from the subset your package allows), SSL on/off, DNSSEC on/off, redirects, aliases, mail enable/disable.

The admin controls listen IP (selected from the IP Manager pool), maximum domain count, and quota-related suspension. The admin may also pin SSL on or force a specific PHP version on a domain; in that case the relevant control is read-only on your side.

Nginx options and rewrite rules

Three extra per-domain tabs — Domain options, Rewrite rules, and Advanced directives — appear only when your administrator has enabled tenant domain options for the server. Until then the tabs are hidden, and the domain’s Overview shows a short note that your administrator can turn these controls on.

When they are enabled you can, on your own domains:

  • Domain options — set a curated, safe set of nginx options: maximum upload size, HSTS, the common security headers (X-Frame-Options, X-Content-Type-Options, Referrer-Policy), and gzip. You supply values; each option renders to a fixed, vetted directive — never raw config.

  • Rewrite rules — add structured rules that the panel turns into vetted nginx directives; you never write raw config. The kinds available to you are:

    • rewrite — its target must be a local path (no scheme or host, so it can never become an open redirect or a proxy to another service).
    • custom_header — adds one response header. The headers the panel manages for security — Strict-Transport-Security, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy — can’t be set here; use Domain options for HSTS and the security headers instead.
    • Deny paths — block all access to files by extension (for example hide .env, .sql, .bak, .log). You supply a list of bare extensions and the panel builds the matching rule; PHP files are handled by the server and can’t be blocked this way.
    • Static cache — set a long cache lifetime for files by extension (for example pdf, mp4). Common web assets (css, js, images, fonts) are already cached by the server, so those are declined; and PHP-family extensions are refused so a source file is never served as a static download.
    • Front controller — for an app with its own router. It sets where a request goes when it matches no file or folder: a PHP script (by default /index.php) and the query string passed to it (by default $query_string). The panel writes it as try_files $uri $uri/ <script>?<query>; in the site’s location /. Files and folders that exist (CSS, JavaScript, images) are still served as they are, and PHP keeps running the way the panel sets it up. For example, the script /index.php with the query mod=$uri&$args sends /users/edit/123 to /index.php?mod=/users/edit/123. The script must be a .php path from the site’s root folder; the query can use letters, digits, _ . - = & / % and the variables $uri, $args, $query_string, $request_uri, $document_uri and $is_args. A domain has one front controller, and it applies only when the domain runs PHP. If you also turn on page caching, keep in mind that a query other than the default $query_string means every routed page reaches PHP with a query string, so those pages are never served from the page cache (existing files still are).

    Every rule is validated before it is applied. Deny paths, Static cache and Front controller don’t apply to a domain that is served entirely by a reverse proxy — on those, the proxy handles every request before these rules are reached.

    If you are migrating from another host, Import from an nginx config lets you paste a raw nginx snippet and converts the parts that map to these rules (rewrites, response headers, extension deny blocks, extension expires caches, and a location / { try_files $uri $uri/ /index.php?...; } block, which becomes a Front controller) into typed rules you can review before saving. An imported front controller replaces the one the domain already has. Anything else that routes, proxies, or reads files (proxy_pass, root, alias, return, other prefix location blocks) is listed as not-imported rather than applied — those stay admin-only.

  • Advanced directives — a small raw-directive box for response tuning only. Just three directives are accepted — add_header, expires, and etag — one statement per line, no { } blocks and no backslashes. Headers the panel manages for you (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Content-Length, Transfer-Encoding) are rejected so you can’t accidentally weaken them. If a line is refused you see exactly which one. Anything that routes, reads files, or proxies is not accepted here — those stay admin-only.

Under Rewrite rules, if your administrator has added their own raw nginx directives to your domain, they are shown to you read-only as Administrator-managed directives — so nothing that shapes your site’s config is hidden from you, even though only an administrator can change it.

Reverse-proxy targets (proxy_pass), file paths (root / alias), location blocks, IP access rules, and PHP settings stay admin-only whether or not tenant domain options are enabled. Your administrator turns the feature on under Server Settings → General.

CLI

If you have SSH access to the panel host (operators only, tenants do not have shell access), the same operations are available via jabali domain list / create / enable / disable / delete.