Search results

Many of theconfig files carry warnings about not editing - can you confirm the correct place in Plesk to configure those values on a server wide basis? Thank you for your prompt response to this matter Peter! :-)

Following for an answer... on Plesk, support for HTTP/2 is provided by NGINX, advice from NGINX to mitigate is: https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/ So far not been able to work out how this can be applied at server level.

Okay, thanks - I have done that: https://talk.plesk.com/threads/plesk-extension-transfer-of-dns-records-not-functioning.364942/

Username: TITLE Plesk Extension 'Transfer of DNS Records' Not Functioning PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian, 18.0.43 Update #1, CentOS Linux 7.9.2009 (Core) PROBLEM DESCRIPTION The extension installs without issue. When logged into the Plesk UI as...

Thanks for your reply Igor, much appreciated. I've just tried removing the extension and re-installing it but still get the same result - should I restart the Plesk service in-between?

Hi All, Been a Plesk user for a long time but only ever used for web / email hosting, we are looking to migrate the DNS hosting for our client domains from our own DNS servers to the Plesk server(s) and then sync back, so users can edit DNS records themselves in the Plesk control panel. I...

I am not sure that post is related to the issue you are having. You could try running your hostname (server.xxx-xxxxxxxx.de) through a DNS tool such as MXToolbox which may reveal the issue: Network Tools From MxToolBox ...or private message me your domain name and I will take a look!

This is the question I came to ask Pascal - did you find a solution? :)

The error 'NXDOMAIN' means 'Non Existent Domain' - the Let's Encrypt network cannot resolve your domain / hostname, Plesk have an article about this issue: Let`s Encrypt installation error on Plesk server: DNS problem: NXDOMAIN looking up A

The error message: "invalid DNS MX or A/AAAA resource record" ...suggests it is an issue with the DNS config for your domain name - care to share your domain name? (I have a bit of experience with email deliverability :-)

Just for reference in case anyone else comes across this post looking for an answer... I also got this error running a YUM update: " OSError: No such file or directory ValueError: SELinux policy is not managed or store cannot be accessed. warning: %posttrans(bind-32:9.9.4-73.el7_6.x86_64)...

Hi All This is not strictly Plesk related but I imagine it affects any Plesk server running on CentOS so really just looking for someone to confirm my understanding of it. I am running Plesk 17.5.3 Update #54 on CentOS 7.5.1804, with Apache / HTTPD 2.4.6-80.el7 (latest from repo). We have...

Okay - thats fair enough, sorry I didn't see that earlier, I only searched the Onyx forum for similar issues. It's a shame this doesn't function by default, this does mean that a fresh installation is effectively broken from the start - the spell checking is enable by default in Horde but it...

Don't get me wrong Igor... you know infinitely more than I do about Plesk and it's inner workings, I could be completely wrong and will happily hold my hands up if I am but the Spellcheck in Horde simply wasn't working as I described in my initial post - does it work on your test server? The...

Thank you for responding Igor, this raises an interesting point - I have two servers that were installed at different times... ------------------ The first server was upgraded from Plesk 12.5 to Onyx very early on: # plesk version Product version: Plesk Onyx 17.5.3 Update #32 Update date...

TITLE: Spellcheck in Horde webmail silently fails, aspell dictionary is missing... PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE: - CentOS Linux 7.4.1708 (Core) - Plesk Onyx v17.5.3_build1705170317.16 os_CentOS 7 PROBLEM DESCRIPTION: I noticed that Horde was not identifying mis-spelled...

Possibly - you will need to wait for an admin / moderator to reply

Might be better to post this in reports as a bug so that it get's forwarded to the Plesk developers: Reports Rob

I have replied to your PM, would fix up your SPF first to see if that resolves the issue. Thanks Rob

Okay - I have just sent a test message to [email protected] from one of my Plesk servers and it did not return that error so does seem to be something specific to your server. If you want to PM me your server hostname, IP and sender domain I can have a quick look for you to see if I can see...