• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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

    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.
  16. M

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

    Hello, this is the nginx configuration file that the error refers to, all configuration files for other vhosts have the same structure. server { listen "my IP":443 ssl; ssl_certificate /opt/psa/var/certificates/"my certificate"; ssl_certificate_key...
  17. M

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

    Hello, this morning plesk show the next error on screen: New configuration files for the Apache web server were not created due to errors in the configuration templates: nginx: [emerg] "server" directive is not allowed here in /etc/nginx/plesk.conf.d/vhosts/mydomain.com.conf:29 nginx...
Back
Top