Search results

There is no such thing with Plesk, this is a system operation managed by the system administrator as a root user. and should be set up first before installing Plesk. Example: On a new CentOS server: You can set up the needed disk as: Disk Root: (Default server disk): / DIsk1: /dev/sdb/...

The period value is the issue here. Just chang it from 1 week to 1 day The reports mentioned in the description is just a warning icon Solved.

You can use Plesk CLI in these times. Turn WAF engine completely off: plesk bin server_pref --update-web-app-firewall -waf-rule-engine off If you do, execute this command to enable ModeSecurity and switch rule set to Atomic Standard: plesk bin server_pref --update-web-app-firewall...

Short answer: yes https://docs.plesk.com/release-notes/obsidian/update-notes/ Postfix 3.4 has an SNI support to secure individual mail domains while earlier versions don't.

There is no use for DNS without a domain and vice versa. https://docs.plesk.com/en-US/obsidian/administrator-guide/dns.59440/ Advanced: https://docs.plesk.com/en-US/obsidian/administrator-guide/website-management/websites-and-domains/domains-and-dns/configuring-dns-for-a-domain.69433/

https://docs.plesk.com/en-US/obsidian/administrator-guide/website-management/websites-and-domains/domains-and-dns/adding-domain-aliases.65286/ https://support.plesk.com/hc/en-us/articles/213372009-How-to-install-Let-s-Encrypt-certificate-for-domain-alias-in-Plesk Hope that helps.

It seems to me that the Comodo Free ModSecurity rules blocked the font request but it shouldn't crash the server, only the website at most. Or there are unsupported PHP versions that triggered this error with "Comodo" ModSec. You have three options: 1- Disable the ModSecurity Completely and...

Same here on Plesk 18.0.28 #1 How to remove this warning? I've fixed the limit issue but still persist.

They just put it on the main support page as a suggestion.

# grep exclude /etc/yum.conf ?

Sorry, the answer is for him, the thread isn't a public debate. If I didn't know that was my server private IP.. How on earth... I'm gonna handle.. IPv6. @SoufianeAb I'm not saying you can't but it's not going to be easy day to day use by just adding addresses and wait for the traffic, there...

Got it on title :)

Can you stop this sync and see the difference? Try this: https://labs.gidix.de/nginx/ What is the version for Magento and How did you install it with a deprecated mcrypt module? See this comment :

You can run your websites without IPv6 and keep your server safe from IPv6 attacks.

# rpm -qi mod_security | grep Vendor # Empty.

This might help, https://support.plesk.com/hc/en-us/articles/115002552134-How-to-manage-Plesk-Firewall-via-CLI-in-Plesk-for-Linux-

Plesk Obsidian 18.0.28 today: # rpm -qi mod_security Name : mod_security Epoch : 1 Version : 2.9.1 Not sure why rolling back from 2.9.3 to 2.9.1

Most likely : You need to open A custom rule for port 3000 and make sure your server fit the RC minimum requirements. https://docs.plesk.com/en-US/onyx/administrator-guide/plesk-administration/the-plesk-firewall-linux.72046/ The server is controlled by Plesk so it's recommended to install...

You've got 4 questions there. :) Add it to your domain "Manually" through advanced settings in SSLit. You need to issue a wildcard *.cert. or a standalone certificate for mail.domain.tld and set that on domain mail settings. You can, If it's wildcard certificate add the TXT record to...

It could be a thousand reason. if you mean you can access your server via Google interactive console by default, that is a very useful feature to use. If you mounted a volume recently, you have to add ,nofail option next to defaults line in /etc/fstab in case you removed the volume by mistake...