Dashboard
Notifications
alerts, drills, nightly jobsStorage
today's backups on the system disk, older ones on the backup driveResource budgets
used of availableDisk cleanup
checking…Essentials
Hosted websites
—Panel sign-in
email + OTP activeTelegram alerts
—Deploy results, go-lives, health alerts, recoveries and auto-rollbacks are pushed here. No chat ID? Save the token, message your bot once on Telegram, press Detect chat.
Backups
—Hosted on this server
Domains
from your Hostinger account — migrate any of them hereQyverix AI
—Mail engine
—Mail domains
every domain shares the same client settings: mail.qyverix.inAny domain in your Hostinger account. MX, SPF and DKIM records are created automatically — inbound mail starts arriving on this server once the MX change propagates.
Domain health
the four DNS requirements, checked live — Fix uses the Hostinger APICatch-all
misspelled or unknown addresses land in one inbox instead of bouncingMailboxes
real accounts — SMTP, IMAP, POP3 and webmailMailbox avatars
shown in webmail when reading mail from/to the addressAliases & forwarding
extra addresses without extra mailboxes — external forwards workAutomatic DNS
one token removes every manual DNS stepCreate it at hpanel.hostinger.com → Account → API. With it the panel manages site A records, DKIM TXT and webmail DNS by itself.
Relay (how mail leaves this machine)
direct delivery works to some servers but Gmail/Outlook refuse this IP (Spamhaus PBL) — the relay makes it dependableyour Hostinger plan includes smtp.hostinger.com
Space separated — each gets a DKIM key.
DKIM records
add each at Hostinger DNS as TXT — signing already works; publishing makes receivers trust itSend a test
queues locally, delivers via the relayProvision database
one DB + one role per appDatabases
Websites by size
app directory on the system disk · source checkout · archivesBackup drive
what the SSHD holdsFree up space
Docker images and build cache from old deploysGuided restore
always into a scratch copy — never over live dataFiles land in a dated folder under /var/lib/qyverix/restore-out; databases appear as restore_<name>_<timestamp> next to the original. Inspect the copy, then promote it yourself — the panel never overwrites live data.
Manual backup
limit: once per hour per target — automated schedules keep running regardlessRestore drill
every Sunday, newest backups restored to scratch and checked against liveRestic snapshots
local + Pentium offsitePostgreSQL point-in-time (pgBackRest)
Schedules
AutomatedBackup & restore history
from the activity logTLS certificates
live check, cached 10 minZone records
live from Hostinger — edits apply immediatelyDNS lookup
read-only, any registry domainHost services
—Live logs
journald follow via SSE— select a unit and Follow —
Create a cron job
runs as the operator user · output captured per jobCron jobs
—Give someone access
three steps · no technical knowledge neededType their name and press the button. You will get a key and a ready-written message — copy it and send it to them. That is the whole job.
They already made their own key — paste it instead
Safer, because their private key never touches
this server. Ask them to run ssh-keygen -t ed25519 and send you the
contents of ~/.ssh/id_ed25519.pub.
Someone cannot get in?
—After several wrong attempts the server blocks that address for a while. If a teammate is stuck — or you are — unlock it here. Blocking stays switched on: anything that starts guessing again is blocked afresh.
Who has access
—The steps, if you need them separately
already included in the message above1. Save the key on your own computer and lock the file. SSH refuses a key other people can read.
mkdir -p ~/.ssh && chmod 700 ~/.ssh nano ~/.ssh/qyverix # paste the key, then Ctrl-O, Enter, Ctrl-X chmod 600 ~/.ssh/qyverix
2. Connect.
ssh -i ~/.ssh/qyverix qyverix@103.178.44.194
3. Optional — shorten it to ssh qyverix
by adding this to ~/.ssh/config.
Host qyverix
HostName 103.178.44.194
User qyverix
IdentityFile ~/.ssh/qyverix
IdentitiesOnly yes
Permission denied — the key is not being offered. Check the path after
-i, and that you ran chmod 600.
It hangs, then times out — the address is blocked. Unlock it above.
Never send a private key over a public channel, and never share one between two people.
If one leaks, revoke just that key above; nobody else is affected.
Activity log
—Terminal
connectingA real login shell as qyverix on srv.qyverix.in — the same environment you get over SSH, no SSH client needed. Sessions keep running when you close the tab: start a build, come back later, the scrollback is still here. Every session is recorded below.
Session history
—Qyverix Cloud
Loading…Needs attention
Customers
—Users
—Server sites
Loading…Every site running on this server, with its health and the workspace that holds it. Allocating one lets that customer see and operate a site we are already hosting for them — nothing is deployed or moved.