• 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.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Search results

  1. D

    Plesk 10.4.4 --> 11/5/3 update fails due to php53-common/php-common issues

    Server Type: Linux Linux 2.6.18-53.1.21.el5 Centos Current Installed Panel Version: 10.4.4 #Update 56 Operation. Attempt to upgrade panel to 11.5.30 Outcome - failure. This is the key part of the error file I think: Attempt to remove 'php53-common' to resolve conflict has failed...
  2. D

    Can´t stop an spammer...

    Okay - I asked that because our 10.4.4 server was hacked and used to send 300k+ SPAM messages from local - i.e. not by relaying, and those files were involved. You have probably been hacked also so without knowing the specific cause, you should alter your plesk and ssh passwords, and lockdown...
  3. D

    Can´t stop an spammer...

    Check the following: 1/ Do you have a file called dnsquery in /etc/cron.daily ? 2/ Do you have a directory called /var/spool/named ?
  4. D

    scp -stalled-

    We use scp to download hourly gzipped backups of our MySQL databases from our plesk server. Server has a cron job that mysql-dumps locally and gzips the data into the vhost/../private directory A few minutes later, one of our local network machines (again on a cron) uses scp to fetch these...
  5. D

    Cannot call out to port 8080 on other servers

    Anybody able to suggest anything I could try to find out why port 8080 is blocked on our Plesk server?
  6. D

    Cannot call out to port 8080 on other servers

    Plesk 10.4.4, CentOs PROBLEM DESCRIPTION I cannot access port 8080 on any servers from my Plesk box. For example: curl -v example.com:8080 gives: * About to connect() to example.com port 8080 * Trying example.com... Connection refused * couldn't connect to host * Closing...
  7. D

    10.4.4 Backup Fails

    Hi Igor, thanks for the pointer. Unfortunately, I am not quite certain of what I am supposed to do. ALL the domains on the server have a webspace_id of 0 except one, which has an id of 4. I am not certain how to use the smb_apsPackages table to set the correct webspace_id. There are...
  8. D

    10.4.4 Backup Fails

    Backups have not been working on our plesk server for some time now - either scheduled or manually started. They spend quite a fair bit of time running, but then their status becomes 'failed'. The error report is: Any suggestions please?
  9. D

    Backup Fails on 10.3.1

    I have just updated from 10.2.0 to 10.3.1. Backups no longer work (either Scheduled or manually started). I am sent this information by the server: <?xml version="1.0" encoding="UTF-8"?> <execution-result status="error"...
  10. D

    Changing Apache FileETag for PCI Compliance

    Excellent, That has done the trick. Thank you Paul
  11. D

    Changing Apache FileETag for PCI Compliance

    My Plesk server is currently failing PCI scans: "Description: Apache ETag header discloses inode numbers Severity: Potential Problem CVE: CVE-2003-1418 Impact: A remote attacker could determine inode numbers on the server." I have added the following line to '/etc/httpd/conf/httpd.conf'...
  12. D

    Cannot password protect httpsdocs directories

    It definitely worked fine (for me) under Plesk 9.x The problem with .htaccess is Plesk doesn't keep the files in a standard place. There are already some 30-40 password protected directories, per domain, on this server, and just adding .htaccess and .htpasswd files doesn't work
  13. D

    Cannot password protect httpsdocs directories

    *bump* Can anybody recommend how to secure httpsdocs under plesk 10?
  14. D

    Cannot password protect httpsdocs directories

    Some of the domains hosted on my Plesk box were setup under older version of Plesk to have separate directories for http and https. Since version 10 of Plesk, if I create a new directory under the httpsdocs part of the domain, I cannot set a password for it the Control Panel. A password can...
  15. D

    Plesk 10.2 - FAILS PCI - qmail EXPN/VRFY

    No - I didn't read it - I couldn't find it! (Latest I could find was article for v9.5) - it seems impossible to see an index of those documents. I will read it now, thank you!
  16. D

    Mailman problems after switching to Plesk 10.2

    We have seen this problem with since upgrade to 10.0. Lists created in pre-10.0 plesk still work, but no admin or moderator e-mails can be delivered to them. This is whether we re-create the lists or not.
  17. D

    Mailman problems after switching to Plesk 10.2

    So - if people are seeing this with both qmail or postfix MTAs, then it must be a problem with the Plesk setup for mailman in general in v10?
  18. D

    Plesk 10.2 - FAILS PCI - qmail EXPN/VRFY

    Version. Parallels Plesk for Unix/Linux 10.2 Operating System: Linux 2.6.18-53.1.21.el5 Affected service: psa-qmail 1.03-cos5.build1011110330.18 Our server is failing PCI Compliance checks because the mail daemon is responding to VRFY or EXPN requests. Security Metrics say...
  19. D

    Mailman problems after switching to Plesk 10.2

    I am also seeing this problem on our Plesk server. Moderators and admins are not informed of pending moderation requests as qmail cannot deliver e-mails to the moderator/admin addresses as they do not exist.
  20. D

    port 8443 pcsync-https with medium strength SSL ciphers

    Please advise for the slow-witted like me. How do we restart the psa service?
Back
Top