• 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 jamin587

  1. J

    Question DKIM Signature Body Hash Verified Body Hash Did Not Verify

    Here is the report from mxtoolbox Email Header Analyzer, RFC822 Parser - MxToolbox
  2. J

    Issue DKIM Authenticated problem, DKIM Signature verified

    Hi, i'm facing the same error. Did you find a solution for this Problem? Ubuntu 20.04 and Plesk Obsidian 18.0.45 Update #1
  3. J

    Question DKIM Signature Body Hash Verified Body Hash Did Not Verify

    Hm i checked now again, it is not failing on "DKIM Signature Body Hash Verified => Body Hash did Not Verify" but on "TDKIM Signature Verified => Signature Did Not Verify"
  4. J

    Question DKIM Signature Body Hash Verified Body Hash Did Not Verify

    @IgorG the KB article is not solving the issue for me and others.
  5. J

    Resolved access system environment variables with php-fpm

    Solution: Run /usr/local/psa/bin/php_settings -u after changing /var/www/vhosts/system/example.com/conf/php.ini
  6. J

    Resolved access system environment variables with php-fpm

    I need to add env[PATH] to php-fpm pool configuration for domains which are running Nextcloud. I added additional directives to the php-settings opcache.enable_cli=1 opcache.interned_strings_buffer=8 opcache.max_accelerated_files=10000 opcache.memory_consumption=128 opcache.save_comments=1...
  7. J

    Resolved 17.8.11 U2 Certificate not used although it is selected

    More Info Mailservice is working. But i used Nextcloud to authenticate against smtp by {mail.domain.com:143/imap/tls} which worked with Plesk 17.5.3. I was able to open https://mail.domain.com:443/ too. I now use {mail.domain.com:993/imap/ssl/secure/readonly} and Nextcloud works again. Ok i...
  8. J

    Let's Encrypt extension

    Yes you are right. Mailservice is working. But i used Nextcloud to authenticate against smtp by {mail.domain.com:143/imap/tls} which worked with Plesk 17.5.3. I was able to open https://mail.domain.com:443/ too. I now use {mail.domain.com:993/imap/ssl/secure/readonly} and Nextcloud works again...
  9. J

    Resolved 17.8.11 U2 Certificate not used although it is selected

    Mail Server Plesk
  10. J

    Let's Encrypt extension

    Securing Mail Server is not working version 2.5.3-354 on 17.8.11 U1/U2. (I was only able to update from U1 to U2 by assigning Certificate from Server Pool valid for mail.domain.com to domain.com) plesk server: https://mail.domain.com:8443 is fine mail server: https://mail.domain.com uses...
  11. J

    Resolved 17.8.11 U2 Certificate not used although it is selected

    Securing Plesk is ok, but mailserver uses certificate from domain. plesk: mail.domain.com:8443 => Certificate for mail.domain.com mail: mail.domain.com => Certificate for domain.com/www.domain.com/webmail.domain.com Additionally: I could only update from U1 to U2 with setting the used...
  12. J

    Issue "Select existing Database" not saved for domains

    Hello, url:8443/smb/database/list shows which database belongs to which domain. This setting is not reflectet under url:8443/smb/web/view for all but one domain. Neither changing it under database/list nor with "Select existing Database" from web/view solves this. Kind regards Benni
See more
Back
Top