BTK Apprendre et faire apprendre

## Mod_rewrite in use. RewriteEngine On # Blocage com_ajax via Apache <Files> (plus sûr) <Files "index.php">     <If "%{QUERY_STRING} =~ /(^|&)option=com_ajax(&|$)/">         Require all denied     </If> </Files> # Bloquer com_ajax dans l'administration pour toutes les langues (fr, en, ar, etc.) RewriteCond %{REQUEST_URI} ^(/(fr|en|ar))?/administrator/index.php$ RewriteCond %{QUERY_STRING} (^|&)option=com_ajax(&|$) RewriteRule .* - [F,L] # Force HTTPS RewriteCond %{HTTPS} !=on RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

  Run the  rebuild_bandwidthdb_root_cache  script. /usr/local/cpanel/scripts/rebuild_bandwidthdb_root_cache Please note that the script will process bandwidth for every user on the server and not just the user you wish to manage. Introduction On occasion, you may need to reset a user's bandwidth to 0 before the end of the month. This article provides the procedure to reset a specific user's bandwidth to 0 for the month.   Procedure Access the server's command line as the 'root' user via SSH or "Terminal" in WHM. Move aside the user's bandwidth database file. mv -v /var/cpanel/bandwidth/$username.sqlite{,.$(date +%s)} Please note that "$username" must be replaced with the cPanel user's username. Move aside the user's bandwidth cache file. mv -v /var/cpanel/bandwidth.cache/$username{,.$(date +%s)} Please note that "$username" must be replaced with the cPanel user's username. Run the  rebuild_bandwidthdb_root_cache  script....

 grep "success" /usr/local/cpanel/logs/access_log | grep ":2087" | awk '{print $1, $4, $5}' | uniq Pour avoir les derniers connexion au port 2087,heure et date grep "2087" /usr/local/cpanel/logs/access_log | grep ' 200 ' | awk '{print $4, $1}' | sed 's/\[//' | sort | uniq -c | sort -nr

   uname -r dnf update -y dnf upgrade  -y reboot

 Pour checker le nombre de connexion via le webmail   grep "Logged in" /var/log/maillog | grep "rip=::1" | awk -F'user=<' '{print $2}' | cut -d'>' -f1 | sort | uniq -c | sort -nr | head -n 10 Le nombre des IPs et ::1 siginife le webmail  grep "Logged in" /var/log/maillog | awk '{print $11}' | cut -d= -f2 | sort | uniq -c | sort -nr | head -n 10 Les ips connecté netstat -antp | grep dovecot | grep ESTABLISHED | awk '{print $5}' | cut -d: -f1 | sort | uniq -c | sort -nr Pour connaitre l'IP elle c'est connecté où grep "52.98.156.101" /var/log/maillog redemarré systemctl restart dovecot Voir les stats d'anvil en temps réel doveadm who # Nombre total de process dovecot actifs   ps aux | grep dovecot | wc -l grep -E "35\.173\.197\.133|13\.218\.91\.109|52\.98\.156\.101|52\.55\.20\.105|3\.80\.183\.157|34\.228\.0\.162|100\.29\.201\.125|54\.90\.212\.216|54\.89\.33\.238|54\.82\.54\.22|54\.2...

Apache problem can affect the entire server.     With the Apache problem, this seems to have been encountered less frequently but it has occurred several times in the last few days.   # grep 'MaxRequestWorkers' /usr/local/apache/logs/error_log [Tue Nov 18 17:27:00.590507 2025] [mpm_prefork:error] [pid 3243:tid 3243] AH00161: server reached MaxRequestWorkers setting, consider raising the MaxRequestWorkers setting [Wed Nov 19 11:28:39.530182 2025] [mpm_prefork:error] [pid 3231:tid 3231] AH00161: server reached MaxRequestWorkers setting, consider raising the MaxRequestWorkers setting [Fri Nov 21 20:03:31.287851 2025] [mpm_prefork:error] [pid 3054:tid 3054] AH00161: server reached MaxRequestWorkers setting, consider raising the MaxRequestWorkers setting   The current Apache limits are shown below, which are also set to the default values.   # grep -Ei "(MaxRequestWorkers|ServerLimit)" /etc/apache2/conf/httpd.conf ServerLimit 256 MaxRequestWorkers 150   The foll...