• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Search results

  1. M

    Question Why update is very very very so long

    If it's mostly stuck in unpacking, check the temperatures with lm-sensors. Might be a bad CPU fan.
  2. M

    Issue A lot of random "500 Internal Server Error" from nginx since March 10th

    Is that a real server or just a vhost?
  3. M

    Issue A lot of random "500 Internal Server Error" from nginx since March 10th

    Then the 500 actually comes from Apache. Check the Apache error log. (/var/www/vhosts/system/yourdomain/logs/error_log)
  4. M

    Question Force same domain emails to use MX records

    ... by violating quite a bunch of standards. This can only work if the google mail server is the first to receive the mails, and then relays all it doesn't know to your internal server. It will definitely break such things as fallback MX.
  5. M

    Issue A lot of random "500 Internal Server Error" from nginx since March 10th

    What are your hosting settings? Do you use nginx only or as reverse proxy?
  6. M

    Question Inefficient PLESK Partition Setup on CloudLinux - Root vs Home

    Usually you don't need /home at all. What is there in /home anyway? All subscription users should have their $HOME under /var/www/vhosts. Growing partitions is safe. I would copy the content of /home to e.g. /home2, then kill the mountpoint and the entry in /etc/fstab, rename /home2 to /home...
  7. M

    Issue Not happy with Plesk Email Security

    Only if it has write access to /var/log/.
  8. M

    Issue Not happy with Plesk Email Security

    Does the dovecot user have write access to that logfile?
  9. M

    Resolved PUM error persists....

    What is the exact line in the sources.list[.d]?
  10. M

    Issue Server almost full

    du only considers files that are actually present in the file system. It is possible to create a file, keep it open and delete it. Such a file will still be able to be used for all practical purposes while it is open, keeping its allocated disk space until it is closed, when the space will be...
  11. M

    Question Wanted: Best practice for certificates (Lets Encrypt) two separate Plesk servers for www and mail

    We have everything (mail, subdomains) except www. of our main domain hosted on our plesk server. /well-known/ is mounted via sshfs, and there's a cronjob copying the certs over (and reloading nginx). Bit kludgy, but works so far.
  12. M

    Issue Scheduled Backup: Not working anymore and access rights issues since 18.0.66

    Some subprocess might be dropping privileges, though. And that would be blocked by the --- for "other".
  13. M

    Issue Scheduled Backup: Not working anymore and access rights issues since 18.0.66

    What are the permissions of /mnt?
  14. M

    Issue Relay access denied for root mails

    Assuming this is a v6 problem, that should be ::1/128.
  15. M

    Issue 404 Server Error on slugs

    Waaait ... that's an nginx error. htaccess won't help there because nginx doesn't touch htaccess. Were those websites mistakenly set to nginx only instead of nginx proxy to apache?
  16. M

    Issue Schedule backups are missing database

    Could you please screenshot what exactly you selected?
  17. M

    Issue Out of memory but plenty of memory

    You seem to have a fundamental misunderstanding how VPS work. When memory allocation is dynamic, your provider might have underprovisioned/overbooked the VPS host and not actually have enough physical memory to guarantee you these 8GB. Probably another tenant on the same VPS host started to use...
  18. M

    Issue Legacy version to restore my server

    But you didn't restore the Plesk backup with Plesk?
  19. M

    Issue Issues with Nameservers

    Probably yes. Does any of the nameservers you configured in Plesk, old or new, show up there?
  20. M

    Issue Legacy version to restore my server

    Should be restorable with a current version. After all, the recommended way to upgrade the OS and Plesk is to migrate/restore, so it has to be able to process older backups.
Back
Top