Docs

Software and Advanced

PHP versions and extensions, PHP settings, Website Compression, Node.js, Python and Ruby applications, scheduled tasks, custom error pages, folder listings, file types, Apache handlers and domain aliases.

9 min read Updated From the panel's guide

These tools control how your websites run: which PHP version and settings they use, compression, applications in other languages, commands that run on a schedule, and how the web server answers for errors, folders and file types.

In the modern look most of them are under Websites & Apps (tabs PHP version, Website Compression, Scheduled tasks, Applications and Website settings). In the classic look they are in the Software and Advanced groups on the Tools page.

PHP Versions#

Each website can run its own PHP version. Open PHP Versions (the PHP version tab under Websites & Apps).

The Websites and PHP version list shows each website with a menu of the PHP versions installed on the server.

  1. Pick the version for the website.
  2. Choose Change.

The change takes effect at once. Check your website afterwards.

Good to know:

  • Versions before 8.2 are no longer supported by the PHP project. Use them only for sites that cannot run on a newer version.
  • Before moving to a newer version, check that your software (and its plugins and themes) supports it. If the site breaks, switch back.
  • PHP settings you made for a website (see below) stay when you change its version.
  • Which versions are offered is decided by your hosting provider. Ask your hosting provider if you need another one.
  • The PHP column on Domains links here too.

PHP extensions#

Some software needs extra PHP extensions, such as intl, imagick or soap. Open PHP Versions and find PHP extensions (shown when your hosting provider offers optional extensions).

For each website, with its PHP version shown:

  1. Tick the extra extensions the website needs.
  2. Choose Save.

Always loaded lists the extensions every website of that version gets anyway.

Good to know:

  • The list depends on the website's PHP version. If you change the version, check the extensions again.
  • "There are no optional extensions for this PHP version" means nothing extra can be chosen for it.
  • Your hosting provider decides which extensions can be chosen. Ask your hosting provider if one you need is missing.

PHP Settings per Version#

You can change PHP's limits and options for each website. Open PHP Settings per Version (the PHP settings box on Website settings) and pick the website at the top.

Leave a field empty to use the server's standard value. The settings are:

  • Memory limit (memory_limit): 16M to 2048M.
  • Largest upload (upload_max_filesize): 1M to 2048M.
  • Largest form submission (post_max_size): 1M to 2048M. Keep it at least as large as the largest upload.
  • Longest run time (seconds) (max_execution_time): 1 to 3600.
  • Longest input time (seconds) (max_input_time): 1 to 3600.
  • Most form fields (max_input_vars): 100 to 100000.
  • Show errors to visitors (display_errors): On or Off. Keep it Off on a live website.
  • Short open tag (short_open_tag): On or Off.
  • Open remote addresses as files (allow_url_fopen): On or Off.
  • Time zone (date.timezone): such as Europe/London.

Choose Save PHP settings. They apply to that website, whichever PHP version it uses.

Good to know:

  • A common fix for "upload too large" in WordPress is to raise both Largest upload and Largest form submission.
  • Values outside the allowed range are refused.

Website Compression#

Compression shrinks pages, style sheets and scripts before they are sent, so they reach visitors sooner and use less data transfer. Open Website Compression (the Website Compression tab under Websites & Apps). It applies to the websites of your account.

Choose one:

  • Off.
  • Compress everything: images, video, music, fonts and archives are left as they are, because they are compressed already.
  • Compress only these MIME types: list the types under MIME types to compress, separated by spaces, for example text/html text/css application/javascript.

Choose Save.

Good to know:

  • This changes only the web server's own compression (Apache's mod_deflate). Compression of PHP output itself (zlib) is a PHP setting.
  • Each website also has a Send pages, style sheets and scripts compressed option in its Folder listings, compression, file types and handlers box on Website settings.
  • "Compress everything" is the simplest good choice for most websites.

Web Applications#

You can run Node.js, Python and Ruby applications on your websites. Open Web Applications (the Applications tab under Websites & Apps). Each application runs as your account, keeps running after a server restart, and is reached through the address you choose.

To create an application:

  1. Enter a Name (lowercase letters, digits and "-").
  2. Choose the Language and version installed on the server.
  3. Choose the Website and the Address on that website: / makes the whole website the application; /shop only that part, and the rest stays an ordinary website.
  4. Enter the Application folder, such as apps/shop. Keep it outside public_html, so its source files cannot be downloaded.
  5. Enter the Startup file, such as app.js, wsgi.py or config.ru. If it does not exist yet, a small "It works!" example is put there.
  6. Choose Create.

An account can have up to 50 applications. If no language is installed, ask your hosting provider to install Node.js, Python or Ruby.

Web Applications: running and settings#

To manage an application, open Web Applications and choose Manage. The page shows its status (Running, Stopped, Failed or Starting again and again), its address and folder.

  • Start, Restart, Stop. Restart the application after changing its files.
  • Run npm install (Node.js) installs what package.json lists. Run pip install (Python) creates a virtual environment (.venv) in the folder and installs what requirements.txt lists. Run bundle install (Ruby) installs what the Gemfile lists into vendor/bundle. This can take a few minutes; the output is shown when it has finished.
  • Settings: change the language and version, website, address, folder and startup file, and add Environment variables, one NAME=value per line. Save (and restart when running).
  • Log: what the application printed, and its starts and stops; the last 100 lines are kept, and new lines appear by themselves.
  • Remove this application: stops it and makes it unreachable. Its files stay.

Good to know:

  • The application must listen on 127.0.0.1 on the port given in the PORT variable.
  • For Python, the startup file only needs a WSGI callable named application or app (Flask and Django have one); it is served with gunicorn if requirements.txt lists it.
  • With an address other than /, requests reach the application with the full address, and the same path is in BASE_PATH.
  • "Starting again and again" means the application stops right after starting; look in the Log for the error.

Scheduled Tasks#

A scheduled task (cron job) runs a command at set times, as your account. Open Scheduled Tasks (the Scheduled tasks tab under Websites & Apps).

To add a task:

  1. Under How often, pick a preset (every 5 or 15 minutes, twice an hour, once an hour, twice a day, once a day at midnight, once a week on Sunday, once a month on the 1st), or Use the times below and fill in Minute, Hour, Day of month, Month and Weekday.
  2. Enter the Command, for example php /home/youraccount/public_html/cron.php.
  3. Choose Add task.

In the time fields, * means every; */10 every tenth; 1-5 a range; 1,15 a list. Weekday 0 (and 7) is Sunday. Times follow the server's clock.

The list shows each task; Remove deletes it.

Where output goes: whatever a task prints is mailed to the address you save here. Leave it empty to send nothing, or add >/dev/null 2>&1 to a command to discard its output.

Good to know:

  • Use full paths in commands.
  • Tasks stop while an account is suspended.

Custom Error Pages#

You can show your own page instead of the web server's standard one when something goes wrong, for example when a page is not found. Open Custom Error Pages (the Custom error pages box on Website settings) and pick the website at the top.

The box lists the codes 400, 401, 403, 404, 500 and 503, each marked Own page or Standard.

  1. Open a code, such as 404.
  2. Write or paste the page's HTML, for example <h1>Page not found</h1><p><a href="/">Back to the home page</a></p>.
  3. Choose Save 404 page (or the code you opened).

Use the standard page again removes your page.

Good to know:

  • A page can be up to 64 KB. Use full addresses (starting with / or https://) for images, style sheets and links in it.
  • 404 is for "not found", 403 for "forbidden", 401 for a wrong password on a protected folder, 500 for a server error, 503 for "unavailable".
  • Software with its own error handling, such as WordPress, shows its own "not found" page for its addresses.

Folder Listings#

When a visitor opens a folder of your website that has no index page (such as index.html or index.php), the web server either refuses or shows a list of the files in it. Open Folder Listings (the Folder listings, compression, file types and handlers box on Website settings) and pick the website at the top.

Under A folder without an index page shows, choose:

  • The server's usual answer,
  • Nothing (access refused): visitors get "Forbidden". The safest choice.
  • A plain list of its files,
  • A list with sizes and dates.

Choose Save. The setting applies to the whole website.

Good to know:

  • Listing files can show visitors things you did not mean to publish, such as backups or configuration files. Turn listings on only for folders meant for downloads.
  • Right-clicking a folder in the File Manager offers Folder Listings, which opens this box for that folder's website.

File Types (MIME)#

The file type (MIME type) tells browsers what a file is, so they know whether to show it, play it or download it. Most endings are known already. To add or change one, open File Types (MIME) (the Folder listings, compression, file types and handlers box on Website settings) and pick the website at the top.

Under Extra file types, write one per line: the type, then the file endings. For example:

text/calendar ics
font/woff2 woff2

Choose Save.

Good to know:

  • Endings cannot be made to run as PHP here.
  • If a file downloads instead of showing (or the other way round), a missing or wrong type is the usual cause.

File Handlers (Apache)#

A handler tells the web server how to process files with certain endings. Open File Handlers (Apache) (the Folder listings, compression, file types and handlers box on Website settings) and pick the website at the top.

Under Handlers, write one per line: the handler, then the file endings, for example server-parsed shtml. The handlers you can use are:

  • server-parsed: pages that include other files (server-side includes),
  • send-as-is: files that contain their own HTTP headers,
  • default-handler: serve the file as it is,
  • type-map: files that choose between versions of a page.

Choose Save.

Good to know:

  • PHP is set up by the panel for every website; endings cannot be made to run as PHP with a handler.
  • Most websites need no handlers at all.

Domain Aliases#

A domain alias (parked domain) is another domain that shows the same website. Open Domain Aliases (the Aliases box on Website settings), pick the website at the top, enter the other domain and choose Add alias. Remove takes one away.

The alias gets a DNS zone here, and its DNS must point at this server. Choose Issue again on SSL/TLS afterwards so the website's certificate covers the alias too.

See Domains and Websites for more on aliases, and on when to use a redirect or a separate domain instead.

Was this article helpful?

Something missing? Ask in the community or open a ticket.