We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Implement Apache v2.4 Access Control in apache2.conf / httpd.conf NOT .htaccess
Implement Apache v2.4 Access Control in apache2.conf / httpd.conf NOT .htaccess
On our site https://subdomain.example.com we want to only allow access via certain IP.
We edited :
/home/admin/conf/web/subdomain.example.com.apache2.ssl.conf
adding the following into the directory container for the site :
/home/admin/web/subdomain.example.com/public_html/
<RequireAll>
Require ip xxx.xxx.xxx.xxx
</RequireAll>
This approach and variations on it does not work.
...
By itself in the .htaccess, Require ip directive does work.
I ran :
apache2ctl -V | grep SERVER_CONFIG_FILE
and of course it returns /etc/apache2/apache2.conf
So, I suspect I will need to add a virtual host to the apache2.conf, but then why not do this in the domain specific VirtualHost confs?
apache2.conf also includes the conf.d dir and its config files - including vesta conf which loads the domain specific confs.
Can someone shed light on how to achieve domain specific access control in Apache 2.4 ?
Any clarifications and help would be appreciated.
...
I have read the docs here :
https://httpd.apache.org/docs/2.4/mod/m ... _host.html
https://httpd.apache.org/docs/2.4/howto/access.html
We edited :
/home/admin/conf/web/subdomain.example.com.apache2.ssl.conf
adding the following into the directory container for the site :
/home/admin/web/subdomain.example.com/public_html/
<RequireAll>
Require ip xxx.xxx.xxx.xxx
</RequireAll>
This approach and variations on it does not work.
...
By itself in the .htaccess, Require ip directive does work.
I ran :
apache2ctl -V | grep SERVER_CONFIG_FILE
and of course it returns /etc/apache2/apache2.conf
So, I suspect I will need to add a virtual host to the apache2.conf, but then why not do this in the domain specific VirtualHost confs?
apache2.conf also includes the conf.d dir and its config files - including vesta conf which loads the domain specific confs.
Can someone shed light on how to achieve domain specific access control in Apache 2.4 ?
Any clarifications and help would be appreciated.
...
I have read the docs here :
https://httpd.apache.org/docs/2.4/mod/m ... _host.html
https://httpd.apache.org/docs/2.4/howto/access.html