Search results

Hi IgorG, first you wrote "try to fix with # plesk repair installation" your post to support.plesk.com is not my problem. when i run"package-cleanup --dupes" there are no duplicates i run plesk repair installation **** Product repair completed successfully. I will wait 24 hours and then see...

I received the message from 3 centos 6 servers tonight that the upgrade to 18.0.27 failed. with other centos6 servers the update went through without problems error was: Error: Cannot open file /var/cache/yum/x86_64/6/base/packages/perl-Error-0.17015-4.el6.noarch.rpm: [Errno 2] No such file or...

what speaks against it to update mariadb 5.5 to e.g. 10.3. All features of mysql 5.7 are included. https://support.plesk.com/hc/en-us/articles/213403429-How-to-upgrade-MySQL-5-5-to-5-6-5-7-or-MariaDB-5-5-to-10-0-10-1-10-2-on-Linux-

User name: moswak TITLE German translation missing on /admin/home/ System overview PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Centos7, Obisidan, latest MU Centos6, Obisidan, latest MU PROBLEM DESCRIPTION On the home page of the admin area, the German translation is missing in...

ok great, then I'll wait and see if such messages still come. What completely irritates me is that today I get another email notifications regarding the certificates that could not be renewed yesterday "although" the certificates were all manually renewed yesterday.

have you looked at the topic and especially this answer? https://talk.plesk.com/threads/tls-negotiation-failed-the-certificate-doesnt-match-the-host.356100/#post-875969

@IgorG we have to manually renew dozens of certificates every day. only with centos 6 servers. I have created a report. https://talk.plesk.com/threads/ssl-it-lets-encrypt-could-not-obtain-directory-host-must-be-a-string.356160/

User name: moswak TITLE SSL It! / Let's Encrypt - Could not obtain directory: Host must be a string PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE CentOS 6.10 Obsidian 18.0.25 Update #2 SSL It! 1.3.0-677 Let's Encrypt 2.9.0-611 PROBLEM DESCRIPTION automatic renewal of...

That has something to do with the last update of SSLIT. This seems to cause problems with the old Centos 6. [2020-04-14 10:26:02.298] ERR [panel] PHP Warning: Use of undefined constant INTL_IDNA_VARIANT_UTS46 - assumed 'INTL_IDNA_VARIANT_UTS46' (this will throw an Error in a future version of...

CentOS 6.10 Obsidian 18.0.25 Update #2 For a few days now I have received the message, but only from centos 6 servers: "Could not renew Let`s Encrypt certificates for ...." Could not obtain directory: Host must be a string The manual renewal in Plesk works without problems. What could that be ?

- Customers expand the services e.g. if the onlineshop runs better or a school needs more mailboxes etc. - some smaller companies give up and quit hosting - other companies are trying to save costs by reducing the domain portfolio or downgrade services - private customers have time and are more...

I can confirm that. and even so strange that this appears on a server that I use as a clone and that is absolutely empty and has no customers / domains.

thanks for your detailed explanation. then of course it is completely understandable that the updates take place with a time delay.

okay. So there is a difference between the release date of the new version and the start date of the automatic updates. I didn't know that this was separate. thank you for the information is not mandatory

Hi, That doesn't seem to be working properly. Obsidian 18.0.25 was released on 03/17. The day is 21.03 and the settings are still the same [updates] updateDays = friday,saturday timeFrameStart = 01 timeFrameEnd = 05 not a single server has updated :(

I'm not sure if that makes a difference. here it would be good if someone from plesk said about it. as you can see, this issue has not been considered by anyone since 11.2019.

What do you mean exactly ? The server-wide spam filter is always activated. The settings for a single email address only refer to the number of points and white / blacklist. these instructions are only available in german, but are said to have led to improvements in many of them...

we implemented this without iXHash Plugin on some servers and the detection rate has improved.

The following helped me: 1. delete all files and folders of directory "/var/log/journal". Make sure you have not deleted the journal directory itself. 2. Now delete the imjournal state file. You can file the file at "/var/lib/rsyslog/imjournal.state". This file holds the state of rsyslog...

thank you for the quick feedback and information "where people work mistakes are made" ;) no problem