• 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

Recent content by Antonio Sanchez

  1. A

    Possible BUG: 11.0.9 #MU55 - Apache Webmail Wildcard missing by default

    It is simple. Plesk creates by default the *.webmail.domain.tld in the DNS zone becoming from Plesk default DNS templates. Therefore, it would be normal to maintain a consistent configuration, if the wildcard is generated automatically when you create the DNS zone for a new domain, it would...
  2. A

    File system loop detected

    I have this issue into a Container. Virtuozzo 4.7. CentOS 6.3 du: WARNING: Circular directory structure. This almost certainly means that you have a corrupted file system. NOTIFY YOUR SYSTEM MANAGER. The following directory is part of the cycle: `./var/named/chroot/var/named' Any...
  3. A

    Possible BUG: 11.0.9 #MU55 - Apache Webmail Wildcard missing by default

    I have detected a possible BUG in the default configuration of Plesk 11.0.9 at least in #MU55. Working with the DNS Wildcard for Webmail I have found that the system does not create the ServerAlias Wildcard according to the DNS Zone in the Apache directives. Recreate: * Create a new...
  4. A

    Article ID: 115733 from KB: Downgrading PHP 5.3 has a bug

    Hello all, Yesterday I tryed to downgrade default PHP version from Plesk 11 to a PHP 5.2.17 in a CentOS 6 VE. I followed the instructions on the KB Article 115733 and I have found a problem in the last sentence. It says: yum downgrade $(rpm -qa --qf "%{NAME} " | grep -v ioncube | grep...
  5. A

    Mailbox Quota Warning

    Hello all, I have been reading the forum searching for a solution to advice clients that their Mailbox Quota is reaching its limits. I have seen workarounds applicable to version 9.X and priors based on cronjobs and scripts. I am using Plesk 11.X with Postfix over CentOS. 1.- Is...
  6. A

    Nginx BAD GATEWAY

    Problem Solved. This is the fix. I have activated the nginx log in /etc/nginx/nginx.conf, then restart nginx. I have found an error in /var/log/nginx/error.log like that "upstream sent too big header while reading response header from upstream" I have been googling and the fix is to...
  7. A

    Nginx BAD GATEWAY

    Same problem here
  8. A

    JS files being hacked, even after micro-updates

    I can assure that the password has not been re-used. I have patched the server 3 times, reset password 3 times, delete sessions 2 times, and cleanup the infected files 3 times. The result is that the last night I was hacked from a Pakistan ISP. If I see the logs in /usr/local/psa/admin/logs I...
  9. A

    JS files being hacked, even after micro-updates

    Thanks for the help. I have cleaned the files, I am going to reset the passwords and apply this workaround. Keep waiting a Parallels Solution. Best Regards
  10. A

    JS files being hacked, even after micro-updates

    Rename de filemanager? Where? If you rename the filemanager it is supposed it stops function, isn't it? Thanks
  11. A

    JS files being hacked, even after micro-updates

    I have bad news. One of our servers, desinfected, patched, password changed and session removed has been hacked again this night. Our clients are complaining about it is the third time it happens. It is critical to solve this issue. Any thought about how to do it and why it has happened...
  12. A

    JS files being hacked, even after micro-updates

    This info about delete sessions I think must be in the Fix. Thanks a lot Best Regards
  13. A

    JS files being hacked, even after micro-updates

    Fix not solve the problem I have a Plesk 9.0.3 over Ubuntu 8.04LTS. I was hacked last week, removed the bad code, and changed all the FTP User password, root & admin. Then Patched the server. Today morning I have been hacked again. Any additional fix? Brest Regards
  14. A

    Application Vault Error: All applications failed to download

    I have changed all to 777 to test if this resolved the problem without success. Other question that has appeared is that we can't delete the Drupal Installation we have in our test site with the same error. Also, we can delete de domain, with the same error. I know I have an old version...
Back
Top