• 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 D3nnis3n

  1. D

    Important New Plesk webmail / SOGo Webmail extension

    I will the next time I need to create a thread and it doesn't work. It currently looks like I would be able to send something (I can switch to BBCode mode, which was also blocked when I was blocked from sending the thread) and I don't want to create a useless thread :) Thanks for letting me know...
  2. D

    Important New Plesk webmail / SOGo Webmail extension

    I can confirm that after applying today's nightly build the problem is resolved. Also, because I see no other way to inform you: I am for some reason blocked from posting new threads on this forum, but I can post replies to already existing threads without problem. Next to the "There was an...
  3. D

    Important New Plesk webmail / SOGo Webmail extension

    It seems this commit in SOGo caused the problem and was rolled into yesterday's nightly build: fix(mail): escape angularJS directive for description · Alinto/sogo@47133fd I attempted to somehow send them a bug report, but for regular users that is basically impossible - even after registering...
  4. D

    Issue MariaDB upgrade fails with 521 error within Plesk due to MariaDB website being unavailable

    I was able to upgrade fine after using the posted work around: Without that however, I get the same issue discussed here and outlined in the OP.
  5. D

    Important New Plesk webmail / SOGo Webmail extension

    Since I updated Plesk to 18.0.80 today (which also updated the nightly build of SOGo), the software doesn't work anymore. Clicking the buttons to send an e-mail doesn't do anything and throws an 501 error in the developer console.
  6. D

    Issue MariaDB upgrade fails with 521 error within Plesk due to MariaDB website being unavailable

    I'm facing the same issue when attempting to upgrade to MariaDB 12.3.
  7. D

    Question How to determine renewal period for ACME SSL?

    Thank you, that is what we actually already have set. We'd personally appreciate if more configuration options would be possible, including determining the renewal schedule. I understand your concern about rate limits, but we're one of those clients you probably don't really want to see anymore...
  8. D

    Question How to determine renewal period for ACME SSL?

    Hello, ACME SSL notes it can renew certificates before expiration - I'd like to have it renew on the first of every month for all domains, no matter their expiration date. How can I achieve this? This used to be possible with the Let's Encrypt extension and a config setting for it in the past...
  9. D

    Question How to figure out where a certificate is used?

    Hello, I replaced all of our certificates with ACME SSL ones today - while doing so I deleted all Let's Encrypt ones. However, one domain didn't allow deleting the Let's Encrypt certificate, as even after removing the certificate from all places (Domain, Subdomains, Web, E-Mail, IP, Plesk Panel...
  10. D

    Question SSLs shortening validity period

    That was it. Probably it shouldn't be locked behind that when it's the only option one has ...
  11. D

    Question SSLs shortening validity period

    ACME SSL doesn't appear as provider for me after installing, even after removing Let's Encrypt. Can't figure out how to make use of it.
  12. D

    Resolved Repair Kit not working

    Using a different browser seems to indeed have worked. Pretty weird, I never opened the repair kit before at all. Might rather be related to already having been logged in to Plesk when I opened it - though that is the natural result when a process in Plesk tells me to do so.
  13. D

    Resolved Repair Kit not working

    I planned to do the MariaDB upgrade to 11.8 today and as part of the process in the web ui (the last time I did it via ssh) it requires me to check that I have the repair kit opened. Unfortuately, the repair kit doesn't work, as Google Chrome just tries to connect for a while and then shows a...
  14. D

    Resolved Weak Algorithm Warning (DSA1024) for Plesk Repositories on Ubuntu 24.04 LTS

    Doing so causes the updating problems if you have any other repositories configured that use default accepted algorithms, so they should not do that as it breaks their clients servers ... We only updated to .70 yesterday, and it did indeed restore the Imunify sources. There is no signs of...
  15. D

    Resolved Weak Algorithm Warning (DSA1024) for Plesk Repositories on Ubuntu 24.04 LTS

    So we figured this one out as well. The workaround is bad. It configures: APT::Key::Assert-Pubkey-Algo ">=dsa1024,rsa4096,rsa3072"; However, this line will replace the defaults, e.g. if this is configured, what is accepted by default will no longer be accepted when it is not in that...
Back
Top