The panel, page by page

What this page is for. It says what every page in the panel does, what you will use it for most, and when to leave it alone.

You need

• To be logged in to the panel (First login).

Read this once. It is the difference between hunting for a button and knowing where it lives.

Two groups of pages

The menu is split in two.

Panel pages act on the whole server: Home, Projects, AI, AI Coding, Server, Backups, Activity, Security, Migration, Addons, Settings.

Project pages act on one project: Overview, Deploys, Domain & SSL, Database, Logs, App .env, SixChecker, Staging & Testing, AI agent, AI Coding, Advanced.

Most people run one project, so the two groups feel like one menu. If you run more than one on the same server, a switcher in the top bar chooses which one the Project pages act on. See More than one project.

A website or app — a static website, a Node.js app, a PHP website, WordPress, or one made with Create with AI — has its own menu in place of the Project pages, showing only the pages its kind uses. See Websites and apps.

A window the panel opens — a confirmation, Connect git, a restore — closes only from its own buttons (Cancel, Close, Done). A click beside it only nudges it, so a half-filled form is never lost to a stray click.

The web address tells you which group you are in. …/#/server is a Panel page. …/#/p/default/logs is a Project page. Bookmarks and the browser's Back button both work, and older addresses still work too — #/health, #/disk, #/firewall and #/cloudflare all land on the tab that absorbed them.

The bell

The top bar of every page carries a bell. It is the one place for what waits for you, so you never have to be on the right page to learn of it.

• Waiting for your approval — a change that Tia, an automation or your own AI agent wants to make and may not make alone. The card says who asks and exactly what will run, with Approve and Decline; a command that runs with full control of the server asks you to confirm it is you on the card (your 6-digit code, or your admin password when two-factor login is off). A new request also shows a short notice with Review, whichever page you are on. (In Tia's own chat the card appears in the conversation as well — answer it in either place.)
• Needs your attention — one line per thing that is actually wrong, each with the button that opens the page that fixes it. A stopped service, a certificate close to expiry, a backup that has not run, an available panel update, a disk past its comfortable level — and what monitoring has open right now: a website failing (its button opens that website's error log) or not answering, a job that failed. Failures come first, then what is going wrong now, then the rest; past eight lines it says how many more there are and where: the Health page for check-up lines, AI → Monitoring for what monitoring has open. While monitoring is switched off, what it had open is not listed. When there is nothing, it says All clear.

The number on the bell counts what cannot wait: approvals, checks that fail, and what monitoring has open. Warnings are in the list and never in the number — so a number on the bell always means "look now". The list comes from the last check-up and says when that was; opening the bell asks for a new one.

A temporary login and the demo login have no bell: approvals are the owner's.

Panel pages

Home

What it is for. The first look every day, and the answer to "does anything need me?"

It opens with one line: Needs your attention and how many things there are — Open shows them in the bell (above) — or All clear when there is nothing.

Under it: This server (processor, memory, disk, uptime), then Monitoring, then Your projects (one card each, with its addresses, whether HTTPS is on, whether the app is installed, the last deploy and quick links to the admin and the store), Backups, and Recent activity.

Monitoring is the history behind those three meters: how busy the processor, the memory and the disk have been over the last hour, six hours or 24 hours — your choice, with the buttons in the corner of the card. Each chart carries a red dashed line at 90%: a line that touches it and stays there is the server telling you it needs a cleanup or more capacity. The number beside each label is where it is right now.

Open Per-service usage right now at the foot of that card to see which service is using what — the database, the web server, PHP, the panel itself. It is read only when you open it, so a closed card costs the server nothing.

You will use it for that first line. If it says All clear, close the tab.

Projects

What it is for. Creating and listing projects: 6ammart installs, and the websites and apps beside them. Each 6ammart project gets its own domain, database, Linux user, PHP pool and services.

Create a new project asks first what kind of project it is — 6amMart, or one of the websites and apps — then everything else on one screen: the name, with the short id the server derives from it shown underneath (never asked). Creating a 6amMart project builds the isolated runtime: this project's own database, its own cache service, its own Linux user, its own PHP pool and its own services. Then it hands you Continue to install the app. A website or app opens straight on the page where its next step is. If another job is running, the create queues behind it and says so, rather than being refused.

6amMart's address is not asked here. The web address, its DNS records and its certificates belong to Put 6amMart on this project on the project's Deploys page, which asks for the address while your code uploads and then registers the names, creates the records (always proxied) and gets the certificate for the admin panel and for the website. One question, one place. A website or app may be given its address in the dialog — it is optional — and the panel connects it as soon as the project is set up.

Every card carries the same three facts — its address (and whether HTTPS is on), its status, and the last deploy — so two cards side by side end at the same height, with Open this project on the bottom edge. A WordPress website the panel installed is never deployed: its Last deploy row says when it was set up. A 6amMart card adds one Apps row: the admin app, the customer website and the website's own address. A project that has staging sites says Staging sites (2); click the line to see them, each with its own page and address.

Each project card also shows what is still missing, a rename… link, and a search box once you have several. Renaming changes the label this panel shows and nothing else — see Rename a project.

Do not create a second project on a small server without adding memory first. See More than one project.

AI

What it is for. SixPanel's own AI, in six tabs: Tia, the assistant that runs the server with you, Automations, Monitoring (what went wrong, why, and a one-click fix), Connect (your own AI agent over MCP), Providers — where the AI comes from, for Tia, monitoring and Create with AI alike — and Settings. The Ask Tia button on every other page opens Tia over that page. Full page: Tia, the AI assistant, and AI monitoring.

The AI features need SixPanel Pro (on allsweb.com). Without it each tab shows an upgrade card above what it does; monitoring and its alert emails stay free. See Your AllsWeb account and SixPanel Pro.

Providers.

Add a provider is three steps: how (a subscription, an API key, your own endpoint such as a LiteLLM or OmniRoute gateway, or a model on this server — Ollama or LM Studio), which (Anthropic, OpenAI, OpenRouter, Google Gemini, DeepSeek, Groq, Mistral, xAI, Nous Portal), and Connect: paste the key and press it. Connect checks the key, chooses the model and tests it, and says on each line how it went — or the exact error and what to do. One provider is the Default and answers everything unless you chose otherwise; the first that works becomes it, and saving one starts any Create-with-AI project that was only waiting for it. A Claude or ChatGPT subscription is signed in once on this tab and serves AI Coding and the coding of Create with AI — not Tia or monitoring.

Keys stay on this server and are never shown again; a saved key is only ever sent to the address it was saved for.

With Pro, AllsWeb AI is listed first: no key to paste, paid from your AI credit, with Choose model and Buy AI credit on its row.

Full page: AI providers.

Server

What it is for. The machine itself. It has ten tabs.

Info — every fact about this server, in one place, with copy buttons: your public IPv4 and IPv6 addresses (the values a DNS A or AAAA record needs), the processor and how many cores, memory and swap, which Ubuntu or Debian this is, and the exact PHP, MariaDB, nginx, Redis and Node.js versions — which are what a security advisory is written against, so they are the versions to quote. One button copies the lot as plain text for a support ticket.

Two things on this tab are worth reading rather than skimming:

• Swap. If it says your server is using swap, that is memory being kept on disk, which is far slower than real memory. A little is normal. A lot means the box is short of RAM, and it is the commonest reason a server "feels slow" while every page still works.
• A public address that is not on the server. If the tab says so, your provider puts your machine behind network address translation. That is normal on some hosts, and the public address is still the right one for a DNS record — but it explains why the address you see inside the server is different.

Health — a full check-up: DNS, certificate expiry, services, the database, the queue, the scheduler, disk space, memory, backups, Cloudflare and more — over thirty checks in one view. Each failure carries a plain-language fix that names the page to go to. The row Staging sites names every staging site that is not started, with the reason — a warning, not a failure: a staging site that is not started answers nobody.

Five checks are worth knowing about in advance:

• The app answers requests. The panel dials your project's own hostname on this machine, with the real name in the request, and reports what /api/v1/config gives back — the first call every 6ammart phone app makes. A green services list and a 404 here means your customers get nothing while everything looks fine.
• Shop timezone. 6ammart keeps the shop's timezone inside its own admin panel and applies it on every request. If that value is a name this server's PHP does not know, PHP quietly falls back to UTC — every order time, report boundary and scheduled task is out by the offset while every page renders normally. This check reads the value and says whether the server really has it.
• Database time zone. Every database on a SixPanel server runs on UTC unless you choose another zone for it on Server → Database; your panel timezone only changes what the panel shows. A server set up by an older first-run wizard may have its database on your timezone instead — this check says so and offers Move the database to UTC, which keeps every date your apps show exactly as it is (see Troubleshooting).
• Storefront rate-limit exemption. SixPanel limits abusive traffic at the web server automatically, so one bad source cannot use up the whole site. That check confirms your own storefront is never caught by those limits.
• Customer website. See below — it now catches a website address that was published before the website was ever built.
• Modules enabled with no code. See below — it reads which 6ammart modules your shop has switched on and checks that their code is actually here.

Customer website

This check asks your storefront address for a page, on this machine, and reports what a shopper would get. It is the only row that looks at the storefront rather than the admin app, and it exists because a broken storefront can look perfectly healthy from everywhere else: if your site sits behind Cloudflare, visitors may keep seeing a cached copy while nothing is running here at all.

One case it now catches that it used to miss. If this server publishes a website address for a project but the website has never been built, every shopper who follows that address gets an error page — a 503 — and it never recovers on its own, because there is nothing there to start. The check turns orange and offers you the two real repairs, because only you know which one you want:

• install the customer website from the project's Deploys page — see The customer website; or
• remove the website address under Domain & SSL, if this shop sells through the phone apps only, so nothing advertises an address that leads nowhere.

A project that sells through the apps alone and has no website address at all is not a fault and never nags you. That row stays grey and simply says there is no customer website on this project.

Modules enabled with no code

6ammart is built from modules — RideShare, Rental, and so on. Its own settings file records which ones are switched on, and that list can name a module whose code is not on this server. This is how plain CodeCanyon 6amMart arrives: the download switches nine modules on and ships three. You did nothing wrong, and it is worth knowing that before you read the row.

So the check does not count them. It reads how each missing module is actually reached, and grades what it finds:

• red — a page on this server asks for a missing module in a way it cannot skip. On untouched 6amMart v4.1 that is RideShare: the rider sign-up page answers a 500 error to anyone on the internet who opens it, and the tool everything else uses to list the app's pages stops working too. Nothing else on the Health page notices, because the home page, the apps and the admin panel are all fine.
• orange — the missing module is not being reached today, so nothing is erroring. Either the app only loads that code once the module is properly installed, or every place that reaches for it is guarded. Worth tidying up, not an emergency.
• green — every module switched on for this shop has its code here.

For orange the fix is 6ammart's own switch: turn the absent modules off, so the list matches what is really installed. The row carries a Switch off the missing modules button that does it for you, right there on the Health page — it works on plain CodeCanyon code, which does not ship SixChecker, and the page checks again when it finishes.

Red is different, and the row says so. That page asks for the module's code before it checks whether the module is switched on, so switching it off tidies the list but cannot stop the 500 — on untouched 6amMart 4.1, /rider/apply answers 500 either way. The page works once the module's folder is in Modules/, and the row stays red until then. Nothing is deleted and no module you paid for is lost: if you were sold a module and did not receive its code, 6amtech can supply it, and switching it on again is all that is needed once the code is here.

On some servers the panel will tell you to do it from 6ammart's own Addons page instead, and say why: on a project installed from git, that settings file is one the panel must not write, or the next deploy would refuse to run.

Services — the programs this whole machine shares, each on its own row: the web server (nginx), PHP, the database (MariaDB), and one cache row per project. Each row says what the program does, whether it is running, and gives you two things: Restart and Live logs.

Two details worth knowing before you press anything here:

• Restart on the web server and on PHP is a graceful reload, not a stop and start: the program is told to re-read its configuration and no visitor's request is dropped — including the one your own click is riding on. (On PHP, a request already being served gets up to five seconds to finish; only one that runs longer than that, such as a large export, is ended.) On the web server the configuration is checked before anything is asked of it, so a file it would not accept means nothing is touched and the page tells you exactly that. The cache rows are an ordinary restart, which is a second or two.
• There is no Stop button, on purpose. These are shared by every project on the server, so stopping one takes every shop on the machine offline until somebody comes back and starts it again. A restart is a few seconds and recovers by itself; a stop is an outage that waits for you.

The cache rows are the exception to "shared": each project has its own, so restarting one leaves the other projects alone. The page labels every row either shared by every project or this project only, so you can see which you are about to touch.

You will use it for the two Health rows that send you here — the database, and the app answers requests — because both of those fire when the machine itself is what is wrong.

Resources — where the disk went, per project (app code next to customer uploads) and per website (a Websites row, with each website under it), and a tick-list of safe things to remove: Laravel caches and logs, old system logs, the package manager's cache, PHP temporary files and the panel's own job leftovers, each with an estimate of what it frees. Customer uploads and the database are never touched by the cleanup. There is also a switch for running the cleanup automatically.

Firewall — the exact rules this server needs, with copy buttons. See Firewall and ports.

Scheduled — everything the panel does by itself on a timer: certificate renewal, backups, the backup restore test, disk cleanup; then each shop's tasks, and each website's own cron jobs with how its last run went (a failed one turns the banner amber and links to that website's Cron page).

PHP and Node.js — the versions websites can run on: the server's own first, extra ones as optional downloads, and every website on each version, movable from there. See PHP and Node.js versions.

Database — the one database server (MariaDB) every project shares: whether it is running, its version, connections, memory and data at a glance, Restart and Live logs; its time zone (UTC unless you change it — a change keeps every stored date reading as it does now); every database on the server and the project or website it belongs to; and your own MariaDB settings. See The database server.

Terminal — a shell on the server as root, in the panel itself (your password is asked first), the terminals open right now, and SSH for the whole server: on which port, and a switch to turn it off once the panel answers on its own domain. What you type is never recorded. See Terminal and SSH.

You will use it for the Info tab whenever something outside the panel asks what your server is — a support form, a DNS record, a firewall rule; the Health tab every time something feels wrong; and the Resources tab the moment the disk passes about 90 per cent. A full disk stops the database, and a stopped database stops the site.

Backups

What it is for. Choosing where backups go, how often they run, and getting data back when something goes wrong.

Backups are incremental: after the first one, only the changes are stored, so later backups stay small and fast.

You will use it for three things, and they matter more than everything else in this manual: send backups somewhere that is not this server, keep your own copy of the backup password, and read the Can your backup be restored? card, which loads your newest backup into a throwaway database every week and tells you whether it really works.

Full page: Backups.

Activity

What it is for. One list of everything that has happened on this server — what a person did and what the panel did by itself, in the same stream.

You will use it for the question "what happened to my server", and it is usually answered by the first few rows: everything here is newest first. The Project filter narrows it to one 6amMart project or one website — each row carries that name — and Server-wide shows only what belongs to neither.

Full page: Activity.

Migration

What it is for. Moving one project — or this whole server — to another server, without touching your DNS.

Three tabs, in the order you use them: Servers to pair the other machine once, then One project or Everything depending on how much you are moving. A single-project move needs SixPanel already installed over there; a move of everything installs it on a plain empty server for you.

You will use it for outgrowing a server or changing provider. Nothing is switched over for you — you decide when the DNS moves.

Full page: Move projects to another server.

Addons

What it is for. Paid extras for SixPanel, like 6amMart for SixPanel — the addon whose code creates, installs and updates 6amMart shops. Upload the zip from CodeCanyon once, enter its purchase code, press Activate: 6amMart then appears in Create new project, and every SixPanel update keeps the addon current. Each addon's card shows its version and its licence (active, support until, last checked) with Refresh licence, Release (to move it to another server) and Remove; below, the addons AllsWeb sells. On a server that ran SixPanel before addons, the 6amMart card says Included with this server and needs no zip and no code.

A licence that lapses never takes a shop down: running shops, backups, certificates and monitoring carry on; only creating, installing and updating wait for it.

Full page: Addons.

Security

What it is for. Everything about who can get into this panel, and a record of what they did.

It holds your login name, your password, two-factor login, the list of browsers signed in right now, the secret panel link and entry code, the panel's own domain and certificate, the panel port, the login address list, the addresses you have blocked, the addresses currently locked out after failed logins, temporary logins, the public demo login, and the activity log.

Blocked addresses is the one to reach for when a single address is bothering your panel. It shuts that address out completely and at once — even a session signed in from it right now — and it covers the panel only, never your shop. The panel will not let you block your own address or 127.0.0.1, and sudo sixpanel block clear always lets an address back in from the server itself.

You will use it for the activity log when something changed and you do not know who changed it, and for handing a developer a login of their own instead of your password.

This cannot be undone — pressing Change entry code kills the old panel link immediately, on every device including the one you are using. Save the new link when it is shown.

Full pages: Security and Let someone else in.

Settings

What it is for. How the panel talks to you, and the few buttons that take something offline. Its tabs: General, Alerts, Repairs, Performance, Maintenance, Updates, Cloudflare, AllsWeb account and Problem reports. (Pairing another server lives on the Migration page.)

• General — language, panel timezone and alert email, the basics from the first-run wizard, changeable any time. If alert email cannot reach you yet, its card has a button straight to Alerts.
• Alerts — email (SMTP) — give the panel a mailbox so it can write to you when a job fails, a service crashes (whether it comes back by itself or stays down — the email says which), health turns red, the disk passes 90 per cent, someone is locked out after wrong passwords, or a certificate renewal fails. At most one email per topic every six hours — each failed service is its own topic, so one never silences another, and an email your mail server refused is sent again by the panel itself 15 minutes later (twice at most) instead of being lost for six hours. Press your provider's button — Resend, Gmail, Outlook / Microsoft 365, Brevo, SendGrid, Mailgun, Amazon SES or Zoho — and the server, port and encryption fill in (on the port least often blocked, where the provider has one); you add the user name and password. Typing a port sets the encryption that belongs to it, and a test email that arrives saves the settings it proved. The first-run wizard's last screen offers the same form, so most servers finish setup with alerts already working.

About the port, because this is where it usually goes wrong. Most hosting companies block outbound 25, 465 and 587 from a server, to stop a compromised box sending spam. Your mail provider is fine and your password is right, and the test send still fails with a timeout that explains nothing. So the form lists the alternatives too:

If a test send times out, try the 2000-series port for the same encryption before changing anything else — that one change fixes it most of the time. Your provider's own documentation will list which of these it accepts.

The saved password only ever goes to the server it was saved for. Leave the password empty to keep it — but when you change the SMTP server, type it again: the panel never hands the saved one to a different server, whether you save or press Send a test email (the empty field says so).

• Repairs — automatic repairs: once a minute the panel checks the handful of things that take a site offline, and for a few of them it does the same repair you would do by hand. It is on by default. It never deletes anything, never restarts the database, and never starts a service you stopped yourself; each repair has a daily ceiling and a cooldown, and one it keeps failing at is abandoned rather than retried forever. Everything it does is on the activity log, and it emails you either way.
• Performance — auto-tune: the install sized the database, the cache and the PHP workers for the hardware you had at the time. If you later give the server more memory or more processors, open this card and press Apply tuning. The affected services pick up the new sizes and one page load may feel slow while they do.

The suggested column is the same calculation the installer used, so on a server whose hardware has not changed it will usually say there is nothing to do. Where a suggestion is lower than what you are running now — because you removed a project, or because you raised a number yourself — the job says so in its log before it writes, since a later update will not put it back.

• Updates and Maintenance — panel updates, server security updates and Restart this server.
• Cloudflare — see Cloudflare.
• AllsWeb account — link this server to your account on allsweb.com: see AllsWeb account and Pro.
• Problem reports — what you, or Tia, told AllsWeb support went wrong, and the replies: see Problem reports.

You do not have to set up anything to keep the queue worker, the scheduler or the websocket service alive. Each one is a systemd unit with a restart policy, so it comes back after a crash and after a server restart. Do not add your own systemd units or Supervisor for them — two supervisors fighting over one process is a real way to break a working site.

There are three different updates on this server, and mixing them up is the most common misunderstanding in this product:

Restart this server is on the same tab. You have to confirm, and the site is offline for the whole restart.

Full pages: Update SixPanel itself and Server updates and restarts.

Project pages

Overview

What it is for. One project at a glance: its addresses, whether HTTPS is on, whether the app is installed, which services are up, the versions, the last deploy, the last backup, recent activity and the newest error lines from the application log. Anything the Health checks found wrong with this project is listed right under the four tiles, worst first, each with a button to the place that fixes it — so "open and healthy" only ever appears when Health agrees.

You will use it for landing somewhere sensible after switching projects.

Deploys

What it is for. Getting 6ammart code onto the server and keeping it current.

The first screen answers three questions and nothing else: is my project live, which version is running, and what do I press. Depending on the state you see Install 6ammart Admin, Get the latest code, or a note that a domain has to be added first.

You can install from a git repository or by uploading the CodeCanyon zip — both are first-class, and the page offers them side by side. Below the first screen sit the customer website's own install and update, automatic deploys on git push (one webhook per repository, each with its own address and secret), the full deploy history with rollback, and the wizard for moving a project here from another server.

Every long action runs as a job with a live log you can watch.

Full pages: Install your 6ammart code, Deploy and update, Move an existing site here.

Domain & SSL

What it is for. Connecting names to this server and securing them.

There are three groups: Admin site (main domain), Customer website, and Live updates (websockets). Each name moves through three chips: added → pointed → secured.

Full page: Domains and HTTPS.

Database

What it is for. Size, table counts, the biggest tables, slow queries, a speed check, quick safety copies, and phpMyAdmin when you really need to look inside.

Make a backup now is the button to press before anything risky, and there is a download for a copy you keep yourself.

The Speed card is worth knowing about. Your project keeps shortcuts that let it find orders and products without reading through every row, and depending on where your 6ammart code came from some of them may never have been created. The card names the missing ones and builds them on one press. Safe to run while the site is busy; nothing is deleted.

Database clock opens only when your shop's own timezone differs from the database's — which, since every database runs on UTC, is any shop outside UTC. That is expected: the shop writes and reads its own dates on its own clock. The card names the few columns the database fills in itself and what that costs.

Open in phpMyAdmin opens the familiar database browser signed in as this project's own database user — no password to copy — and turns it on first if it is off. It is reachable only while you are logged in to the panel; Turn off when you are done. Server → Database has the same card for the whole server.

This cannot be undone — the danger zone's import replaces everything. Orders and users that are not in the file you upload are gone. When the file is a whole shop, tables it does not contain are removed as well once it has loaded, so the database changes run cleanly afterwards. A file holding only a few tables is added to what is there, and a file that fails to load removes nothing.

The import runs as a job. The page answers as soon as your file has arrived, and a card at the top of the Database page shows each step: the queue worker and the scheduler stopped for as long as the file runs, the database as it is kept first (the newest two such copies stay on the server; with no room for one the import is refused and nothing changes), your file, the tables it left behind, and how many database changes the file leaves for Run migrations. A large file takes minutes — you can leave the page, and Activity keeps the job's log. When it ends, the page and that log say where the copy of the database as it was is kept. If it fails, a dialog that stays says why, in the database server's own words, and — when your file had started to run — where that copy is and the one line that puts it back. It says "The import did not start" when it stopped before your file ran, which means the database is as it was.

Logs

What it is for. Every log this project writes, in one place, live: the application's own log, the web server, PHP, the queue worker, the scheduler, the websocket service and the customer website.

App errors is the first thing on it — the newest error lines from the 6ammart log, grouped, with how many times each has happened and when it was last seen. Empty is exactly how it should look.

You will use it for the moment something fails: the error usually explains itself here in one line.

App .env

What it is for. The 6ammart app's own settings file, made safe to edit.

Settings that only accept certain values get drop-down lists and switches, so a wrong value cannot be typed. Secrets stay hidden until you press Reveal (each reveal is written to the activity log). Settings this server manages — database, domain, websockets — are shown but locked.

Press save and the panel writes the file, rebuilds the settings cache and reloads PHP without dropping visitors.

The Health tab checks this file against the reference file your 6ammart code ships with, and names every setting that is missing or empty along with what it breaks. Payment keys and Firebase push keys are not in this file at all — 6ammart keeps those in its own admin panel.

Do not change APP_KEY. It locks every user out and makes encrypted data unreadable. The page marks that one, and a few others, as careful.

Some mail settings can also be changed inside 6ammart's own admin panel, and those win over this file. The page says so at the top.

SixChecker

What it is for. SixPanel looks after the server. SixChecker looks at your project's own settings — a missing payment key, a mailbox that cannot send, debug mode left on. This page shows what it found, worst first.

Full page: SixChecker.

Staging & Testing

What it is for. Trying a change somewhere safe before it goes live. A staging site is a private copy of this project, complete and separate — its own database, files and address — and nothing done on it reaches the live shop. The page lists this project's copies, one card each, with Create staging site at the top; opened on a copy, it shows that copy and Open production.

Full page: Staging & Testing.

AI agent

What it is for. Giving this one project — and nothing else on the server — to Claude Code, Codex, Cursor or another AI agent. Three cards: Connect your AI agent to … (an agent on your own computer: pick it, press Connect, paste what the page shows), Connections to this project (the ones made for it; Remove stops one at once), and Let an agent work on the server itself (an agent in a shell on the server, as the project's own account). The page is the owner's.

Full pages: Connect your own agent and An agent on the server, inside one project.

AI Coding

What it is for. Having the code of this project changed for you: you write what you want in a chat, and a coding program (Claude Code, or Codex) does the work on the server as the project's own account — on a staging site first. The panel menu has an AI Coding page too, for the whole server: what it needs, the programs and their versions, and every project's sessions. Needs SixPanel Pro. Full page: AI Coding.

Advanced

What it is for. The tools you rarely need, on three tabs.

Files — a file manager for this project's code: the app and, if you run it, the customer website. Upload, edit, rename, move, compress, extract, change permissions, download, delete. Rows marked protected hold things the site cannot live without — uploads, settings files, anything under version control — and the server refuses to delete or rename those. The manager cannot see outside your project's folders: SixPanel's own settings, the database files and the panel's code are not reachable from here. That is a safety boundary, not a missing feature. Changes take effect immediately, and there is no undo.

Selecting and opening. Click a row to select it. Hold Shift and click another row to take every row between the two; hold Ctrl (⌘ on a Mac) to add one row or take one out; the box at the start of a row does the same. The bar under the toolbar then holds what can be done with the selection — Download, Copy, Move, Compress, Extract, Rename, Permissions, Delete — and Clear the selection. Double-click a row, or click its name, to open it: a folder opens, a text file opens in the editor, a picture as a preview. The keyboard works on the list too: the arrow keys move, Enter opens, Delete deletes (it asks first), F2 renames, Ctrl+A selects every row and Backspace goes up one folder. Every folder in the path above the list is a link, and the pencil at the end of the path lets you type one.

A long action shows how far it is. Compress, extract, copy, move, delete and permissions start at once, and a strip above the list says what is happening: the item in hand and how many of how many are done, or — where that cannot be counted — how long it has been running. You can reload the page or go to another one and come back: the strip is where it was. When the action ends you are told, and the list is read again; if part of it could not be done, the strip lists what was not done until you close it. One such action runs in a project at a time: until it ends, the other actions — in the toolbar and in a row's menu — are dark, and Refresh still reads the folder. It cannot be cancelled half-way, because none of them can stop in the middle and leave the folder in a sound state.

If your project came from a git repository, the code files git looks after are read-only here: the panel refuses to save, rename, delete or re-permission them, and the refusal explains why and gives you the command that does the job properly. Editing one used to stop every later deploy of that project. Your .env, your customer uploads and the settings files 6ammart writes itself stay editable, and a project installed from a zip is unaffected — every file is editable there. See Deploy and update your code.

Cron — this project's timed tasks: 6ammart's own schedule, plus any job you add yourself. 6ammart needs its scheduler running every minute for subscriptions, reports and cleanups; this tab shows whether that is alive.

Services — the background programs that run this project, each one separately: PHP, the queue worker, the scheduler, the websocket service and the customer website. Start, stop or restart each one, and open its log. This tab also holds Live order updates — one button that sets up real-time order pings — and the websocket domain wizard. See Live order updates.

The web server and the database are not on this tab, because they are one program each for the whole machine rather than for this project. They live on Server → Services — see above. This project's cache is its own, so the row here restarts only this shop's. Stopping it also stops this project's queue worker and scheduler, because both read the cache all the time and would only fail without it; they start again by themselves once the cache is running.

How to check it worked

You have finished this page when you can answer, without looking: which page do I open to reload the web server, which page restarts just this project's workers, and which page tells me what is wrong?

(Server → Services — and it is a graceful reload, not a restart. Advanced → Services. Server → Health.)

If it went wrong

• A page says not available on this panel yet — SixPanel is older than that feature. See Update SixPanel itself.
• A page will not load at all — check Server → Health, then When something is broken.