Manage Websites¶
Website management allows you to create, configure and manage your websites. You can select PHP versions, customize PHP settings, use preview domains, view logs and use deployment tools such as Composer and Git.
Overview¶
The website table shows all your websites with the following information:
| Column | Description |
|---|---|
| Preview | Thumbnail image of the website |
| Domain | Primary domain of the website |
| PHP Version | Active PHP version (e.g. 8.1, 8.2, 8.3, 8.4) |
| Document Root | Path to the web directory |
| Status | Active or Disabled |
The table supports search, sorting and pagination.
Create Website¶
- Click Create Website
- Fill out the form:
| Field | Required | Description |
|---|---|---|
| Domain | Yes | The domain for your new website |
| PHP Version | Yes | Desired PHP version (8.1, 8.2, 8.3 or 8.4) |
| Document Root | No | Subdirectory within your webspace (default: domain root) |
- Click Create
The system automatically configures:
- Nginx configuration with security policies
- PHP-FPM pool for your website
- Directory structure on the server
- Upload directory protection (PHP execution blocked)
Quota Check
You can only create as many websites as your hosting package allows. You can see the remaining quota on the dashboard.
Edit Website¶
Click on a website in the table to open the detailed configuration.
General Settings¶
| Field | Description |
|---|---|
| PHP Version | Change PHP version (8.1 / 8.2 / 8.3 / 8.4) |
| Document Root | Adjust the web directory |
| Status | Enable or disable the website |
www ↔ Bare Domain Redirect¶
So search engines and browsers see only one canonical address for your domain, you can redirect automatically between www.example.com and example.com (HTTP 301):
| Option | Effect |
|---|---|
| Off | No automatic redirect (default) |
| Redirect to www.example.com | example.com permanently redirects to www.example.com |
| Redirect to example.com | www.example.com permanently redirects to example.com |
Can't be saved if the application already redirects
If your website itself already redirects in the opposite direction (e.g. a WordPress "site URL" setting or an .htaccess rule), this option cannot be saved — the two 301 redirects would otherwise call each other forever. In that case, check and change the setting in your application first.
PHP Configuration¶
You can customize PHP settings per website:
| Setting | Description | Example Value |
|---|---|---|
memory_limit |
Maximum memory per PHP process | 256M |
max_execution_time |
Maximum execution time in seconds | 300 |
max_input_time |
Maximum input time in seconds | 300 |
post_max_size |
Maximum POST size | 128M |
upload_max_filesize |
Maximum upload file size | 128M |
max_input_vars |
Maximum number of input variables | 3000 |
max_file_uploads |
Maximum number of simultaneous uploads | 20 |
display_errors |
Show errors in the browser (development only!) | Off |
error_reporting |
Error reporting level | E_ALL & ~E_NOTICE |
session.gc_maxlifetime |
Session lifetime in seconds | 1440 |
opcache.enable |
Enable/disable OPcache | 1 |
display_errors
Only enable display_errors during development. In production, this can expose sensitive information.
Reset OPcache¶
If your website still shows old content after code changes, you can reset the OPcache. Click Reset OPcache in the PHP configuration section.
Nginx Directives¶
You can add custom Nginx directives for your website (e.g. redirects, headers, caching rules).
- Open the Nginx Directives tab
- Enter your directives in the text field
- Click Validate to check the syntax
- Click Save to apply the changes
Syntax Errors
Invalid Nginx directives are rejected before saving to prevent taking your website offline. Use validation before saving.
Preview Address¶
The preview makes your website reachable under a second address while the real domain still points somewhere else. The typical case: your live site is still with your previous provider, the new one is to be built here, and the domain should only be switched over once the new site is finished.
Two ways to get an address¶
| Way | Requirement | When it fits |
|---|---|---|
| Your own address (recommended) | A single A record in your DNS zone, e.g. build.your-domain.com, pointing at this server |
Whenever you can reach your DNS zone — no matter where it is managed |
| Generated automatically | Your provider has set a DNS wildcard record on the panel domain | When you cannot add a record of your own |
Your own address is the more reliable route: it needs nothing your provider has to set up first, and it gets its own SSL certificate.
Switching the preview on¶
- Open the website details (or, in the WordPress toolkit, the tile of the installation) and click Preview
- Enter the address you want — e.g.
build.your-domain.com. Leaving it empty means: use the automatically generated address - Click Check. The panel looks up whether the name already points at this server and shows the finished DNS record ready to copy
- Confirm with Switch preview on
What the check reports:
| Result | Meaning |
|---|---|
| Points at this server | All set. The SSL certificate is obtained automatically |
| Points at a different server | The name is already in use — pick another one, or repoint the record |
| No A record found | Add the record shown to your zone |
| Could not be checked | The DNS query went unanswered. That does not mean the record is missing — you can switch the preview on anyway |
The order does not matter
You can switch the preview on and add the DNS record afterwards. The
certificate follows once the record takes effect — at the latest on the
panel's daily pass. Until then the preview runs over http://.
WordPress¶
For WordPress the preview is more than a second name: WordPress stores its own
address in the database and redirects every request to it. Switching the preview
on makes the panel move that address (siteurl and home, including the
references inside your content) to the preview address — which is the reason the
preview works at all while the domain does not point here yet.
Login and Open in the toolkit then go to the preview address automatically.
Switching the preview off¶
Click the same preview icon again. For WordPress the stored address is moved back to your domain in the process. Do this once the domain points at this server — afterwards the site is only reachable via the domain.
A preview is not staging
The preview shows the same website under a second name — there is no second copy. If you want to work on a test copy and merge the changes later, use staging.
Log Browser¶
You can view the access and error logs of your website directly in the panel.
- Open the website details
- Click Logs
- Select the log type:
| Log Type | Description |
|---|---|
| Access Log | All HTTP requests to your website |
| Error Log | PHP errors and web server errors |
Features¶
- Filter — Filter by search term or HTTP status code
- Auto-Refresh — Updates the display every 5 seconds
- Download — Download the log file
- Log Rotation — Information about automatic log rotation
Composer¶
If your hosting package includes Composer support, you can manage PHP dependencies directly in the panel.
Check Status¶
The Composer tab shows whether a composer.json exists in your website's document root and which packages are installed.
Install Dependencies¶
- Open the Composer tab
- Click Install — runs
composer install - Wait until the installation is complete
Update Dependencies¶
- Click Update — runs
composer update - Wait until the update is complete
composer.json required
Composer only works if a valid composer.json exists in your website's document root.
Git Deploy¶
If your hosting package includes Git Deploy, you can deploy your website directly via Git.
Initialize Git¶
- Open the Git tab
- Click Initialize Git
- The system creates a bare repository on the server
Add SSH Key¶
To push from your local machine to the Git repository, you need to add an SSH key:
- Switch to the SSH Keys tab
- Click Add SSH Key
- Paste your public SSH key
- Click Save
Deployment¶
- Push your changes to the server repository
- The post-receive hook is triggered automatically
- Alternatively: Click Deploy Manually in the Deploy tab
Commit History¶
In the Commits tab you can see the latest commits received on the server.
Access Restrictions (IP Access Control)¶
You can restrict access to your website by IP addresses:
- Open the Access Control tab
- Select the mode:
- Allow all, block specific IPs — Blacklist
- Block all, allow specific IPs — Whitelist
- Add IP addresses or CIDR ranges
- Click Save
Site Doctor — your website's health¶
The Site Doctor shows you at a glance whether everything is fine with your website — without having to read logs or understand technical details.
- In the website list, a colored dot per site shows its state: green = all good, amber = notice/warning, red = urgent.
- Expand a website and a health banner appears at the top with a score of 0–100 and any issues found, in plain language.
It checks, among other things:
| Check | What it means |
|---|---|
| SSL certificate | Is your certificate expiring soon or already expired? |
| Malware | Were suspicious files found on the website? |
| WordPress security | Are there known vulnerabilities or available updates? |
| Resources | Is your website being throttled by its CPU/memory limit? |
| PHP service | Is your website's PHP service running? If not, one click on Restart PHP service fixes it. |
| Server & PHP errors | Are 5xx server errors or fatal PHP errors piling up in the logs? |
| Storage | Is your storage or file (inode) quota almost exhausted? |
Each issue has a fix button that takes you straight to the solution. Some actions are performed by the panel directly:
| Fix | What happens |
|---|---|
| Restart PHP service | Restarts the website's PHP service (fixes outages & 5xx spikes) |
| Renew now (SSL) | Triggers a certificate renewal (runs in the background) |
| Clean up logs | Truncates the website's log files and frees storage |
Other issues link straight to the relevant place (file manager, WordPress, malware scanner). Use Check again to re-run the diagnosis at any time.
Nothing happens automatically
The Site Doctor never performs an action on its own — you decide, with a click, what gets fixed.
View error details¶
For "PHP errors in your application", Show details reveals the actual recent error lines (file, message, line) — so you see exactly which error occurs without having to dig through logs.
Automatic monitoring & history¶
The Site Doctor also checks your websites regularly in the background. When a new problem appears, you are notified through the Notification Center (in-app and/or email) — so you don't have to keep checking yourself. The health score is recorded, so a small trend arrow shows whether things got better or worse.
Delete Website¶
- Click the delete icon next to the website
- Confirm the deletion in the dialog
Irreversible
Deleting a website removes all associated files, configurations and logs from the server. Create a backup beforehand if you want to keep the data.