Search results

I just installed the new update 18.0.52 but both errors continues.

As the latest Version of Plesk Obsidian supports MariaDB 10.11, I would like to upgrade now from my current version 10.6. What is the best procedure for doing this? Is this the right basis: https://support.plesk.com/hc/en-us/articles/12388091703703

Hi Peter, thank you for the clarification concerning sophos. Then it was helpful to raise this question:) I also did not know the survey results. Your roadmap include some milestones I am waiting for; good to know when to expect those. However as far as ClamAV is concerned I am not wondering...

Thank you, but then I will continue with ClamAV what works fine although I had to install it separately. By the way, do you know whether and when it could become part of the free emal-security version of Plesk? Many users are voting for this for a long time but get ignored by the develeopment...

With the update to 18.0.51 Sophos is available as free and paid extension. What is the difference?

I just installed the new update 18.0.51 but both errors continues.

Thank you, then I will wait to the next updates and let you know if these help.

Since the last update to Version 18.0.50 I receive the following warning: PHP Warning: Undefined property: Net_DNS2_RR_CNAME::$exchange; File: /opt/psa/admin/plib/modules/email-security/library/ConfigCheck.php, Line: 239 Is this a new problem for email-security? I am using the free version...

I just tested it and now it works like before. Thank you for resolving this issue quickly!

Unfortunately, after first tests the backup didn't work for me yesterday - neither with sftp nor with ftp. With that, Plesk.Backup is no longer useful to me. It needs a.s.a.p a solution!

This works, I obviously used the wrong link. Now I am using ftps and ticked passive mode and backup works again.

How can I switch from FTPS to FTP / passive mode as I cannot open tools&einstellungen/backup-manager as this leads to a hanging task? I.E. Also https://[my-server]/admin/server/tools/backup/ftp-settings/ does not work as it produces a blank screen with the headline "Tools"

Yesterday I upgraded from Version 18.0.49 to Version 18.0.50. One result: the scheduled backup for the night failed. I received the message by E-Mail: ... <?xml version="1.0"?> <execution-result log-location="/opt/psa/PMM/sessions/2023-02-12-002909.484/migration.result" local-dump-created="true"...

Found a solution. Searched the id of the hanging task with this command: # plesk db "SELECT id,type,status,finishTime FROM longtasks WHERE status <> 'done'" Deleted the found id 2215: # plesk db "DELETE FROM longtasks WHERE id=2215" And finally: # pkill task-async-executor Now message has gone.

I created a subdomain just for testing and tried tor remove it. Now Plesk shows a message, saying that this task is in a waiting state. This message does not disappear and the task is not performed for hours. How can I kill the plesk task?

Was the problem! Looking for a solution last night I found a 2nd issue. After server restart and #postfix check there were a differenc between 1. etc/resolv.conf => ... nameserver 127.0.0.1 nameserver 127.0.0.53 and 2. /var/spool/postfix/etc/resolv.conf ... nameserver 127.0.0.1nameserver...

Suddenly I receive new error messages in var/log/mail.err h2828820 postfix/sendmail[7558]: fatal: open /etc/postfix/main.cf: Permission denied Feb 1 21:13:00 h2821220 plesk-sendmail[7557]: S7546: sendmail unsuccessfully finished with exitcode 75 Feb 1 21:13:00 h2821220 postfix-local[7546]...

So, now it was investigated by Level 1 and 2 support of the Plesk Team. It is a bug. Here comes the final answer: .... Hello , Thank you for waiting Our developer's team confirmed such behavior to be a bug with ID: PPPM-13853 Currently there is no workaround provided. You may observe...

I also asked the Plesk support for taking care of this issue but they do not support drush. However, I am left with my workaround. switch openbasedir to none work with drush switch openbasedir to default. In case that something more comfortable comes to my mind I will let you know.

So, I discussed my problem with the Plesk support (which are very quick by the way:-)) and they recommended the same procedure as done before as a starting point. So I did again root@mail:/# mv /etc/sw/keys/registry.xml /root/ root@mail:/# service sw-engine restart root@mail:/# plesk repair...