aaP_chuotlua99 I want to reinstall version 6.8.27, how do I do? Because 6.8.28 doesn't work the same as 6.8.27 . Please help me
aaP_chuotlua99 aaPanel_Kern I just comment. If there is a new version, still let users choose the old version to install. Because many times they are used to the old version
aaP_llopez870407 aaPanel_Kern Gracias por el dato de los logs. He notado que el problema que he reportado sobre wordpress está relacionado con WAF Nginx, cuando lo desactivo o añado a la lista blanca mi IP no me da error wordpress. En los logs del WAF reporta como ataques la acción de subir imágenes. ¿alguna sugerencia?
aaPanel_Kern aaP_llopez870407 Hello, try adding the upload link to the url whitelist of waf Or add your local IP to waf's IP whitelist
elite Rocky Linux release 8.8 (Green Obsidian) This scan checks 2 risks, fix them in time! Please explain well since when I modify the status does not change to security. I have restarted the server and nothing.
aaPanel_Kern elite Hi, thanks for your feedback, this is a known issue. Just ignore it after changing
aaP_michal6040 hello, I have a problem that after restarting the server, nginx does not start automatically, I have to start it manually via aapanel. Everything was working great before the upgrade
aaPanel_Kern aaP_michal6040 /dev/shm/nginx-cache/wp https://www.aapanel.com/forum/d/12574-update-to-6823-result-nginx-mkdir-nginx-cachewp-failed/32
defin Hi, after updating from 6.8.27 to 6.8.28 (with Debian 11), I get these 5 security issues: Critical file permission checks Test type: Critical file permission checks Risk level: High risk Risk detail: The following critical files or directories have permission errors: /etc/shadow Current permissions: 640 : root Suggested changes to: 400 : root /etc/security Current permissions: 755 : root Suggested changes to: 600 : root /etc/gshadow Current permissions: 640 : root Suggested changes to: 400 : root /etc/shadow Current permissions: 640 : root Suggested changes to: 400 : root /etc/gshadow Current permissions: 640 : root Suggested changes to: 400 : root Solution: 1、On the [File] page, set the correct permissions and owner for the specified directory or file SSH idle timeout detection Test type: SSH idle timeout detection Risk level: Medium risk Risk detail: The current SSH idle timeout time is: 0, it is recommended to set it to 300-900 Solution: 1、Set [ClientAliveInterval] in the [/etc/ssh/sshd_config] file to be between 600 and 900 2、Tip: The recommended SSH idle timeout time is: 600-900 SSH connection attempts Test type: SSH connection attempts Risk level: Medium risk Risk detail: The current maximum number of SSH connections is: 6, please set it to 3-5 Solution: 1、Set [MaxAuthTries] to 3-5 in the [/etc/ssh/sshd_config] file 2、Tips: Set [MaxAuthTries] to 3-5 in the [/etc/ssh/sshd_config] file Panel login alarm Test type: Panel login alarm Risk level: Medium risk Risk detail: Please enable it in [Settings] - [Notification] Solution: 1、Enable it in [Settings] - [Notification] The panel is not monitoring Test type: The panel is not monitoring Risk level: Low risk Risk detail: Open it in [Monitor] - [System Monitor] Solution: 1、Open it in [Monitor] - [System Monitor] Thanks in advance