Search results

The same here: 2.6G /var/log/kolab-syncroton/console.log 2.5G /var/log/kolab-syncroton/errors.log Obviously no rotation configured. How to fix this?

This worked for us on. Thank you.

Because Spamassassin is already on the server, this solution probably help: 1. Editing Postfix We need to configure Postfix so that it can pipe mails through SpamAssassin. So run the command below to edit Postfix main configurations file: $ sudo nano /etc/postfix/master.cf Look for the...

Great. Really simplify interactions with the support.

What if custom ssh port is used or other restrcitions on the server for ssh?

We used Custom Plesk Host extension for years on our server. Now after we set "Permanent SEO-safe 301 redirect from HTTP to HTTPS" for most domains, redirecting isn't possible more because all browsers block this with warning about unsecure connections. Custom Plesk Host extension worked fine...

That fixed the bug, but again and again these problems with Atomic are annoying. Obviously they don't have many things under control anymore. Update 20. 10. 2018: This morning are mails again in my inbox. Not fixed.

There seems to be something on Atomic's side again that needs to be fixed by them. Only this solution can help temporarily: Notification in Plesk: Error: ASL has not been configured run-parts: /etc/cron.hourly/asl exited with return code 1

But I'm asking how can happen again if: "Resolution The issue has been fixed on Atomic ModSecurity side. Fix should be delivered in scope of rule set update, so in order to force it, enable and disable Atomic Basic ModSecurity via Tools & Settings > Web Application Firewall."

This helps again: Notification in Plesk: Error: ASL has not been configured run-parts: /etc/cron.hourly/asl exited with return code 1

This morning again on few servers. All Ubuntu 16.04 LTS

Hi Andreas, Probably is this solution: Resolved - Avoid root folder path (INBOX). Regards, Mike

Same here on 3 servers. All on ‪Ubuntu 16.04.4 LTS‬.

Same here. Running test on SSLLabs show me a lot of weak cyphers.

On Plesk 17.8 you can activate per domain Nginx Cache under Apache & nginx, what you already know and you can skip step 1. Just proceed with Step 2. Plesk write in /var/cache/nginx for any domain separately. Check proper path to add in WordPress NGINX Caching Plugin. Under Apache & nginx...

Why is not working? We implemented successfully and is working fine.

And check nginx.conf for your domain to see proper nginx cache path in /var/cache/nginx

Probably help this article: https://www.alibabacloud.com/blog/blogblogwordpress-caching-solutions-part-2---configuring-nginx-fastcgi-static-page-caching-and-final-load-testing_328726

I found this: Cannot send messages between internal mailboxes: DMARC: REJECT message but I'm having issues with external mails and Plesk is up to date.

Hi, From time to time are some mails from valid senders rejected with: DMARC: REJECT message for [email protected] message discarded by a mail handler In Plesk is DMARC policy set to default: V=DMARC1;p=none Example from maillog...