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

  1. M

    Resolved Error when importing emails

    Hi again, I think I have found a solution, deleting the Site Import extension and reinstalling it has made it work again. Thanks for your help.
  2. M

    Resolved Error when importing emails

    Good, thanks for the quick response, I just updated to version 18.0.63 Ubuntu 22.04 1800240816.11 and the problem remains the same, what can I do? Thank you.
  3. M

    Resolved Error when importing emails

    Good, I am trying to import emails from mail/import mail but I can not get that once the import is done I generate the list of emails that has been imported, it only happens with a single domain with the others is shown correctly. In addition I attach an error that has thrown me the on one...
  4. M

    Resolved DNS issues after domain migration to Plesk server

    Good morning, sorry for the delay, the problem was generated by a firewall rule too restrictive, thanks for the answer.
  5. M

    Resolved DNS issues after domain migration to Plesk server

    Good morning, recently i change the name servers to one domain from one enterprise to my plesk server, but the MX record doesnt work. The problem is caused because that same record MX mail.------------.com was resolved by other ip and now my Plesk server try to connect to the old ip instead of...
  6. M

    Issue High CPU usage and Swap full despite have RAM avalible

    Good morning, this is what I have added to my nginx configuration file:
  7. M

    Issue High CPU usage and Swap full despite have RAM avalible

    Good, I tried to add this Nginx configuration but I get this error: Invalid nginx configuration: nginx: [warn] protocol options overridden for 172.26.24.152:443 in /etc/nginx/plesk.conf.d/vhosts/mydomain.com. conf:7 nginx: [emerg] unexpected ";" in...
  8. M

    Issue High CPU usage and Swap full despite have RAM avalible

    I think so too, it's too low, this instance runs on the AWS lightsail service and by default the instances have 1gb of SWAP regardless of the amount of RAM you choose. Do you think increasing it will improve performance? Thank you.
  9. M

    Issue High CPU usage and Swap full despite have RAM avalible

    Good morning, first of all thank you very much for the quick response. We have made the checks you have suggested, I will give you the results. In the log files you tell us we have found the following amount of requests to our host with more traffic: 46678 requests that do not include the word...
  10. M

    Issue High CPU usage and Swap full despite have RAM avalible

    Good morning, as I say in the title we have large CPU usage of our hosts, the hosts that have more traffic are Prestashop with version 1.7.8.8.8 with PHP version 7.4.33, for these hosts we use PHP FPM for Apache and Nginx as a proxy. In addition to this we have an excessive use of SWAP, I attach...
  11. M

    Resolved DNS problems with Offices 365

    Good morning, sorry for the delay, it seems it was a temporary problem with Office, thanks for the quick response.
  12. M

    Resolved DNS problems with Offices 365

    Good morning, until two days ago we had the mail of our domains working with Office365 and our Plesk server acted as DNS for these domains, but yesterday we started to not receive some emails randomly, the solution that we have come has been to use our domain provider as DNS server after this...
  13. M

    Resolved Nginx error "nginx: [emerg] "server" directive is not allowed here in /etc/nginx/plesk.conf.d/vhosts/mydomain.conf:29"

    any suggestions on this ? Thanks.
  14. M

    Resolved Nginx error "nginx: [emerg] "server" directive is not allowed here in /etc/nginx/plesk.conf.d/vhosts/mydomain.conf:29"

    Good morning, after the last update should I click on this message or not ?, I don't want to generate more problems on my server by generating new configuration files. "New configuration files for the Apache web server were not created due to errors in the configuration templates: nginx...
  15. M

    Resolved Nginx error "nginx: [emerg] "server" directive is not allowed here in /etc/nginx/plesk.conf.d/vhosts/mydomain.conf:29"

    Hello, no, i dont have any additional directive on that domain.
See more
Back
Top