Web Hosting

Narrated with the voice of Edi AI AI developed by ServerHost

Step-by-step guides to setting up your websites and managing your hosting from your account.

Getting started: bring your website online
  1. Point your domain to the server

    In your domain's DNS management panel, set the A records for example.com and www.example.com to SERVER_IP.

    Replace SERVER_IP with the IP address shown in the Allocated resources panel in your account.

    The SSL certificate is issued automatically once both records point to the server.

    DNS records
    example.com.        A    SERVER_IP
    www.example.com.    A    SERVER_IP
    
  2. Install WordPress with one click

    Under Code deploy, click Edit and open Marketplace. Select the website and click Install. The latest version of WordPress is downloaded from wordpress.org, and the database and wp-config.php file are created automatically.

    Once a valid SSL certificate has been issued, open your website to choose the language, website title and administrator account. See “Marketplace: WordPress” for details.

    The remaining steps are for uploading a website or another application manually.

  3. Add your access address

    Under Security, click Edit and add your IP address or a DDNS hostname. SSH access on port 22 is allowed only from authorised addresses and through ServerHost VPN.

  4. Create an SSH user

    In the same panel, under SSH keys, enter a username and your public key. See “SSH and SFTP access” for instructions.

  5. Upload your website files

    Use SFTP or rsync to upload your files to:

    /var/www/public-folder/example.com/www

    Files in this folder are publicly accessible on your website.

  6. Create the database

    If your application needs a database, under Databases, click Edit and create one. The password is shown only once. Save it somewhere secure and enter the connection details in your application's configuration.

  • Until the SSL certificate is issued, the website uses a temporary certificate and your browser may display a security warning. At this stage, limit testing to viewing the website. Complete the administrator account setup and enter passwords or other sensitive information only after a valid SSL certificate has been issued.
Web addresses: domains and subdomains

Each domain or subdomain has its own website, with a separate folder, PHP version, SSL certificate and settings.

  1. Add a subdomain

    Under Web addresses, click Edit, enter the subdomain name, such as blog, and click Add. This creates blog.example.com with its own folder. You can add up to 3 subdomains.

  2. Add another domain

    Under “Add a domain”, enter the domain name, such as another-domain.com. A separate website is created for it, accessible both with and without www.

    The number of available domains depends on your hosting plan. To increase it, under Allocated resources, click Edit and adjust the Domains value.

  3. Choose the primary address

    For each domain, choose whether the primary address uses www. The other version will redirect automatically to your chosen address.

  4. Delete a website

    Deleting a domain or subdomain also deletes its folder and all files inside it. Save a copy first if you need to keep the content.

Server folders
/var/www/public-folder/
├── example.com/
│   └── www/          ← example.com and www.example.com
└── blog.example.com/
    └── www/          ← blog.example.com
  • A domain can be associated with only one ServerHost service.
SSL certificate (HTTPS)

Each website receives a free Let's Encrypt certificate that renews automatically.

  1. Check the DNS records

    All website addresses, such as example.com and www.example.com, must point to the server's IP address before the certificate can be issued.

  2. Check the certificate status

    Under Security, click Edit and open the Sites section. For each website, you can see its certificate, expiry date or the reason a certificate has not yet been issued.

  3. Request a new certificate

    After correcting the DNS records, click Generate certificate.

  • DNS changes become visible gradually and may take a few minutes or several hours.
SSH and SFTP access

Each user connects to the server with their own SSH key. Authentication uses keys only, with no passwords.

  1. Generate an SSH key

    If you do not already have a key, generate one on your computer. To add the user, you will need the public key from the file ending in .pub.

    Keep the private key on your computer. Do not share it with anyone or upload it to a repository.

  2. Add the user

    Under Security, click Edit, then enter the username and public key in the SSH keys section.

    Usernames must be between 3 and 32 characters long and may contain lowercase letters, numbers, hyphens (-) and underscores (_). You can add up to 5 users per account. A username cannot be changed after it has been created.

  3. Allow access from your address

    Port 22 is accessible only from authorised IP addresses and through ServerHost VPN. Before connecting, add your IP address to the access list or connect to ServerHost VPN.

  4. Connect to the server

    Connect through SSH from your terminal or through SFTP using FileZilla, Cyberduck or WinSCP. Use the same username and SSH key for both connection methods.

  5. Replace a key or delete a user

    “Replace key” updates the SSH key while keeping the user account.

    If you delete a user, their account is removed from the servers within a few minutes. Website files are kept.

Generate a key (on your computer)
ssh-keygen -t ed25519 -C "laptop"
cat ~/.ssh/id_ed25519.pub
Connect over SSH
ssh anna@SERVER_IP
cd /var/www/public-folder/example.com/www
ls -la
SFTP settings (FileZilla, Cyberduck)
Protocol:  SFTP
Host:      SERVER_IP
Port:      22
User:      anna
Key file:  ~/.ssh/id_ed25519
Folder:    /var/www/public-folder/example.com/www
Synchronize a folder with rsync
rsync -avz --delete ./site/ anna@SERVER_IP:/var/www/public-folder/example.com/www/
  • The --delete option removes files from the destination folder on the server if they no longer exist in the local folder. Check the source and destination before running the command.
Databases

Create databases for your applications and manage their connection details from your account.

  1. Create a database

    Under Databases, click Edit, enter a short name, such as shop, and click Create. The database will be named db_shop and its user usr_shop.

  2. Save the password

    The password is shown only once, immediately after creation. Save it somewhere secure and enter it in your application's configuration, together with the database name and username.

  3. Generate a new password

    If you lose the password, generate a new one from the database list. Then update your application's configuration with the new password to restore its connection.

  4. Import or export data

    Connect through SSH and use mysqldump to export data or mysql to import it, as shown below.

    Keep database exports and archives outside the public www folder. They may contain personal data, passwords and other confidential information.

wp-config.php (WordPress)
define('DB_NAME', 'db_shop');
define('DB_USER', 'usr_shop');
define('DB_PASSWORD', 'the-password-shown-once');
define('DB_HOST', 'localhost');
Export and import over SSH
# Create a private backup directory
mkdir -p "$HOME/private-backups"
chmod 700 "$HOME/private-backups"

# Restrict permissions on newly created files to the account's UID.
# SSH users belonging to the same customer share this UID and can access these files.
umask 077

# Export
mysqldump -u usr_shop -p db_shop > "$HOME/private-backups/backup.sql"

# Import
mysql -u usr_shop -p db_shop < "$HOME/private-backups/backup.sql"
  • The commands prompt for the password. Do not include the password directly in the command. The private-backups directory in this example must be outside all public website folders.
  • The number of available databases depends on your hosting plan. MySQL settings adjust automatically to the server's resources.
PHP

Each website can use its own PHP version and execution limits.

  1. Open the PHP settings

    In the PHP panel, click Edit.

  2. Configure each website

    Choose the PHP version and adjust these limits if needed:

    • memory available to a script: 128 MB to 1 GB;
    • maximum size of an uploaded file: 16 MB to 256 MB;
    • maximum execution time for a request: 30 to 300 seconds.
  3. Save your changes

    The new settings take effect within a few minutes, without interrupting the other websites.

  • Increase memory and execution time only when your application needs it, for example for large imports or resource-intensive plugins. These limits apply to each PHP request.
  • The number of PHP processes and the OPcache settings adjust automatically to the server's resources and the number of websites.
  • Sending email: the PHP mail() function is disabled. Configure your application to send email through SMTP using the connection details of an email account. For WordPress, you can use a plugin such as WP Mail SMTP.
Security

Under Security, click Edit to manage protection settings for your server and websites.

  1. Check for security updates

    We check daily whether the PHP version and the applications detected on your websites (WordPress, Joomla or PrestaShop) are up to date. When an update is needed, you receive an email and the Security panel turns red.

    To run an immediate check, click Check now.

  2. Restrict access to a website

    In the Sites section, you can allow access only from your authorised addresses and through ServerHost VPN. Other visitors receive an HTTP 403 response (access denied).

    This option is useful for development or test websites.

  3. Configure Content Security Policy (CSP)

    CSP controls the sources from which the browser can load scripts, styles, images and fonts.

    Add the external domains your website uses and start in “Report only” mode. This does not block resources, but reports policy violations in the browser console. After checking the results, switch to “Enforced” mode to enable blocking.

  4. Manage access addresses

    Add the IP addresses or DDNS hostnames you connect from. These allow SSH access and access to restricted areas, such as WordPress administration. Access is also allowed through ServerHost VPN.

  5. Block traffic to and from selected countries

    Select the countries you want to block. The rule applies to traffic in both directions, on all server ports.

  6. Manage WordPress protection

    When we detect WordPress and, where applicable, WooCommerce, the available protections are enabled by default: Restrict WP Admin, WordPress hardening, Block PHP in themes, Limits per IP and WooCommerce protection.

    You can disable each protection separately using its switch.

Allowed domains for CSP (one per line)
fonts.googleapis.com
fonts.gstatic.com
*.google-analytics.com
*.googletagmanager.com
  • When “Restrict WP Admin” is enabled, WordPress administration is accessible only from authorised addresses or through ServerHost VPN.
Performance

Under Performance, click Edit to enable the optimisation options available for your websites.

  1. Optimise static files and images

    Enable the Static files cache, WebP images and Lazy load options:

    • the browser stores CSS, JavaScript, images and fonts locally;
    • JPG and PNG images are delivered as WebP when the browser supports it;
    • images load as the visitor reaches them on the page.
  2. Enable page caching for WordPress

    nginx caches pages for 60 minutes and serves them without running PHP. Requests from logged-in users, along with cart, checkout and administration pages, are excluded.

    Install the Nginx Helper plugin and select the “GET request to /purge/” purge method so the cache is cleared automatically when you change content.

  3. Run scheduled WordPress tasks from the server

    With “WP-Cron from the system” enabled, scheduled tasks run every 5 minutes, independently of visits to your website.

    Enable the option and add the line shown below to wp-config.php.

  4. Configure object caching

    The server includes Redis, available at 127.0.0.1:6379, and APCu.

    For WordPress, install the Redis Object Cache plugin and configure a unique prefix for each website, as shown below.

wp-config.php: WP-Cron from the system
define('DISABLE_WP_CRON', true);
wp-config.php: Redis (Redis Object Cache plugin)
define('WP_REDIS_HOST', '127.0.0.1');
define('WP_REDIS_PORT', 6379);
define('WP_REDIS_PREFIX', 'example.com:');
  • Redis is shared by the websites on the server. Use different prefixes to prevent accidental overlap between cached data. Prefixes organise keys, but they are not an access control mechanism and do not, by themselves, provide security isolation between applications.
Logs

View website requests and errors in real time.

  1. Choose the website and log type

    Under Logs, click View live and select the website. You can view nginx access logs, nginx errors, PHP errors or PHP requests that take longer than 5 seconds.

  2. Start viewing

    Click Start. New entries appear as they are written to the log.

    The Clear button clears the current view.

Deploy from Git

Publish changes from your repository to your website automatically using GitLab CI/CD or GitHub Actions.

  1. Configure the code source

    Under Code deploy, click Edit and choose ServerHost GitLab or another Git service. Enter the repository address.

    Access from ServerHost GitLab is allowed automatically. For another service, enter the address your CI system connects from; port 22 will be accessible from that address.

  2. Save the deployment key

    The private deployment key is available for 24 hours. Store it in your CI/CD platform's secret management system as SVH_DEPLOY_KEY.

    In GitLab, use a protected CI/CD variable and make it available only to authorised deployment jobs. In GitHub Actions, use a secret available only to the workflows that need it.

    Do not commit the key to the repository or print it in job logs.

    After 24 hours, the key can no longer be displayed. If you have not saved it, generate a new one.

  3. Choose the branch for each website

    Open the website's tab, enter the branch to deploy, such as main, and save.

  4. Add the CI/CD configuration

    Use one of the examples below and push your changes to the repository. The deployment job sends the archive to the server and runs the specified operations for the selected website.

    Before the first run, under Code deploy, click Edit and copy the known_hosts entry from “Public SSH key of the server”. Check the SHA256 fingerprint shown next to it, then store the complete entry in the CI/CD variable SVH_KNOWN_HOSTS. In GitLab, save it as a regular variable (type Variable, not File); in GitHub Actions, as a secret.

    This is the server's public key, used to verify the destination. It is different from the private SVH_DEPLOY_KEY used to authenticate the job.

The whole site (.gitlab-ci.yml)
deploy:
  stage: deploy
  image: alpine:3
  rules:
    - if: $CI_COMMIT_BRANCH == "main"
  script:
    - apk add --no-cache git openssh-client
    - umask 077
    - mkdir -p "$HOME/.ssh"
    - chmod 700 "$HOME/.ssh"
    - printf '%s\n' "$SVH_DEPLOY_KEY" > "$HOME/.ssh/ci-svh"
    - printf '%s\n' "$SVH_KNOWN_HOSTS" > "$HOME/.ssh/known_hosts"
    - chmod 600 "$HOME/.ssh/ci-svh" "$HOME/.ssh/known_hosts"
    - git archive --format=tar HEAD > site.tar
    - ssh -i "$HOME/.ssh/ci-svh" -o IdentitiesOnly=yes -o StrictHostKeyChecking=yes
        -o UserKnownHostsFile="$HOME/.ssh/known_hosts" svhdeploy@SERVER_IP example.com
        deploy "$(sha256sum site.tar | cut -d' ' -f1)" reload-php purge-cache < site.tar
Deploy only the theme, with releases and rollback (.gitlab-ci.yml)
deploy:
  stage: deploy
  image: alpine:3
  rules:
    - if: $CI_COMMIT_BRANCH == "main"
  script:
    - apk add --no-cache git openssh-client
    - umask 077
    - mkdir -p "$HOME/.ssh"
    - chmod 700 "$HOME/.ssh"
    - printf '%s\n' "$SVH_DEPLOY_KEY" > "$HOME/.ssh/ci-svh"
    - printf '%s\n' "$SVH_KNOWN_HOSTS" > "$HOME/.ssh/known_hosts"
    - chmod 600 "$HOME/.ssh/ci-svh" "$HOME/.ssh/known_hosts"
    - REL="$(date +%Y%m%d-%H%M%S)-$CI_COMMIT_SHORT_SHA"
    - git archive --format=tar HEAD:wp-content/themes/theme > release.tar
    - ssh -i "$HOME/.ssh/ci-svh" -o IdentitiesOnly=yes -o StrictHostKeyChecking=yes
        -o UserKnownHostsFile="$HOME/.ssh/known_hosts" svhdeploy@SERVER_IP example.com
        release "$REL" "$(sha256sum release.tar | cut -d' ' -f1)" activate "$REL" wp-content/themes/theme
        reload-php purge-cache prune 5 < release.tar
GitHub Actions
name: deploy
on:
  push:
    branches: [main]
jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Deploy
        env:
          SVH_DEPLOY_KEY: ${{ secrets.SVH_DEPLOY_KEY }}
          SVH_KNOWN_HOSTS: ${{ secrets.SVH_KNOWN_HOSTS }}
        run: |
          umask 077
          mkdir -p "$HOME/.ssh"
          chmod 700 "$HOME/.ssh"
          printf '%s\n' "$SVH_DEPLOY_KEY" > "$HOME/.ssh/ci-svh"
          printf '%s\n' "$SVH_KNOWN_HOSTS" > "$HOME/.ssh/known_hosts"
          chmod 600 "$HOME/.ssh/ci-svh" "$HOME/.ssh/known_hosts"
          git archive --format=tar HEAD > site.tar
          ssh -i "$HOME/.ssh/ci-svh" -o IdentitiesOnly=yes -o StrictHostKeyChecking=yes \
            -o UserKnownHostsFile="$HOME/.ssh/known_hosts" svhdeploy@SERVER_IP example.com \
            deploy "$(sha256sum site.tar | cut -d' ' -f1)" reload-php purge-cache < site.tar
  • The examples verify the server's identity using the key stored in known_hosts. If the server presents a different key, the connection stops. Investigate the change before updating the stored key: if the change is legitimate (for example, after the server is rebuilt), copy the new entry from Code deploy, check its fingerprint and update SVH_KNOWN_HOSTS.
  • Do not disable host key checking to resolve a connection error. A key collected using ssh-keyscan alone must be verified separately through a trusted channel.
  • Deploying the whole website: the deploy <sha256> command verifies the archive's integrity before publishing it. Files removed from the repository are deleted from the server, while user uploads are kept.
  • Deploying separate releases: the release and activate commands create and activate a new version of the code. The previous version remains available for rollback. The prune 5 command keeps the latest 5 releases.
  • After deployment, you can use reload-php, reload-nginx and purge-cache. nginx is reloaded only if its configuration is valid.
Marketplace: WordPress

Install the latest version of WordPress from your account, with the database and initial configuration created automatically.

Under Code deploy, click Edit and open Marketplace.

  1. Choose the website and click Install

    Installation is available only when the website's www folder is empty. If it contains any files, including hidden files, installation stops and a message is displayed. Existing files are not changed or deleted.

  2. Follow the progress

    The installation steps appear below the panel: checking the folder, identifying the version, downloading WordPress, verifying the checksum published by wordpress.org and extracting the files.

  3. Save the database details

    The database and its user are created automatically, with names derived from the website address. For example, blog.example.com creates db_blog-example and usr_blog-example.

    The password is generated automatically and shown only once. Save it somewhere secure.

  4. Complete the WordPress setup

    The wp-config.php file is created automatically. It includes the database connection details, a server-specific table prefix, unique security keys and settings that disable the file editor in WordPress administration.

    If “WP-Cron from the system” is enabled under Performance, the corresponding configuration is also added.

    Once a valid SSL certificate has been issued, open your website and follow the WordPress setup steps to choose the language, website title and administrator account. If your browser displays a certificate warning, check the certificate status before entering account details.

    If you later deploy through CI/CD, manage the application's connection credentials through your platform's secret management system. Do not store passwords or private keys in the repository.

wp-config.php
define('DB_NAME', 'db_shop');
define('DB_USER', 'usr_shop');
define('DB_PASSWORD', 'the-password-shown-once');
define('DB_HOST', 'localhost');
  • You can generate a new password under Databases using the New password option. After changing it, update the WordPress configuration as well.
  • Set up email delivery: the PHP mail() function is disabled. For password resets, notifications and forms, install an SMTP plugin such as WP Mail SMTP and configure it with the connection details of an email account.
Example: migrating an existing website

Move the files and database, test the website on the new server, then update the DNS records.

  1. Prepare access and the database

    Add your access address, create an SSH user and create a database. Save the password shown when the database is created.

  2. Transfer the files and database

    On the old server, export the database and archive the website files in a private directory outside the public website folder. Transfer the archive and database export to a private directory on the new server.

    Extract the website files into the www folder and import the database. Do not place the SQL export or archive in the public website folder.

  3. Update the application configuration

    For WordPress, update the database name, username and password in wp-config.php. Use localhost as the database host.

  4. Test the website and update DNS

    To test before changing DNS, temporarily edit the hosts file on your computer so the domain points to the new server.

    At this stage, the website uses a temporary certificate and your browser may display a security warning. Limit testing to public pages, without signing in or entering passwords, payment details or other sensitive information.

    After testing, update the A records for the domain and www to SERVER_IP, then remove the temporary entries from your hosts file. The SSL certificate is issued automatically once the DNS records point to the new server.

    Once a valid certificate has been issued, test sign-in and any features that use sensitive information.

Commands
# On the old server: prepare a private directory
mkdir -p "$HOME/private-backups"
chmod 700 "$HOME/private-backups"
umask 077

# Export the database and archive the files
mysqldump -u USER -p DATABASE > "$HOME/private-backups/backup.sql"
tar czf "$HOME/private-backups/site.tgz" -C /path/to/site .

# Download these two files to your computer using SFTP.
# Do not move them into the public website folder.

# From your computer: prepare the private destination
ssh anna@SERVER_IP 'mkdir -p "$HOME/private-backups" && chmod 700 "$HOME/private-backups"'

# Run from the local directory containing the downloaded files
scp site.tgz backup.sql anna@SERVER_IP:~/private-backups/

# Connect to the new server
ssh anna@SERVER_IP

# Restrict access to the transferred files
chmod 600 "$HOME/private-backups/site.tgz" "$HOME/private-backups/backup.sql"

# Extract the website files and import the database
tar xzf "$HOME/private-backups/site.tgz" -C /var/www/public-folder/example.com/www
mysql -u usr_shop -p db_shop < "$HOME/private-backups/backup.sql"
wp-config.php
define('DB_NAME', 'db_shop');
define('DB_USER', 'usr_shop');
define('DB_PASSWORD', 'the-password-shown-once');
define('DB_HOST', 'localhost');
  • Keep the old server running while DNS changes propagate. If the website receives orders, new accounts or other data, also plan how to transfer changes made after the initial database export.
Resources and changes

The Allocated resources panel shows the server's vCPU count, RAM, storage and IP address.

  1. Choose the resources you need

    Click Edit, adjust the vCPU, RAM, storage or domain values, and confirm.

    For resource upgrades, a pro forma invoice is issued with the cost calculated proportionally for the remainder of the billing period.

  2. Choose when to apply the change

    After payment, you can apply the change immediately or overnight.

    Some changes require a server restart and a few minutes of downtime. Your account shows whether a restart is required before you apply the change.

    Additional domains become available immediately, without a server restart.

  3. Reduce resources

    Resource reductions take effect at the start of the next billing period.

  • Options that change the server's configuration are available only while the server is running.