• We value your experience with Plesk during 2025
    Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025.
    Please take this short survey:

    https://survey.webpros.com/
  • On Plesk for Linux mod_status is disabled on upgrades to improve Apache security.
    This is a one-time operation that occurs during an upgrade. You can manually enable mod_status later if needed.

Search results

  1. M

    Resolved MariaDB: 4C470FFFEFC4D3DC59778655CE1A3DD5E3C94F49 (untrusted public key algorithm: rsa2048)

    Hi! No changes. Same error, after that curl command. There is no /etc/apt/apt.conf.d/99weakkey-warning.
  2. M

    Resolved MariaDB: 4C470FFFEFC4D3DC59778655CE1A3DD5E3C94F49 (untrusted public key algorithm: rsa2048)

    Hi! System OS: Ubuntu 24.04.3 LTS Plesk: 18.0.75 I got this error after "apt update" as root: How can I fix it?
  3. M

    Question How to use Plesk on Ubuntu 24 with DNSBL?

    Sorry, but I don't get it. It's OK, not to edit netplan. My target is, to get that DNSBL work, without an account. Just to use local settings / local resolver. How do I setup Plesk or my server, to use a DNSBL, like bl.spamcop.net, b.barracudacentral.org, or zen.spamhaus.org?
  4. M

    Question How to use Plesk on Ubuntu 24 with DNSBL?

    In this article, they recommended using local DNS in resolving.conf (like DNS in netplan): https://www.plesk.com/kb/support/incoming-mail-to-plesk-server-is-rejected-by-spamhaus-bl-error-open-resolver/
  5. M

    Question How to use Plesk on Ubuntu 24 with DNSBL?

    If I am using the providers DNS in netplan, DNSBL won't work. The masked IP is the IP from my server provider. Not the IP from my server or the DNS IP in netplan.
  6. M

    Question How to use Plesk on Ubuntu 24 with DNSBL?

    Thanks. Yes, that is the easy part. The difficult one is, to use a local resolver. And there's no word about that, in your link. Without a local resolver, DNSBL doesn't do anything in 2025.
  7. M

    Question How to use Plesk on Ubuntu 24 with DNSBL?

    Hi! DNSBL require local DNS. I am using Plesk as Master DNS, to resolve my hosted domains. If I am using the DNS resolver from my provider in netplan, DNS is working perfectly, instead of DNSBL. If I am using local IP (127.0.0.1 or the given IP from my provider) in netplan config, DNS won't work...
  8. M

    Question no DNS answer on main domain

    That's it! I disabled DNSSEC in Plesk, and I am getting a dig-answer! Is this normal?
  9. M

    Question no DNS answer on main domain

    This could be useful, I've done another dig without "+short": dig @plesk.domain.de defect-domain.de TXT ; <<>> DiG 9.10.6 <<>> @plesk.domain.de defect-domain.de TXT ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 42443 ;; flags: qr...
  10. M

    Question no DNS answer on main domain

    Yes! What do you mean? The domain ist configured like every other domain. I just need to declare the primary (my Plesk server) and some secondary DNS. As I said: subdomains from this problem-domain are working!
  11. M

    Question no DNS answer on main domain

    Hi! As I said, I am getting an answer on subdomain and all other domains. Only this one domain did not answer. DNS is enabled. The repair does not change anything. No errors after running and same error with dig.
  12. M

    Question no DNS answer on main domain

    Hi! I am using Plesk 18.0.62 on Ubuntu 20.04.6 LTS with some domains and Plesk as Primary DNS. One of my domains got DNS Problems. No answer on main-domain, only subdomains. No answer with main-domain: dig @plesk.my-domain.de +short domain.de TXT but subdomain gives an answer: dig...
  13. M

    Resolved How to block e-mail names?

    I got more than 20 mails from name "Bitcoin Halving" with changing mail addresses. How can I block them? Using blacklist allows me to block addresses, not names.
  14. M

    Resolved Plesk Lets Encrypt outdated, would not update

    OMG! That's simple, but it works... :eek:
  15. M

    Resolved Plesk Lets Encrypt outdated, would not update

    Hi! My Plesk (Version 18.0.26) certificate is outdated. So I decided to renew it manually. After that it's still outdated. I deleted it (Home > Tools & Settings > SSL/TLS Certificates) regarding to this docs. And create a new certificate. My browser always says I got that same old certificate...
Back
Top