Search results

Hi, make sure the cron service is running (it happened to me a while back with an old Debian machine that nothing was being rotated because of that).

Hi, while you try to find out what happened you can temporarily limit the outgoing emails for the affected domain/subscription/mailbox: https://support.plesk.com/hc/en-us/articles/12377316784663-How-to-set-limitations-on-outgoing-email-messages-in-Plesk

Sorry, this was not explained in the link, is this a valid entry?: [updates] timeFrameStart = 05 timeFrameEnd = 09 or should it be: [updates] timeFrameStart = 5 timeFrameEnd = 9

Perfect, thanks!

Hi, today Plesk updated itself on my server from 18.0.62.2 to 18.0.63.4 at 12:20PM. This is a production server and although the update had no errors I don't think it should be done at a peak hour like that. Is there a way to limit the timeframe when plesk runs the autoupdate? Thanks in advance.

Hi, no problem for me at all making a copy before updating, I just wanted to know if I had to.

Hi, over the years I've been adding manually to the apache-badbots fail2ban filter specific entries for my server. Will these be lost if I update Plesk to version 18.0.63? Per the changelog (https://docs.plesk.com/release-notes/obsidian/change-log/?18063-mu3#plesk-18063):

Hi, first of all make sure the cron service is active. Then check this file: /etc/logrotate.d/rsyslog, it should have the log rotation config for maillog. Also you should have this file: /etc/cron.daily/logrotate that does the log rotation every day if the cron service is active (again, check...

Does it ship active by default with new installs? My two newest servers come with it (I assume it's the rearrangable blocks one, I actually like it)

Hi, the Plesk server is where the database is, I needed access to it from my local machine. I changed it on the plesk server by adding the new port to the /etc/mysql/mariadb.conf.d/50-server.cnf file under mysqld. This worked because now I can access the database hosted at Plesk through that...

Product version: Plesk Obsidian 18.0.61.5 OS version: Debian 12.5 x86_64 mariadb Ver 15.1 Distrib 10.11.6-MariaDB Hi, I needed remote access to a subscription database, I follow a couple of docs and everything worked fine. Now I figured to change the default Mariadb port (my first time doing...

I can also confirm this. Last week I upgraded a Debian11 with Plesk to Debian 12 (following the manual steps detailed here: https://support.plesk.com/hc/en-us/articles/12377714344983-How-to-perform-dist-upgrade-procedure-on-Linux-server-with-Plesk), and these messages are not showing in this...

Hi, you don't need client credentials for migrate to another server, I did that to speed the process (changing DNS records and the like). I think you can manage to do it all with the plesk cli commands, which I was forced to fast-learn. I was unable to get official support because the OS and...

I'm still unable to log in as admin, but since the resellers and costumers access work, I've asigned all the subscriptions to 1 reseller via plesk cli to help migrate them all to a new server where I've reassigned them again. Feel free to mark this as solved.

Update: I'm able to login as a costumer, but admin still fails.

Product version: Plesk Onyx 17.0.17 Update #63 OS version: Ubuntu 12.04 Hi, I have a very old server, and since this morning I can't log in to the admin panel. When I tried to log in as admin I get this error: ERROR: syntax error, unexpected '?' (Helper.php:569) What I've done so far (After...

Sorry for the noob question but, how can I test it like that on my server? I'm not very familiar with fail2ban-regex tests, but that result looks very promising.

Hi, check if there are any forwarding from accounts on the Plesk server to Gmail. The only ocurrence on my server of this exact Gmail error (sometimes blocked, sometimes just delayed) was on forwarded messages only, but maybe it has some impact as well on the rest (I didn't experience this on...

This happened to one of my clients early last year with a major international airline. I did exactly the same, temporarily whitelisting.

Hi, I think it might be because the reject policy is set on the source domain, not the one hosted in Plesk. If source domain policy is reject and for some reason the source mailserver is not properly configured it can lead to this error. If this is so, you could exclude the source domain from...