• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Search results

  1. M

    Issue Domain Alias - Mail not forwarded

    With that setup, nobody would be able to send email to support@longdomainname.com unless that account is configured at google too. The MX with the higher number will only be tried if google's server can't be reached or responds with a temporary failure code. But an account that isn't recognized...
  2. M

    Issue Lots of uncompressed log files generated

    fail2ban maybe?
  3. M

    Question Recovery Plesk from Damaged Ubuntu Server VM

    Doesn't aptitude give you any options to resolve those dependencies?
  4. M

    Issue Can not send email to outlook's, check the 'Undelivered Mail Returned to Sender' information may the wrong DNS ,so hao can i config the dns of Plesk

    I do not support spammers.
  5. M

    Resolved PLESK 18.0.60 Problems to configure mails / Certificates, etc.

    As long as the A/AAAA records for serveur001.domain.com do not point to cloudflare, that is not a problem. You can use the same certificate on different servers. You can also use different certificates as long as the issuer is not forbidden via CAA record in DNS. You can even use different...
  6. M

    Question Strategic questions

    I think I'm seeing something similar here ... this morning at 6:26, Plesk updated itself to 18.0.63mu3. Just a minute later, I got a Package Update Manager notification for 108 packages, some of them skipping several versions (e.g. "libc-bin 2.31-13+deb11u10 from Debian-Security for...
  7. M

    Question Redis

    You haven't? What did you try, then?
  8. M

    Issue 502 Bad Gateway - New Install - Restored from Backup

    I would guess it is this problem again: Issue - apache2 proxy target - wrong ip-address
  9. M

    Question Redis

    Isn't that by design? I think you'd need to use separate redis instances if you want to avoid this.
  10. M

    Resolved PLESK 18.0.60 Problems to configure mails / Certificates, etc.

    or you could just use webmail.domain.com for imap and smtp ...
  11. M

    Question SELECT COMMAND IN MYSQL QUERY FROM SHELL SCRIPT

    ${} does not do what you think it does. Lose the {}. And it's 'exit', but you don't actually need that because the script ends anyway.
  12. M

    Issue Access to a database from another plesk server

    Oh, and you should restrict the mariadb users to that IP. See mysqltuner for how.
  13. M

    Issue MariaDB High "created tmp disk tables"

    No, it's just that you're listing the worker status. SHOW GLOBAL STATUS LIKE 'created_%'; has a very different result.
  14. M

    Issue MariaDB High "created tmp disk tables"

    Did you recently restart the mysql server? Also, you should have a look at mysqltuner. Don't blindly follow the recommendations, though.
  15. M

    Question Ioncube Loaders in usr/bin/php ?

    /usr/bin/php is a link to /etc/alternatives/php. Use update-alternatives to change what /etc/alternatives/php points to.
  16. M

    Issue apache2 proxy target - wrong ip-address

    plesk bin apache --listen-on-localhost <true|false> switching it around a bit should make it consistent again see also Resolved - SECURITY - attack surface : ports 7080 and 7081
  17. M

    Issue apache2 proxy target - wrong ip-address

    External ip was the default not very long ago, so you might have a mixture of old and new settings there.
  18. M

    Issue Sometimes it is not possible to connect the panel via :8443.

    and second, use tcpdump to listen to traffic on 8443 to check whether anything arrives at your server at all. Some mobile providers use a lot of transparent proxying and several layers of NAT and may not route traffic on unusual ports.
  19. M

    Issue MariaDB High "created tmp disk tables"

    Caveat: O_DIRECT can lead to problems with SoftRAID where the RAID might appear inconsistent (the data in that place would be garbage anyway though).
  20. M

    Resolved Plesk backup can not Dump databases MariaDB 10.6.7

    Those two are server settings, so they do require a restart.
Back
Top