Frequently asked questions

TurboStack is Hosted Power's self-service platform for managing hosting. You describe how each server should be configured and TurboStack provisions it for you. See Introduction.

Open your host, add an application, connect your domain and publish. The full walk-through is in Deploy your first site.

Save stores your configuration; Publish deploys it to the server. Nothing is kept until you Save - if you change a setting and navigate away, the change is gone. Rows you add to a table are the exception: those are stored immediately. See Publishing changes and the Source (YAML) view.

Yes. The GUI and the Source (YAML) view describe the same configuration - switch freely.

Use groups and templates to apply shared configuration across a fleet of hosts.

Open the host's History and revert to an earlier revision. See History.

Clone an account (files and database) to another system user from the host's History. See History.

Use Migration Hero to pull a site from an external host. See Migration Hero.

Connect a repository on the application's GIT tab. See Git deployment.

On the host's Credentials tab. See Credentials.

No. TurboStack runs a standard open-source stack, so you can run almost any web application on it - there is no lock-in. Use Generic (app_type left empty) for a plain PHP site, or the reverse-proxy pattern for any Node.js, Python or containerized app. See Deploying applications.

WordPress, Magento, Shopware, Drupal, Laravel, Akeneo, OroCommerce, Craft CMS, Nextcloud, Odoo, Medusa and nopCommerce - see the catalog in Deploying applications. Any other app runs on the same stack.

Each has a deploy guide with example YAML: WordPress, Magento, Shopware.

Under your system user's home directory (~/public_html), managed over Secure Shell (SSH). See File layout and permissions.

Run them as user system services so they restart on failure and survive logout. See How to manage user system services.

For your own background workers: never more than the host has processor cores, and keep a margin - too many slow the whole server. PHP-FPM workers are a separate limit with its own ceiling, see Configure PHP. See Scale throughput with more instances.

The full open-source stack: Nginx and Apache; PHP, Node.js, Python, Ruby and .NET; MySQL, PostgreSQL, MongoDB and SQL Server; Redis, Varnish, Elasticsearch/OpenSearch and RabbitMQ; Docker and Kubernetes. See Technologies overview.

Yes. They run as their own process behind Nginx through the reverse proxy (proxy_enabled + proxy_upstream_port). See Node.js.

MySQL/MariaDB, PostgreSQL, MongoDB and Microsoft SQL Server. Enable the one your app needs on the Services tab.

Redis (object and session cache) is recommended for most apps and on by default; Varnish is full-page caching for PHP storefronts.

Yes. See Docker (plus run a container and Docker Compose) and Kubernetes.

Enable Elasticsearch or OpenSearch. Magento and Akeneo require it; other apps use it for large catalogs.

Set php_version per application and publish. See Switch the PHP version.

Override them per site with a .user.ini file. See Override PHP settings.

Over SSH with tscli opcache clear. See Flush OPcache.

On the Applications tab (Extra database users) or with SQL. See Manage database users.

Yes, for managing MySQL databases. See phpMyAdmin.

Use mysqldump and mysql over SSH. See Import and export a MySQL database.

Over an SSH tunnel. See Connect to MySQL remotely.

At https://<your-host>/kibana or https://<your-host>/dashboards. The web server asks for a user name and password first and accepts your system user accounts - the same credentials you use for SSH. See Services, Configure Elasticsearch and Configure OpenSearch.

It is uninstalled on the next deployment, so treat the list as the complete set you want rather than a list of additions. Changing the engine version reinstalls every plugin. See Configure Elasticsearch and Configure OpenSearch.

vector, postgis, timescaledb and pg_stat_statements. Any other name stops the deployment with an error. See Configure PostgreSQL.

Only with redis_listen_addresses: internal, which also binds the host's private addresses. Redis has no password by default and this turns off its protected mode, so use it only on a trusted private network. See Configure Redis and Services.

Yes, per host and without root access, on the server's operating system (OS). See Installing extra OS packages.

Use the caching layers (Redis, Varnish, OPcache) and measure before tuning. See Performance tuning and Why is my site slow?.

Over SSH with the TurboStack command-line interface (CLI): tscli varnish clear, tscli redis clear, tscli opcache clear. See Clear the Redis cache.

Usually PHP-FPM is down or overloaded, or a request timed out. See 502, 503 and 504 errors.

The upload size limit is too low; raise it. See 403, 413 and 429 errors.

Usually the number of PHP workers multiplied by the memory each request uses. php_fpm_pm_max_children is the ceiling on concurrent workers, so it decides the worst case. See Out of memory, Configure PHP and Performance tuning.

The current edition is uninstalled before the other one is installed, so the cache starts empty and responses are slower until it fills again. Plan it outside peak hours. See Configure Varnish.

Find what is using it and clean it safely. See Disk full.

Set cert_type: letsencrypt and publish - TurboStack issues and renews the Transport Layer Security (TLS) certificate automatically. See TLS certificates.

Yes, with the Domain Name System (DNS) challenge. See TLS certificates.

Almost always the DNS is not yet pointing at the host. See TLS certificate problems.

In the Customer Center: DNS management and Domains.

Authenticate the domain with the three records - Sender Policy Framework (SPF), DomainKeys Identified Mail (DKIM) and Domain-based Message Authentication (DMARC) - and confirm the mail service is on. See Mail deliverability.

Add your public key on the host's SSH tab. Then connect with your own SSH client as your system user - the tab manages the keys, you do not connect from it. See SSH access and Add an SSH key.

Add an FTP user on the host's Advanced tab; it also works over Secure File Transfer Protocol (SFTP). See FTP and SFTP access.

Raise the TurboShield level; it rate-limits abusive traffic. See also High CPU and load.

On the Security tab or with tscli firewall. See Whitelist an IP address and Block an IP address.

Yes, by widening the database's bind address. Give a specific private address and restrict access with the firewall. The keyword ANY listens on every interface the server has, including any public one, and a database reachable from the internet is a serious risk. See Services, Configure MySQL and Whitelist an IP address.

On a host that also runs Kubernetes or Docker the platform opens the database itself, because the containers have to reach it. MongoDB does this even when its bind address is set to 127.0.0.1. Set the address explicitly on such a host and check that the firewall is closed. See Services and Configure MongoDB.

On the host's Security tab, in the TurboShield section under Advanced Settings: Allowed Bots for crawlers that must never be limited, Extra limited bots for those costing you capacity. See Configure TurboShield and What is TurboShield?.

Twenty days, on every TurboStack environment, whichever service level you are on. Need a longer retention or extra snapshots? Ask Support. See Backups and Backups and recovery.

Both are published on the Hosted Power website and linked from the Support page - the published documents are the binding versions. See Support.

Yes - Distributed Denial-of-Service (DDoS) protection with rate limiting and abuse mitigation. See DDoS and abuse protection.

Hardening, automatic updates, TurboShield and TurboRadar. See How we protect your platform.

See Reporting a security issue.

Yes - daily backups of files and databases, kept for 20 days, with restore to a folder or database of your choice. See Backups and Backups and recovery.

Set a monitoring_url per application for continuous checks and email alerts. See Monitoring.

Use the Application Programming Interface (API) for platform configuration, or the TurboStack CLI for server-side actions over SSH. See API reference.

Invite contacts or a team in the Customer Center. See Teams.

From the Customer Center. See TurboStack servers, or contact sales.

Enable it under your account settings. See Two-factor authentication.

From the Customer Center ticket dashboard. See Creating a ticket.