Search results

Just for the history, based on the SOGo website, they do not say they support CloudLinux (Installation and Configuration Guide I think it is absolutely normal if Plesk does not provide supporting one 3rd party solution on top of another 3rd-party solution. If you have any other information...

The instruction applies to Watchdog 2.x / Monit 2.x. Watchdog 3.x uses Monit 5.x, but new Monit has slightly different conf.file syntax. Previously, Watchdog was a Plesk module and had more internal dependencies with Plesk; it was converted to an extension and now has a slightly different data...

Hi, That is true; we have added support for modern OSes for Watchdog in the latest release. The KB articles about known limitations for these OSes are still updating. If you saw the error while installing v2.x, it was expected - new OSes were added to v3.x. I believe you didn't see v3.x...

Hi! The latest release contains the fix for the issue with "Unable to get key: Repository is not opened",

As an option, you can see the blog post, Let's talk about the Plesk Docker Extension, it contains a few examples.

Just for history, let me also post here a link to the Plesk KB article, https://support.plesk.com/hc/en-us/articles/12377853490583-Unable-to-install-Plesk-on-Red-Hat-systems-Failed-to-solve-dependencies

Yes, updating will work in a standard way, as the package manager usually does. But this also means that even if the latest package contains some incompatibility or bugs, it will still be installed; nightly packages' compatibility is not guaranteed.

Then we are a step away from enabling Web Hosting :-D It reminds me that it is possible to customize web server configs in Plesk, Changing Virtual Hosts Settings Using Configuration Templates. But I am not sure if it will work with auto-discover end-points or not. Anyway, I got your idea and...

As an option, you can try to install the Log Browser extension (if it is not installed) and check the mail queue for deferred emails (server-wide and per-domain base), check the reason why they are deferred,

There is no ability to change what <domain> to use for auto-discover; the domains/paths are "hard coded" on the email clients' sides because this is a part of the protocol that describes where and how to find the valid settings; that is why applications know what link use. This means that for...

https://support.plesk.com/hc/en-us/articles/12376970141207-How-does-mail-autodiscover-work I would say it is a technical limitation. Autodiscover ("Automatic configuration for mailboxes") requires access to a special page (e.g.: "https://<domain>/autodiscover/autodiscover.xml"...

Hi! To be honest, I have not clearly understood how the components in your environment are connected to each other and what components are under your control. It seems the issue is somewhere in connections, firewalls, etc. To exclude additional software from the investigating, have you tried...

It seems the question is answered :) For history, for people who find the thread in the future, the main thing here is to switch the "Run" setting to the "Cron style"; then Plesk will pass the provided options to the cron. (c) How to add a scheduled task in Plesk UI using crontab syntax?

I am glad to hear that! But what plugin was it?

Interesting. As additional option, I recommend checking what security plugins you have in WordPress and trying to disable them one by one to find out which one blocked the IP address.

https://support.plesk.com/hc/en-us/articles/12377286180503-How-to-proxy-requests-from-domains-to-Docker-container-in-Plesk ?

Try to run the free -m in SSH, and let's see the output.

Hi! Do you have swap? Is it used by the system? Just in case, - Help! Linux ate my RAM! - Resolved - High memory usage

Thank you for the feedback, I have created an internal request to the docs.team to update the documentation page.

It seems it could be a reason. I see the file kernelcare.gpg, but its size differs from that of my systems. I can only guess you need to save the https://repo.cloudlinux.com/kernelcare/kernelcare.gpg file as /usr/share/keyrings/kcare.gpg, set the correct owner/group (root:root), and permissions...