• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Search results

  1. 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.
  2. 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...
  3. 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:
  4. 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...
  5. 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.
  6. 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...
  7. 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...
  8. 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.
  9. 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...
  10. 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...
  11. 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...
  12. 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