Solutions:
1. You move beyond the panel and build a full independant conf file that you include in /etc/sentora/config/apache/httpd.conf main config, so your custom setup is kept always.
2. You can use the panel too in a less common way. You add the new vhost setting to a current vhost and you start with closing the current vhost and then adding a new vhost. It's an ugly solution but works. I advice you to use the first far better.
M B
1. You move beyond the panel and build a full independant conf file that you include in /etc/sentora/config/apache/httpd.conf main config, so your custom setup is kept always.
2. You can use the panel too in a less common way. You add the new vhost setting to a current vhost and you start with closing the current vhost and then adding a new vhost. It's an ugly solution but works. I advice you to use the first far better.
M B
No support using PM (Auto adding to IGNORE list!), use the forum.
How to ask
Freelance AWS Certified Architect & SysOps// DevOps
10$ free to start your VPS
How to ask
Freelance AWS Certified Architect & SysOps// DevOps
10$ free to start your VPS