• 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!
  • 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. S

    Mail pop & map down after last plesk update.

    I was wrong. moved the rndc.key file to another location & restarted Bind, error now gone but still cannot start mail pop or imap.
  2. S

    Mail pop & map down after last plesk update.

    Cant help thinking this is something to do with the problem: WARNING: key file (/etc/rndc.key) exists, but using default configuration file (/etc/rndc.conf) Got this after running "service named status"
  3. S

    Mail pop & map down after last plesk update.

    Stopped smtp postfix Courier IMAP authentication daemon DNS Server (BIND) Plesk milter (Postfix) but still cannot start pop & imap Is that what you meant for me to do?
  4. S

    Mail pop & map down after last plesk update.

    Tried that & all went through ok, no errors or warning but still cannot start courier pop or imap services
  5. S

    Mail pop & map down after last plesk update.

    Got a Plesk update a few nights ago & all seemed well but rebooted my server last night & courier map & pop services will not start with errors of: courier-pop3d: bind: Address already in use courier-pop3s: bind: Address already in use courier-imapd: bind: Address already in use courier-imaps...
  6. S

    Plesk 12.0.18 MU#66

    Re-installed Postfix & that resolved the problem Thanks for your assistance.
  7. S

    Plesk 12.0.18 MU#66

    Restarted service & status is running but still cannot connect
  8. S

    Plesk 12.0.18 MU#66

    Get this error from round cube: An error occurred! SMTP Error (535): Authentication failed.
  9. S

    Plesk 12.0.18 MU#66

    Yes it's up & I have restarted the service & server. Get this warning in the maillog: warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory but from previous experience I know that all I need to do is change a file name that didn't update correctly...
  10. S

    Plesk 12.0.18 MU#66

    Postfix smtp error. Since the update I cannot connect to the smtp server from either my mail client or webmail. This has happened before & is something to do with a file name (in postfix I think) not updating during the upgrade but I cannot remember which one.
  11. S

    Resolved Godaddy ucc ssl

    I'm trying to load a Godaddy ucc ssl onto my domains but can't get it to work properly. I generated the csr from the primary domain & then added another 3 domains (SAN's) to it on Godaddy's site to create the certificate. I can load the certificate onto the primary domain no problem but I can't...
  12. S

    Plesk_saslauthd not running/working

    Solved: During the update the file /etc/sasl2/smtpd.conf was renamed to /etc/sasl2/smtpd.conf.rpmsave
  13. S

    Plesk_saslauthd not running/working

    I had a similar problem when I updated to Plesk 12 from 11 in that I was unable to send email because it appeared that smtp was unable to find the authentication service. During my attempts to troubleshoot the problem I turned off the POP service to check something & forgot to turn it back on...
  14. S

    'PHP Warning: date() driving me nuts

    The php.ini timezone was Europe/London but I realised that the problem only occurred if I used the Magento one click install in Plesk Applications. I eventually deleted the one click install & downloaded the files directly onto the server & it went through the installation when I first logged...
  15. S

    'PHP Warning: date() driving me nuts

    Bit more info. Centos 6.5 Plesk 11.5.30 Update #45 PHP 5.3
  16. S

    'PHP Warning: date() driving me nuts

    I have a Centos server with Plesk, one domain with Magento 1.9.0.1 installed with demo data just to test as I am quite new to this. All was OK until I tried to get into Magento backend & couldn't so went to change the Plesk admin password & got this error when I tried to save: Error: Failed...
View older results
Back
Top