• 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.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • 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.

Recent content by MSandakov

  1. M

    Issue Atomic Standard ruleset problem

    Hello. It looks like there is an issue on Atomic's side. We observed that they are providing an empty file instead of an archive containing the ruleset for some Plesk installations. We are waiting for their response.
  2. M

    Issue Ports in use can't run anything

    This message means the port you want to use for your Node.js application is already being used by another application. To find the process ID (PID) of the application currently using the port, you can run `sudo lsof -i :3000`. Then, to identify exactly which command is using this port, you can...
  3. M

    Question Limit the number of recipients for a single message on outgoing emails

    I don't think so, because emails will still be sent from the Plesk server and should comply with Postfix restrictions. Potentially there might be issues with Plesk notifications if the recipient limit is set too low. However, I haven't had a chance to verify this yet. As I mentioned, this...
  4. M

    Issue Ports in use can't run anything

    Do you use the node.js toolkit extension in Plesk, or do you install node.js by hand? In some node.js projects, you manually set the port in your code. Simple example: If you choose a port that is already in use, your program will not start because the 'listen' method will fail. You'll need to...
  5. M

    Question Limit the number of recipients for a single message on outgoing emails

    Unfortunately, you cannot adjust this restriction directly through Plesk. However, you can use `smtpd_recipient_limit` in your Postfix configuration. To do this, add the following line in /etc/postfix/main.cf: Then, restart the Postfix service: This will cap the number of recipients allowed...
  6. M

    Input Pre-Announcement of Changes

    Hi @manni, We typically have a release every 6 weeks, but occasionally it might be delayed by one or two weeks. For example due to holidays. Additionally, we sometimes issue hotfix versions to address specific critical issues. These releases are not planned in advance, so you won't be able to...
  7. M

    Issue nginx configuration error after elevation

    So, nginx is currently working well and can be restarted without any issues?
  8. M

    Issue nginx configuration error after elevation

    If the addresses are the same in the ifconfig output and the nginx configuration, there might be: - an issue with SELinux. You can disable it by using the command `setenforce 0`. - another service already using this port on the interface
  9. M

    Issue nginx configuration error after elevation

    Could you please provide the result of the ifconfig command?
  10. M

    Resolved Removing PHP from chroot template

    I couldn't find anything else related to php5.6 in the chroot environment. Therefore, I believe it is true that removing opt/plesk/php/5.6 for domains will be sufficient.
  11. M

    Resolved Removing PHP from chroot template

    Based on my experience, it will not remove the interpreter from chroot environments that already have it. Additionally, if you remove it from the chroot template and reapply the template for the domain, the interpreter will not be removed because it is no longer in the chroot environment, so...
  12. M

    Issue Multiple nodejs versions

    You should execute all the commands mentioned earlier under the context of the domain owner. For example, if you have a domain named "another.check" with the user "another.check_rkm9bjgnsx9", you would execute the commands as that user. The owner of the .nodeenv directory should also be...
  13. M

    Issue Multiple nodejs versions

    Calling of node related utilities should work over nodenv. To ensure that node-related utilities are functioning properly, please check if you have the following files and directories in the home directory of your domain: /var/www/vhost/[youdomain]/.nodenv directory: This directory is essential...
See more
Back
Top