You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I went through the guide and choose the global block method, so it works on all virtualhosts including future ones.
When I came to the blocking part it didn't work. I have put the <Location "/"> parameters at the bottom of the apache2.conf file.
I started reading through the globalblacklist.conf file and there was a part were I saw;
NOW WE ACTIVATE THE BLOCKER USING OUR ACCESS CONTROLS WITH NEW APACHE 2.4 SYNTAX
Remember to de-activate the module access_compat by running sudo a2dismod access_compat
This is where we actually make the blocker work, everything before and above this
section is merely where we are declaring our environment variables.
So I figured aha! I haven't disabled access_compat yet, but when I did, Apache didn"t want to start anymore.
Error Messages
root@panel:/etc/apache2/custom.d# journalctl -xe
Oct 23 21:19:04 vm.domain.ltd su[487880]: (to somedomainonmyvps) root on none
Oct 23 21:19:05 vm.domain.ltd su[487890]: (to somedomainonmyvps) root on none
Oct 23 21:19:05 vm.domain.ltd su[487900]: (to somedomainonmyvps) root on none
Oct 23 21:19:52 vm.domain.ltd sshd[488078]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=some IP user=root
Oct 23 21:19:53 vm.domain.ltd systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
Server (please complete the following information):
Ubuntu 20.04
Hi,
I went through the guide and choose the global block method, so it works on all virtualhosts including future ones.
When I came to the blocking part it didn't work. I have put the <Location "/"> parameters at the bottom of the apache2.conf file.
I started reading through the globalblacklist.conf file and there was a part were I saw;
NOW WE ACTIVATE THE BLOCKER USING OUR ACCESS CONTROLS WITH NEW APACHE 2.4 SYNTAX
Remember to de-activate the module access_compat by running sudo a2dismod access_compat
This is where we actually make the blocker work, everything before and above this
section is merely where we are declaring our environment variables.
So I figured aha! I haven't disabled access_compat yet, but when I did, Apache didn"t want to start anymore.
Error Messages
root@panel:/etc/apache2/custom.d# journalctl -xe
Oct 23 21:19:04 vm.domain.ltd su[487880]: (to somedomainonmyvps) root on none
Oct 23 21:19:05 vm.domain.ltd su[487890]: (to somedomainonmyvps) root on none
Oct 23 21:19:05 vm.domain.ltd su[487900]: (to somedomainonmyvps) root on none
Oct 23 21:19:52 vm.domain.ltd sshd[488078]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=some IP user=root
Oct 23 21:19:53 vm.domain.ltd systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
Server (please complete the following information):
Ubuntu 20.04
Server version: Apache/2.4.41 (Ubuntu)
Server built: 2022-06-14T13:30:55
Server's Module Magic Number: 20120211:88
Server loaded: APR 1.6.5, APR-UTIL 1.6.1
Compiled using: APR 1.6.5, APR-UTIL 1.6.1
Architecture: 64-bit
Server MPM: prefork
threaded: no
forked: yes (variable process count)
Server compiled with....
-D APR_HAS_SENDFILE
-D APR_HAS_MMAP
-D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
-D APR_USE_SYSVSEM_SERIALIZE
-D APR_USE_PTHREAD_SERIALIZE
-D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
-D APR_HAS_OTHER_CHILD
-D AP_HAVE_RELIABLE_PIPED_LOGS
-D DYNAMIC_MODULE_LIMIT=256
-D HTTPD_ROOT="/etc/apache2"
-D SUEXEC_BIN="/usr/lib/apache2/suexec"
-D DEFAULT_PIDLOG="/var/run/apache2.pid"
-D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
-D DEFAULT_ERRORLOG="logs/error_log"
-D AP_TYPES_CONFIG_FILE="mime.types"
-D SERVER_CONFIG_FILE="apache2.conf"
The text was updated successfully, but these errors were encountered: