Server management¶
How to setup a DNS Cluster¶
If you are looking for the options to minimize DNS-related downtime or the way to manage dns across all server you have, you might consider to set up dns cluster.
- Create user dns-cluster on a server which will be used as dns slave
- Run following command on a master
v-add-remote-dns-host slave.yourhost.com 8083 admin p4sw0rd
Password and host name should be replaced with relevant data of course.
This way you can set up master->slave or master-master-master cluster. There is no limitation on how to chain dns servers.
How to setup a (S)FTP Backup server¶
Login on a server as root and run following command
v-add-backup-ftp-host remote.ftp-host.ltd backup-user p4ssw0rd [/path-backups/] [port]
For SFTP
v-add-backup-sftp-host remote.ftp-host.ltd backup-user p4ssw0rd [/path-backups/] [port]
Arguments between brackets [] may be omitted
How to setup a remote database server¶
- It is assumed you already have your second server up and running
- On your Hestia Server run the following command
v-add-database-host mysql new-server.com root password
Mysql maybe replaced by the PostgreSQL
- To make sure database has been added run following command
v-list-database-hosts
How do Web templates work?¶
Warning
Modifying templates could cause errors on the server and services that are not able to reload or start.
Every time you will rebuild the user or domain the config files of the domain will be over written by the new templates. This is done by default during update of HestiaCP or it can be initiated by the admin or by modifying settings by the user.
The templates can be found in the /data/templates/ directory in the install folder
| Service | Location |
|---|---|
| Nginx | /usr/local/hestia/data/templates/web/nginx/ |
| Nginx - PHP FPM | /usr/local/hestia/data/templates/web/nginx/php-fpm/ |
| Apache2 | /usr/local/hestia/data/templates/web/apache2/ |
| Apache2 - PHP FPM | /usr/local/hestia/data/templates/web/apache2/php-fpm/ |
| PHP-FPM | /usr/local/hestia/data/templates/web/php-fpm/ |
When editing it is the best practice to copy the template before editing. As the default templates will reset after update of HestiaCP
cp original.tpl new.tpl
cp original.stpl new.stpl
cp original.sh new.sh
Note
Modifying any default templates can cause issues in the future as there are commonly overwritten during updates.
When you are done modifying enable the template with the selected domain from the control panel.
After modifying existing template you need to rebuild user configuration. This can be done using v-rebuild-user command or bulk operation in the web interface (drop down list on a "User" page).
Available variables¶
| Name | Example | Description |
|---|---|---|
| %ip% | 123.123.123.123 | IP Address of Server |
| %proxy_port% | 80 | Port of Proxy |
| %proxy_port_ssl% | 443 | Port of Proxy (SSL) |
| %web_port% | 80 or 8080 | Port of Webserver |
| %web_port_ssl% | 443 or 8443 | Port of Webserver (SSL) |
| %web_port_ssl% | 443 or 8443 | Port of Webserver (SSL) |
| %domain% | domain.tld | Domain |
| %domain_idn% | domain.tld | Domain (Internationalised) |
| %alias_idn% | alias.domain.tld | Alias Domain (Internationalised) |
| %docroot% | /home/username/web/public_html/ | Document root of domain |
| %sdocroot% | /home/username/web/public_shtml/ | Private root of domain |
| %ssl_pem% | /usr/local/hestia/data/user/username/ssl | Location of SSL Certificate |
| %ssl_key% | /usr/local/hestia/data/user/username/ssl | Location of SSL Key |
| %web_system% | Nginx / Apache | Software used as Webserver |
| %home% | /home | Default home directory |
| %user% | username | Username of user |
| %user% | username | Username of user |
| %backend_lsnr% | proxy:fcgi://127.0.0.1:9000 | Your default FPM Server |
| %proxy_extentions% | List of extensions | All extension that should be handled by the proxy server |
%sdocroot% can also be set to %docroot% with settings
How do DNS templates work?¶
DNS templates can be found in
| Service | Location |
|---|---|
| DNS | /usr/local/hestia/data/templates/dns/ |
Variables that can be used are
| Name | Example | Description |
|---|---|---|
| %ns1% | ns1.nameserver.tld | Name server 1 |
| %ns2% | ns2.nameserver.tld | Name server 2 |
| %ip% | 123.123.123.123 | Ip address of the server or Dedicated ip |
| %domain% | domain.tld | Domain of the user |
| %time% | 12:00:00 | Time of creation |
| %date% | 01-01-2020 | Time of creation |
Templates can support up to 8 name servers with with %nsx% x could be up to maximum of 8
Where can I find more information about the config files¶
A good starting point for every software check the creator
- For Nginx NGINX Docs
- For Apache2 Apache Docs
- For PHP FPM PHP Docs
You could also try our Forum
How to install additional PHP packages / Modules¶
apt-get install php-package-name
For example
apt-get install php-memcached php-redis
Will install php-memcached and php-redis including the required additional packages for PHP.
Incase you use PHP-FPM you don't have to do anything.
IPTables How can I allow/deny an IP to all ports¶
By default after each restart Hestia will clear the current iptables
To allow an IP to all ports (Or block)
Use the following command
v-add-firewall-rule ACTION IP PORT [PROTOCOL] [COMMENT] [RULE]
v-add-firewall-rule 'accept' '123.123.123.123' '0' # Port 0 matches all ports
Also via interface it is possible just enter 0 as port number
Can I use HestiaCP behind Cloudflare CDN?¶
By default Cloudflare supports only a limited number of ports
To change the port you can run the command
v-change-sys-port 2083
Or you can disable the proxy of Cloudflare
Why I can't use http://my.ip.adress/phpmyadmin/¶
For security reason we have decided to disable this option
Please use http://mydomain.com/phpmyadmin/
How can I enable / Disable the filemanager¶
By an new install the filemanager will be enabled by default
For updates please run the following command
v-add-sys-filemanager
To disable the file manager please run
v-delete-sys-filemanager