Means to Access Your Server


Your server is accessible trough SSH by default. To ensure uniformity between SSH and web actions, there are no personal SSH login users created. Log in with the desired websites user name instead.


For security reasons, we allow key based logins only.

Every aspect of the configuration is controlled through our configuration management software. There is no root access possible neither for the customer or ourself.

Shortcuts and sudo configuration

Depending on the installed services, some shortcuts are available to execute certain commands with root privileges. You will find a list of all shortcuts by typing help.

Generic Admin User

A user named devop is created by default. You can log into the server with this user for debugging purposes and to execute global tasks which are not allowed to the website users:

  • read access to all system log files in /var/log/

  • read access to Apache vhosts in /etc/apache2/vhost/

  • read access to the global modsecurity configuration in /etc/modsecurity/

  • puppet-agent to trigger a manual configuration management run

  • reboot to trigger a manual server reboot

  • diskusage to search for big files and folders

  • nft-list to list the current nftables configuration

  • nft-check to validate the current nftables configuration

  • service-summary shows the Monit status of all services

  • letsencrypt-show view Let’s Encrypt certificates and key


To display log files, use the Log File Navigator and GoAccess utilities.


After adding your publickey to the server, is it possible to connect over SFTP. We recommend to use one of the following clients:


To store your key in the memory and not having to enter the password for every connection - use pageant (Windows) or ssh-add it (Linux)