Webserver configuration on konsoleH

You can use the server configuration in konsoleH to manage important settings for your website. This includes directory protection, redirects, IP blocking, custom error pages, start pages, directory indexes, access logs, and error logs.

The settings always apply to the selected directory and its subdirectories. Before you make changes, check that you selected the correct directory.

Directory protection

You can use directory protection to secure access to a specific directory with a username and password. This is useful if you want to protect internal areas, test environments, or files that should not be publicly accessible.

To set up directory protection:

1. Open the server configuration in konsoleH.
2. Select the directory that you want to protect from the directory list.
3. Click the icon for protecting the directory.
4. Click Add.
5. Enter a username.
6. Set a password or use Generate password.
7. Enter a name for the protected area.
8. Click Add.

The name of the protected area is shown during login. Use a clear name, for example the name of the protected directory.

You can change or delete existing users later.

Redirect

You can use a redirect to forward requests for a directory to another URL. This is useful if content is permanently or temporarily available at a different address.

The following redirect types are available:

To create a redirect:

1. Select the desired directory.
2. Select the appropriate redirect type.
3. Enter the complete target URL, for example https://www.example.com/.
4. Click Add.

When a visitor opens the selected directory in the browser, the request is redirected to the configured target URL.

You can edit existing redirects via Change or remove them via Delete.

IP blocker

You can use the IP blocker to block individual IP addresses, IP ranges, or hostnames for your website.

You can enter the following values:

You can change or delete blocked entries later.

Custom error pages

You can use custom error pages to define which file is displayed when a specific HTTP error occurs.

You can configure the following error pages:

For 401 Unauthorized, you can only define a file, not an external URL.

Start page

You can use the start page setting to define which files the web server looks for when a visitor opens a directory without specifying a file name.

Example:

index.html index.php index.htm

The web server checks the files in the specified order. If you leave the field empty, the server uses the default setting.

If no matching start page exists, the behavior depends on the Directory index setting. Depending on the configuration, the server either displays a 403 Forbidden error or lists the content of the directory.

Directory index

You can use the directory index setting to define whether visitors can view the content of a directory in the browser if no matching start page exists.

If the directory index is enabled, the web server may display a list of files and subdirectories. This is often not desired because visitors may see file names, directory structures, or files that are not linked anywhere on your website.

For security reasons, the directory index is disabled by default. Only enable it if you intentionally want to display a file list in the browser.

To disable or enable the directory index for a directory:

1. Open the server configuration in konsoleH.
2. Select the folder for which you want to change the setting.
3. Click Server configuration.
4. Select Directory index.
5. Enable or disable the directory index using the button.
6. Save the change.

The setting applies to the selected directory and its subdirectories, unless it is overwritten by a separate setting in a subdirectory.

Relation to the start page

The directory index becomes relevant when a visitor opens a directory without specifying a file name and no matching start page exists.

Example:

https://www.example.com/downloads/

If this directory does not contain a file such as index.html, index.php, or index.htm, the Directory index setting determines what happens.

If you want to prevent visitors from seeing the content of a folder, disable the directory index and create a suitable start page if needed.

HTTP access logs

In the HTTP access logs, you can view the latest requests to your website. You can download the displayed data via Download as file.

You can find the complete daily access logs in the www_logs directory. You can access this directory with your main FTP user.

The log files are usually available from about 01:00 on the following day. Once they reach a certain size, the log files are automatically compressed.

For data protection reasons, IP addresses are anonymized.

HTTP error logs

In the HTTP error logs, you can find web server error messages. These entries are created, for example, when a file does not exist, a link is incorrect, or a resource cannot be loaded.

A common error is:

File Does Not Exist

This error means that a requested file does not exist on the webspace.

You can download the displayed error logs via Download as file.

You can find the complete daily error logs in the www_logs directory. You can access this directory with your main FTP user.

The log files are usually available from about 01:00 on the following day. Once they reach a certain size, the log files are automatically compressed.

For data protection reasons, IP addresses are anonymized.

Why does password protection always ask for access data twice?

You can avoid this by adding / at the end of the link to the folder which contains the password protection.

Example:
www.yourdomain.com/folder/