Search results

Hi @Peter Debik . This is awesome! I was wondering if we can use RHEL 8 also? As this is what we use, we don't want to convert to Alma/Rocky.

Hi, Well after we submitted a ticket we did solved this by our selves. For whoever is having the problems: Although the servers are on the latest MU. There were "Mail Hosting" component updates which are not automatically updated. So updating these or running plesk installer...

On our RHEL7 based Plesk servers, we are currently having issues with both the Mail Server Settings page, as well as the ability to generate DKIM keys for subscriptions. The problem is the same for both issues, though with different binaries that do not appear to upgrade. When hitting OK or...

Hi @Peter Debik this one is known as PPPM-14176 . So guess we'll wait, the officicial workaround is: The current known workaround: Install BIND DNS component in Tools & Settings > Updates > Add/Remove Components as described in Plesk documentation

For one of our customers mails from one sender is rejected, because of an dkim verification message. Google is accepting these mails without problem. This could have multiple reasons so my idea was to skip DKIM verification for certain senders. I did find a (new) solution at...

I can confirm, when you do not have bind installed it does not work. After reinstalling bind on a test server (and restore dns zone) for the subscription it does work. Just to be clear: this always worked before the latest MU. Installing bind is a no-go for us per policy.

Hi, Just a kind of #metoo here. This always worked before the latest MU and now it's now showing the keys anymore, I tested this at random plesk servers (+100) and they all have the same behaviour. All our servers come without bind, so I will check if this will "fix it" .

Are you sure your resolving (/etc/resolv.conf) nameservers are ok? Sounds something networkish.

Hi y'all, At the moment we are using the legacy Lets Encrypt module for securing the panel/mail with: plesk bin extension --exec letsencrypt cli.php --secure-plesk -m [email protected] -w /var/www/vhosts/default/htdocs -d fqdn.panel.com I tried to find it on the forum and in documentation...

Yehh i know this one :-) But I thought the version in the version had deprecated that version. But you helped me a lot @IgorG thanks!

ahhh ok! So the SELECT val FROM misc WHERE param = 'version' is still the prefarable version string (currently 018000000) ?

Hi, We are working on a facter/ansible inventory script. And we are looking to get some versions. We know there is the /usr/local/psa/version file which contains (example): 18.0.28 CentOS 8 1800200703.14 Is there any who knows how to parse the last version string?

@SpAcEDeViL imho it's not correct way to fix it and to bad there is no official answer yet from Plesk. Well here is the short quick fix: cat >> /etc/httpd/conf.d/a_httpoxy.conf <<EOF # httpoxy fix jul 2017 <IfModule mod_headers.c> RequestHeader unset Proxy early </IfModule> EOF And then...

Sweet, thanks tozz!

Yes i can confirm it's ziggo only customers So not a plesk problem, our directadmin servers have the same problem.

Hi toz. Are u using spamexperts by any chance too? We are seeing This problem too but only when using spamexperts.

Oke great that did worked, I had todo a restart of plesk services. So these are all the steps you need (For whoever needs it): rpm -e php-fpm psa-phpfpm-configurator service sw-cp-server restart service sw-engine restart service psa restart Thanks @igor +1

no output :-) So I can remove both of them?

Well in our case we only have the system php installation: rpm -qR psa-phpfpm-configurator-1.0.0-cos7.build1205150819.14.x86_64 plesk-base >= 12.5.30 psa-mod_proxy php-fpm >= 5.4.16 psa-php5-configurator /bin/sh rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1...

Well that was my idea but I get: php-fpm >= 5.4.16 is needed by (installed) psa-phpfpm-configurator-1.0.0-cos7.build1205150819.14.x86_64