Search results

@deepnpisgah For this purpose, it is better to add a paid for SSL certificate, for many reasons. This paid for SSL certificate has to be ordered elsewhere and has to be "uploaded" manually in Plesk - after that, you can assign it to the domain in question. Why should this be preferred over...

@custer Two questions : 1 - any update on wc cli (WooCommerce command line utility) integration? 2 - can you have a look at migration consistency? With respect to question 2, please note that migration of a WPT managed WP instance to a target server CAN result in notifications (on the...

@mow, @mjehlenz The error 103 code is unknown and the drweb update behavior is quite unexpected. However, there are some indicators of the root cause of the problem in /var/log/syslog (on Ubuntu) : 1 - notification : Can not update key file, trying to make update with old key file ...

@danami The re2c package should be included by default and also the plugin is enabled by default - at least, that is or should be the default on Ubuntu OS. However, this does not explain the issue itself ..... but yes, you are right : people should first check those packages/settings before...

@kek, In all honesty, you should simply block specific ports for the sake of security. For instance, if you are the sysadmin and the only one required to access SSH, then use Plesk Firewall Extension to allow you access and block ALL OTHERS. For instance, if you see any (really) suspicious...

@Andreas2022 Even though Fail2Ban may impose some performance issues, it is not very likely that your server is hindered by Fail2Ban. Curl is barely relevant in this equation. The equation consists of a web crawl (piece of cake for the system, even though the external site might block you...

@danami First of all, the command spamassassin --lint is a very rough indicator of config errors, not of compilation or code errors. I too have checked a number of Ubuntu servers, with new and old Plesk versions. The older Plesk versions have this (and some other minor) issue(s), the newer...

@Peter Debik It seems to be an URGENT matter. In some cases, the spam filter regexp - for instance, those used to whitelist domains in the form of *@domain.com - will not work properly. As a result, particular mails will not be received. I am not sure (yet) how these cases particular...

@danami I have reported a "bug" that is related to the Plesk eco environment and that produces an "annoying" error notification in the maillog at restarts of spamassassin. It does not have a major impact on the functionality of spamassassin, only a slight effect can be noticed. The problem...

@Andreas2022 Your script is probably causing the overload. I would suggest that you 1 - reboot the server (and immediately check user_beancounters afterwards .... it should not have failcnts) 2 - monitor the server before the script is run : if user_beancounters shows failcnts, then it is...

ADDITION ISSUE : spamassassin 3.4.4 NOT recompiled - the 403 'body_0' compiled rules issue OS Product version: Plesk Obsidian 18.0.58.2 OS version: Ubuntu 20.04 x86_64 Build date: 2024/01/23 15:00 Revision: 37aa23e80de6aa54485384af35d425af8d131d4b NOTES When running...

Username: TITLE Spamassassin issue - not compiled or not compiled properly PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Tests on 3 OSes, various results OS with compilation errors : Product version: Plesk Obsidian 18.0.59.2 OS version: Ubuntu 18.04 x86_64 Build date...

@WebHostingAce Please check line 35 of /etc/apache2/modsecurity.d/rules/tortix/modsec/tortix_waf.conf and verify whether it contains SecAuditLog logs/audit_log If that is the case, then a referral has been made to a non-existing directory, hence causing Apache to fail to start. Simple...

Username: TITLE Apache2 ModSec Error - Apache2 fails to start and AH00111 error PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Product version: Plesk Obsidian 18.0.56.4 OS version: Ubuntu 18.04 x86_64 Build date: 2023/11/06 22:00 Revision...

@muckaveli Glad to hear that the issue has been resolved! Nevertheless, a bit strange what happened there at IONOS. You should keep track of issues like this, since the basics (of setup) were not complied with by IONOS ....... and it is likely that a similar issue will occur. If something...

@ mow, The purpose of the statement is not entirely clear to me, please explain. In general, there is this common mistake about disks and adding disks - adding disks for the sake of increasing capacity alone is not resolving any issue, unless the configuration is adjusted to store data...

@Peter Debik You are stating the obvious, but you are - apparently - not aware of the fact that "reconfiguration" is not a solid solution - it is a solution, not thé solution. In essence, the "protocol options redefined" issue is associated with : 1 - a root cause of the problem : wrong...

@learning_curve the web configurations troubleshooter itself is not working properly, so that is an additional bug. In essence, there are still some error notifications with respect to "protocol options redefined" for some domains in specific circumstances. The aforementioned error...

@lara-missk ..... no worries, here to help if and whenever possible!

@muckaveli Please note that I am a bit lost here, since I see SFTP and FTP(S) mixed in most posts. What do you exactly want to do? SFTP? or FTPS? That seems to be a "question after the solution", but it is a relevant question. In essence, SFTP and FTPS are totally different and both have...