• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Recent content by canadamcpherson

  1. C

    Question Plesk obsdian is ready to AlmaLinux?

    @IgorG could you also please make some comments?
  2. C

    Question Plesk obsdian is ready to AlmaLinux?

    @Pleskie Thanks my friend. Would you mind sharing the notification about Docker? I looked into the change log. I could see nothing about Docker on Alma. I use docker, so docker is important for me.
  3. C

    Question Plesk obsdian is ready to AlmaLinux?

    Thank you for your reply. Do you also see the limitations mentioned by Sopherl?
  4. C

    Question Plesk obsdian is ready to AlmaLinux?

    Thank you Sopherl. I am still waiting for Igor to answer this question.
  5. C

    Question Plesk obsdian is ready to AlmaLinux?

    Hi Igor, On this page (Software Requirements for Plesk Obsidian) I see Alma Linux is listed without any asterisks (*). However, there are asterisks (*) beside Linux 8. The explanations for the asterisks beside Linux 8 says : "**** - Plesk supports CentOS 8, however, a number of limitations...
  6. C

    Resolved Fail2Ban Cannot Access Log File Inside a Domain

    Alright. I found the solution for both issues. Here is the reason: PHP: Description of core php.ini directives - Manual
  7. C

    Resolved Fail2Ban Cannot Access Log File Inside a Domain

    Hi Jan, Thanks for trying to help. It is a permission issue, and it finds the file. It just cannot read the content. Otherwise, I would receive a "no files found" message. That said, I still tried your suggestion with some hopes and the result was no files found instead of permission denied. So...
  8. C

    Resolved Fail2Ban Cannot Access Log File Inside a Domain

    Thank you, Igor for your suggestion. It is the most logical way of dealing with the issue. I was actually successful in changing the location of the log file. Now problem is that the logs are useless. For example, “remoteAddr”:"" instead of showing any IP address. I am waiting to receive a...
  9. C

    Resolved Fail2Ban Cannot Access Log File Inside a Domain

    Not in a publicly accessible web directory. Also, it's not I placed it. The program I am using has a special directory for logs. I am not a newbie, so I hope I will receive more focused replies.
  10. C

    Resolved Fail2Ban Cannot Access Log File Inside a Domain

    Hi, I created a custom filter and jail in Plesk. The logfile is not inside /var/log/. It is inside the /var/www/vhosts/mydomain.com/httpdocs/logs/entries.log. Therefore, the log path is "/var/www/vhosts/*/httpdocs/logs/entries.log" This is causing the following permission error: f2bmng failed...
Back
Top