Search results

Most default log rotations suck (as does the defaults coming with logrotate) I want all my log files rotate by size only, never by date, and I want a certain history. Having my log files with the standard names (i.e mail.log instead of maillog) also works out of the box with logwatch. I like...

Sorry for being not precise enough. I do not want to manage rotation settings for /var/log/maillog. I am looking to change /etc/rsysllog.d/plesk-mail.conf to mail.* -/var/log/mail.log or even remove /etc/rsyslog.d/plesk-mail.conf at all. Then mail logs should be in...

The default mail log file in Ubuntu is /var/log/mail.log which is also configured in /etc/logrotate.d/rsyslog Plesk does change the default in /etc/rsyslog.d/plesk-mail.conf to /var/log/maillog. Thus, logrotate does not work without modifying the rsyslog config file. Is there a special reason...

Thanks a lot for the quick answer. In fact I missed to install the NGINX component on my newly installed server

After upgrade of my vServer from Ubuntu 16LTS to Ubuntu 18LTS I am missing the OCSP Stapling option on the Let's Encrypt SSL/TLS Certificate page under Home > Subscriptions > myDomain > Websites & Domains > myDomain > SSL/TLS Certificates (see screenshots) Ubuntu 16 Ubuntu18 I did a Plesk...

Migrating to a new server has some drawbacks though, as it requires domain migration and has hostname and IP related issues. My provider offers daily backup snapshots, so I am quite safe in that I can always revert to a snapshot if something fails dramatically. They also offer a special...

Thanks for directing me to "backup" instead of the "migration tool". It was not clear to me that I can restore a backup to a newer version of the operating system. I still wonder if restoring the backup to a new server will keep my imap folders and the let's encrypt certificates intact...

I am looking for a guide to transfer my plesk settings to the same server after a new installation. As the support for ubuntu 16.04 expires in 4 months I want to re-install my vServer with ubuntu 18.04 without losing my plesk settings. In the plesk migrator extension I cannot find how to export...

Sorry, I have selected the wrong forum. This is a Plesk Obsidian for Linux topic. Can some admin please move it to that forum?

I have configured greylisting on the Tools & Settings -> Spam Filter page. This used to work properly with amazon until the end of October but in the past weeks I noticed that mails from amazon don't get through anymore From the mail logs I see that amazon uses different domains to send mails...

My system log always lists the above errors. I am running Ubuntu 16.04.6 LTS with Plesk Obsidian Version 18.0.23 Update #2 with 2 domains and lets encrypt certificates. I followed the guide at How to secure a Plesk mail server with different SSL certificates (SNI support) If I run the given...

I just installed and ran the check of the repair kit extension and it shows something like this There are incorrect permissions on some items: /etc There is incorrect ownership on some items in the WWW root directory of the domain What is this? I want to know exactly what files are affected...

TITLE: Bug in plesk firewall script /opt/psa/var/modules/firewall/firewall-active.sh PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE: Plesk Onys 17.8.11 on vServer with Ubuntu 16.04.5 LTS PROBLEM DESCRIPTION: There is a bug in the version checking part of the firewall script...

OK

There is a bug in the version checking part of the firewall script /opt/psa/var/modules/firewall/firewall-active.sh The line: iptables_version=`/sbin/iptables --version | awk -F '.' '{print $2$3}'` does return the value 60 on version 1.6.0 Thus the version check if [ $iptables_version -gt 420 ]...

I found that I did not check the output properly. 2 of the IP addresses in question did resolve to a name thus they did not show up in the iptables -L as IP adresses but as DNS records. Sorry, for raising an issue which in fact an error by me. Nevertheless I did find a bug in the version...

I have blocked some spammer IPs using a custom rule and run the activation script. At first I added 2 IPs and checked with IPtables -L Everything was as expected Then I added another 3 addresses and checked that the activation script lists the appropriate drop lines. After running the activation...

As I said this is a workaround and it will survive updates of watchdog releases which still may contain the bug. Also I I doubt that you exactly looked at the issue. /run is a volatile file system thus it is rebuilt at boot time and so you need to recreate the symlink at every boot. Also a...

My workaround to the problem is a symlink via cron entry like this crontab -e @Reboot ln -s /run/spamassassin.pid /run/spamd.pid

One could also create a link from /run/spamassassin.pid to /run/spamd.pid but it would be required to be recreated at every boot. I found that there was a mismatch on Ubuntu with spamassassin's pidfile between /etc/default/spamassasssin and the systemd service in...