Suporte técnico

To permanently disable all low level kernel messages (iptables etc) from flooding the console do the following changes (as root):

Edit the file /etc/sysctl.conf Add the following line: kernel.printk = 4 1 1 7 The above changes will be effective at reboot or immediately using the following command: /sbin/sysctl -p /etc/sysctl.conf To make the changes only temporarily: echo "4 1 1 7" > /proc/sys/kernel/printk You can check the current setting with: cat /proc/sys/kernel/printk
Veja o artigo completo...

Maxmind pulled public access to the GeoLite2 databases as of Dec 31/2019. You can read about the changes here: https://blog.maxmind.com/2019/12/18/significant-changes-to-accessing-and-using-geolite2-databases/ For now you will have to register on the Maxmind site and setup a free license key: Signup
https://www.maxmind.com/en/geolite2/signup Create a free license key (When asked - Will this key be used for geoipupdate? Choose: no)
https://www.maxmind.com/en/accounts/current/license-key Then in Juggernaut go to Settings -> Geolocation Settings -> enter the MaxMind license key option.
Veja o artigo completo...

Yes we support blocking attacks like these very easily. See the howto for how to enable a custom login failure trigger:
https://docs.danami.com/juggernaut/how-tos/enable-login-failure-triggers
Veja o artigo completo...

This error means that your service provider is limiting the amount if iptables rules (numiptent)  that your VPS is allowed to create. Your provider can easily raise this limit using the command below on the hardware note (it can't be run inside your VPS). If your provider refuses to raise this limit then it's time to look for a new service provider as they do not really care about your security. vzctl set CID --numiptent 10000 --save Users using Virtuozzo with a limit set will not be able to use the country or blocklists as they will usually put them over their limit. Users can limit the amount of rules that Juggernaut will create by setting the deny permanently limit and deny temporarily limit under Juggernaut -> Settings -> General Settings. Juggernaut will rotate out older entries to stay under the limit set unless the entry is marked with "do not delete". You can also try to limit the number of iptables rules used for country block lists under Juggernaut -> Settings -> Country Settings -> Ignore CIDR blocks smaller than (set it to something like /24). This will allow you to still block the majority of the country while ignoring the smaller networks. Note
Virtuozzo 6 and below is not the ideal VPS because it does not support ipset for high performance firewall blocking. Most of the larger VPS providers like OVH, Digital Ocean, and Linode have long switched away from using Virtuozzo and now use KVM which fully supports ipset. Even Virtuozzo themselves have switched over to using KVM in Virtuozzo 7.
Veja o artigo completo...

Maxmind pulled public access to the GeoLite2 databases as of Dec 30/2019. You now need a free license key before you can download them. You can read about the changes here:

https://blog.maxmind.com/2019/12/18/significant-changes-to-accessing-and-using-geolite2-databases/ Instructions for how to sign up for the free license key can be found below: Warden Anti-spam and Virus Protection
https://docs.danami.com/warden/settings/panel-application/geolocation-settings#how-to-get-a-maxmind-license-key Juggernaut Firewall
https://docs.danami.com/juggernaut/settings/panel-application/geolocation-settings#how-to-get-a-maxmind-license-key Sentinel Anti-malware
https://docs.danami.com/sentinel/settings/panel-application/geolocation-settings#how-to-get-a-maxmind-license-key
Veja o artigo completo...

You can disable and enable the firewall from the command line using the following commands:

To disable the firewall: csf -x To re-enable the firewall: csf -e To get the list of all command line options: csf --help
Veja o artigo completo...

1. Make sure that you are not blocking the licensing server IP addresses on the servers firewall. Imunify360 is known to block our server IPs for some reason. Our licensing server IP addresses are: IPv4: 198.27.80.6 IPv6: 2607:5300:60:2106:: You can run the following command to see if your server can connect to the licensing server. You should get a response of Verify return code: 0 (ok) if the connection was successful. openssl s_client -connect www.danami.com:443 If you get the error below that means that your server cannot connect to our licensing server (usually that means there is a firewall or connection problem): openssl s_client -connect www.danami.com:443 - returns: socket: Bad file descriptor connect:errno=9 2. Make sure that the date and time on the server is correct (The wrong time will cause the SSL certificate connection to fail). Install a NTP time sync daemon on your server like Chrony or if ntpdate is installed on the server you can sync your server time using the command: /usr/sbin/ntpdate -b -s time.nist.gov 3. Many times this error can be fixed by restarting the Plesk panel: /etc/init.d/psa restart 4. Lastly make sure your openssl and curl packages are up to date: // Centos / RHEL yum update openssl curl // Debian / Ubuntu apt-get update openssl curl 5. If you have tried all of the above steps and you are still not able to connect to the licensing server please open a support ticket and include your servers IP address. The tech will run some additional tests on our side to see what the problem is.
Veja o artigo completo...

You can change the interface language under Settings -> Application Settings -> Locale   We are looking for volunteers to fix any errors with the machine translations in our Plesk extensions for the following languages: Español (Spain)
Français (France)
Português (Brazil)
Magyar (Hungary)
Русский (Russia)
Türkçe (Turkey)
Svenska (Sweden)
中文 (China)
中文 (Taiwan/Hong Kong)
日本語 (Japan) Volunteers will get a free license for every Plesk extension that they help translate. The translator must be a native speaker of the language they are translating. The license will remain free as long as they want to remain the translator for that language. Open a support ticket though our client area if you are interested.  
Veja o artigo completo...

1. Double check that the default_monitor_mode is set: Edit /usr/local/maldetect/conf.maldet and find and set: default_monitor_mode="users" 2. Some users may also need to increase their inotify file watch limit on their systems before the maldet monitoring daemon will start. To view your current limit: cat /proc/sys/fs/inotify/max_user_watches To raise your limit: echo fs.inotify.max_user_watches=524288 > /etc/sysctl.d/sentinel.conf
sysctl -p /etc/sysctl.d/sentinel.conf Start the service:

service maldet restart
Veja o artigo completo...

Maxmind pulled public access to the GeoLite2 databases as of Dec 30/2019. You now need a free license key before you can download them. You can read about the changes here:

https://blog.maxmind.com/2019/12/18/significant-changes-to-accessing-and-using-geolite2-databases/ Instructions for how to sign up for the free license key can be found below: Warden Anti-spam and Virus Protection
https://docs.danami.com/warden/settings/panel-application/geolocation-settings#how-to-get-a-maxmind-license-key Juggernaut Firewall
https://docs.danami.com/juggernaut/settings/panel-application/geolocation-settings#how-to-get-a-maxmind-license-key Sentinel Anti-malware
https://docs.danami.com/sentinel/settings/panel-application/geolocation-settings#how-to-get-a-maxmind-license-key
Veja o artigo completo...

There is a bug in the Linux Malware Detect v1.6.4 daily cron script. You can fix the error by changing line 69 in /etc/cron.daily/maldet From: elif [ $cron_daily_scan == "1" ]; then To: elif [ "$cron_daily_scan" == "1" ]; then
Veja o artigo completo...

1. Make sure that you are not blocking the licensing server IP addresses on the servers firewall. Imunify360 is known to block our server IPs for some reason. Our licensing server IP addresses are: IPv4: 198.27.80.6 IPv6: 2607:5300:60:2106:: You can run the following command to see if your server can connect to the licensing server. You should get a response of Verify return code: 0 (ok) if the connection was successful. openssl s_client -connect www.danami.com:443 If you get the error below that means that your server cannot connect to our licensing server (usually that means there is a firewall or connection problem): openssl s_client -connect www.danami.com:443 - returns: socket: Bad file descriptor connect:errno=9 2. Make sure that the date and time on the server is correct (The wrong time will cause the SSL certificate connection to fail). Install a NTP time sync daemon on your server like Chrony or if ntpdate is installed on the server you can sync your server time using the command: /usr/sbin/ntpdate -b -s time.nist.gov 3. Many times this error can be fixed by restarting the Plesk panel: /etc/init.d/psa restart 4. Lastly make sure your openssl and curl packages are up to date: // Centos / RHEL yum update openssl curl // Debian / Ubuntu apt-get update openssl curl 5. If you have tried all of the above steps and you are still not able to connect to the licensing server please open a support ticket and include your servers IP address. The tech will run some additional tests on our side to see what the problem is.
Veja o artigo completo...

Warden requires that you use the ClamAV packages from the EPEL repository. In order to prevent the wrong packages from being installed you must add the line exclude=clam* to any conflicting repositories.
For example if you have the imunify360 repo installed edit the file /etc/yum.repos.d/imunify360.repo Before: [imunify360] name=EL-7 - Imunify360 baseurl=https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/ username=defense360 password=nraW!F@$x4Xd6HHQ enabled=1 gpgcheck=1 gpgkey=https://repo.imunify360.cloudlinux.com/defense360//RPM-GPG-KEY-CloudLinux After: [imunify360] name=EL-7 - Imunify360 baseurl=https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/ username=defense360 password=nraW!F@$x4Xd6HHQ enabled=1 gpgcheck=1 gpgkey=https://repo.imunify360.cloudlinux.com/defense360//RPM-GPG-KEY-CloudLinux exclude=clam* After this is done the extension installer will be able to complete successfully.
Veja o artigo completo...

You can change the interface language under Settings -> Application Settings -> Locale   We are looking for volunteers to fix any errors with the machine translations in our Plesk extensions for the following languages: Español (Spain)
Français (France)
Português (Brazil)
Magyar (Hungary)
Русский (Russia)
Türkçe (Turkey)
Svenska (Sweden)
中文 (China)
中文 (Taiwan/Hong Kong)
日本語 (Japan) Volunteers will get a free license for every Plesk extension that they help translate. The translator must be a native speaker of the language they are translating. The license will remain free as long as they want to remain the translator for that language. Open a support ticket though our client area if you are interested.  
Veja o artigo completo...

Enabling ClamAV Third Party Signatures The clamav-unofficial-sigs script provides a simple way to download, test, and update third-party signature databases provided by Sanesecurity, FOXHOLE, OITC, Scamnailer, BOFHLAND, CRDF, Porcupine, Yara-Rules Project, etc. The clamav-unofficial-sigs script will also generate and install cron, logrotate, and man files. See: clamav-unofficial-sigs for more information. Important
• Rysnc requires that port 873 TCP OUT be opened if you are using a firewall. It must be opened in order to use the script.
• The ClamAV daemon will use over 1GB RAM when enabling the all the signatures together.
• The new signatures will be downloaded to the /var/lib/clamav directory. Centos/RHEL/Cloudlinux There are packages in the EPEL repo that make it easy to install the third party signatures. Signatures will be updated automatically using a cron that the package installs. yum install rsync wget unzip bind-utils clamav-unofficial-sigs // the config file is located at /etc/clamav-unofficial-sigs/user.conf // run the command once to test (run as root) /usr/sbin/clamav-unofficial-sigs.sh // you can view the log using the command tail -f /var/log/clamav-unofficial-sigs/clamav-unofficial-sigs.log You should see the new signatures downloaded to the /var/lib/clamav directory. Debian/Ubuntu There are no up-to-date packages for Debian/Ubuntu so we must install it manually. apt-get install rsync wget unzip dnsutils wget https://github.com/extremeshok/clamav-unofficial-sigs/archive/master.zip unzip master.zip cd clamav-unofficial-sigs-master/ cp -f clamav-unofficial-sigs.sh /usr/local/bin/ chmod 755 /usr/local/bin/clamav-unofficial-sigs.sh mkdir /etc/clamav-unofficial-sigs/ cp -r config/* /etc/clamav-unofficial-sigs/ cd /etc/clamav-unofficial-sigs/ // Copy /etc/clamav-unofficial-sigs/os/os.your-distro.conf to the parent directory as /etc/clamav-unofficial-sigs/os.conf where your-distro is your distribution and version e.g. cp /etc/clamav-unofficial-sigs/os/os.ubuntu.conf /etc/clamav-unofficial-sigs/os.conf Edit the file /etc/clamav-unofficial-sigs/user.conf and uncomment your user config options making sure to set default_dbs_rating to LOW, MEDIUM, or HIGH and uncomment the user_configuration_complete
option after you are done. # Default dbs rating # valid rating: LOW, MEDIUM, HIGH default_dbs_rating="MEDIUM" # Uncomment the following line to enable the script user_configuration_complete="yes" Run the script once as your superuser to set all the permissions and create the relevant directories: /usr/local/bin/clamav-unofficial-sigs.sh --force Install the cron, log rotate and man pages: /usr/local/bin/clamav-unofficial-sigs.sh --install-cron /usr/local/bin/clamav-unofficial-sigs.sh --install-logrotate /usr/local/bin/clamav-unofficial-sigs.sh --install-man You should see the new signatures downloaded to the /var/lib/clamav directory. Signatures Requiring Registration: MalwarePatrol Free
- We do not recommend using MalwarePatrol due to the high number of false positives from that signature provider.  
Veja o artigo completo...

Normally running nightly scans should not be necessary after doing your first full scan because all changed files in your vhosts tree are scanned automatically when the anti-malware monitor is enabled. If you would like to switch to nightly scans instead you should disable the anti-malware monitoring. When the anti-malware monitoring is disabled Sentinel will run the nightly cron /etc/cron.daily/maldet which will scan the entire vhosts tree nightly. To disable the anti-malware monitoring and switch to nightly scans: systemctl disable maldet systemctl stop maldet After the anti-malware monitoring is disabled you will see it marked as "Inactive" in the Sentinel dashboard: To re-enable the anti-malware monitoring and switch back to real-time monitoring: systemctl enable maldet systemctl start maldet After the anti-malware monitoring is enabled you will see it marked as "Active" in the Sentinel dashboard:  
Veja o artigo completo...