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
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
read access to nginx vhosts in
read access to the global modsecurity configuration in
puppet-agentto trigger a manual configuration management run
rebootto trigger a manual server reboot
diskusageto search for big files and folders
nft-listto list the current nftables configuration
nft-checkto validate the current nftables configuration
update-ca-certificates, see CA Certificates for details
modsecurity-logparserto identify blocking Web Application Firewall rules more easily
monit-statusshows the monit status of all services
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)