Settings

Overview

The Settings page lets you manage your site's core configuration: domain name, temporary lock, resource protection, Wildcard Subdomain, owner, site type, web directory, PHP version, proxy port and Git configuration.

INFO

The www/non-www redirect and Force SSL options have moved to their own page. See URL Redirects.

For an alias domain, this page only shows the Domain, Temporarily Lock, Resource Protection and Update Web Directory sections; the rest are managed on the main website.

Instructions

1. Update Domain Name

1. Enter your new domain name in the Domain field.
2. Click Update and confirm in the dialog.

• Note: Changing the domain is intended for sites still under development, not for sites that are already live.

2. Temporarily Lock the Website

1. In the Temporarily Lock section, click the Temporarily Lock button to suspend the website. While locked, visitors receive an error response or the server's default page.
2. To bring the website back, click Unlock the website.

Schedule Toggle

You can schedule your website to be automatically disabled or re-enabled at a specific date and time. This is useful for planned maintenance windows or temporary shutdowns.

1. In the Temporarily Lock section, expand the Schedule toggle panel.
2. To schedule a lock, select a future date and time in the Disable at field.
3. (Optional) To automatically unlock the website later, select a date and time in the Enable at field. The unlock time must be after the lock time.
4. Click Set schedule to confirm.
5. Once scheduled, an alert will display the scheduled time. You can cancel a pending schedule by clicking Cancel next to the alert.

• Note: A schedule runs only once and is removed automatically after it runs.
• Note: If you manually lock or unlock the website before the scheduled time, the schedule will still run at the specified time.

3. Resource Protection

Resource Protection prevents your site from being deleted by mistake.

1. In the Resource Protection section, click Enable Resource Protection.
2. While enabled, the site cannot be deleted until you click Disable Resource Protection.

See Resource Protection for details. If you need to password-protect your site (Basic Auth), use Restricted Access on the Nginx/Apache configuration page.

4. Configure Wildcard Subdomains

1. Check Enabled Wildcard Sub-Domains to let your website answer any non-existing subdomain (e.g., anything.yourdomain.com).
2. Click Update and confirm in the dialog.

5. Change Site Owner

1. In the Update Owner section, select a Linux user from the list or type a new username (it is created automatically if it does not exist).
2. Click Update.
3. The site directory is moved to the new user's home directory and related configuration is updated automatically.

6. Change Site Type

This section only appears once the site has source code installed or a site type declared.

1. In the Update Site Type section, select the new type from the dropdown (e.g., Laravel, WordPress or Custom).
2. Click Update.

• Note: Sites installed with a 1-click app (phpMyAdmin, Chatwoot, Uptime Kuma, ImunifyAV, n8n, Roundcube) or from Git cannot change their type.

7. Change Web Directory

This feature helps you point the website to a specific sub-directory within the default website directory.

1. In the Update Web Directory section, enter the new directory path (e.g., /public for Laravel).
2. (Optional) If the site has alias domains, check Synchronization for all alias domains to apply the change to them too.
3. Click Update to apply the change.

8. Update PHP Version

1. In the Update PHP Version section, select the desired PHP version from the dropdown list.
2. Click Update to apply.
3. If the version you need is missing, install it from the server's Applications page (linked directly in this section).

• Note: After changing the PHP version, you may need to update your deploy script to use the correct PHP binary (e.g., php8.3).

9. Proxy Port

Use this for sites running an application that listens on a local port (e.g., Node.js, Python). When a proxy port is set, the web server forwards requests for the site to the application on that port.

1. In the Update Proxy Port section, enter the port your application is running on (e.g., 3000, 8080).
2. Click Update to save.

• Note: The application must keep running on that port, otherwise the site returns a 502 Bad Gateway error. You can use PM2 to keep a Node.js application running.

10. Git Configuration

These sections only appear for sites installed from Git.

Update Git Remote:

1. Open the Update Git Remote section.
2. Under Choose Source Provider, select the provider.
3. For GitHub, GitLab, or Bitbucket, select the Git account that has access to the repository.
4. For GitHub, GitLab, or Bitbucket, click Load next to the Repository field to load the repositories available to the selected account.
5. Select or enter the repository address in the Repository field.
6. Click Update to save.

Update Git Branch:

1. Open the Update Git Branch section.
2. Select or enter the branch name (click Load to load the branch list).
3. Click Update. Then go to the Deployments page and click Deploy Now to pull code from the new branch.

The selected Git account is saved for this site. Different sites can use different accounts from the same provider. For more information about connecting and managing accounts, see Git Integration.

Notes & Warnings

• Note: Wildcard subdomains require proper DNS configuration (a wildcard A or CNAME record like *.yourdomain.com) pointing to your server.
• Warning: The new Git remote must contain the same Git history as the currently installed repository. Do not use this to install an entirely different project; instead, use Remove Code on the Overview page and install the source code again.
• Warning: Make sure the selected Git account has access to the repository before updating the remote.
• Note: Changing the Git account clears the repository list. Load the repositories again before updating the remote.