• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • 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. I

    Bug with SMTP banner - urgent

    This "Received" section describes the path of your letter from webmail to plesk mailserver (postfix). i.e.: your postfix mailserver received this letter from your webmail. So, why do you think Plesk mailserver helo does not work properly? Check "Received" on plesk->gmail stage. there you should...
  2. I

    Bug with SMTP banner - urgent

    Hm... than that's serious mistake in french locale. It definitely should be reported to Plesk team. Originally, plesk mailserver screen have no option to manage SMTP banner, but you can manage there SMTP greeting which plesk mailserver will use as a HELO with connection to destination server.
  3. I

    Bug with SMTP banner - urgent

    Again, do not mix SMTP Greeting with SMTP Banner.
  4. I

    Bug with SMTP banner - urgent

    so, please, show me where i can manage SMTP banner in Plesk
  5. I

    Bug with SMTP banner - urgent

    No. You are talking of two different things. It's Server SMTP Banner and it has nothing to deal with how Plesk configured to send outgoing mails. Do not mix SMTP greeting and SMTP banner.
  6. I

    502 Bad Gateway after upgrade on subscriptions

    Well, now you have mixed up packages I suppose. Some of plesk packages are still for debian 6 system and you should manually upgrade them to debian 7. The problem which you have to solve is to compare packages on your system with clean install plesk for debian 7 and upgrade yours with force...
  7. I

    Fresh install - nginx and php-fpm don't start

    Check you have Nginx enabled in Plesk panel -> Tools&Settings -> Services Management Enable it in Plesk nginx will not start by # service nginx start if it's disabled in Plesk
  8. I

    Fresh install - nginx and php-fpm don't start

    what is the output of the following commands: # systemctl stop nginx # systemctl start nginx what is in nginx error log after it?
  9. I

    Fresh install - nginx and php-fpm don't start

    use # setenforce 0
  10. I

    Fresh install - nginx and php-fpm don't start

    just to be sure - how did you disable it? what is the output of getenforce after you have disabled it?
  11. I

    Fresh install - nginx and php-fpm don't start

    hm... it definitely should contain selinux logs in case you have audit daemon disabled. Try to temporary disable Selinux and restart services like mariadb, nginx, psa... to finally exclude Selinux from list of possible reasons.
  12. I

    Fresh install - nginx and php-fpm don't start

    what is status of Selinux? (# getenforce) if it's enabled try to find some deny records in /var/log/messages
  13. I

    Mod_security log trouble

    Plesk logrotate already have record for modSecurity: # cat /etc/logrotate.d/mod_security /var/log/modsec_audit.log { daily rotate 7 missingok compress postrotate /etc/init.d/apache2 reload > /dev/null 2>/dev/null || true endscript } and I suppose that apache reload is enough, because...
  14. I

    Access to the server over SSH : forbidden to /bin/sh -- IS IT SAFE ?

    IMO give ssh access to subscription user is not safe by default
  15. I

    How to change Power User view to Administrator

    Tab "Server" -> "Interface Management"
  16. I

    Pre upgrade questions [11.5.30 to 12.0.18] libapache2-modsecurity

    Following will show you installed modSecurity packages: rpm -qa |egrep 'mod.?security' Then use yum utility to remove it
  17. I

    What happened to my FTP when I upgraded to version 12?

    /etc and /lib are sensitive directories for chrooted proftpd and it is not safe to write there: http://bugs.proftpd.org/show_bug.cgi?id=4018 You can add "RLimitChroot off" to proftpd.conf on your own.
  18. I

    Postfix not accpeting Plain Authtentication

    Try to inspect maillog (/var/log/maillog) What is the error on attempt of plain text authorization?
  19. I

    Hard diskquota install error

    this may help you: sudo rm /../aquota.user /../quota.user sudo quotacheck -F vfsv0 -avum
Back
Top