• 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. Jürgen_T

    Resolved How to work with SSH Keys Manager

    Thank you for this information. I do not have the same dashboard as you have. This could be because I only have websites & Domains in the menue and not subscription. Maybe a matter of my license and/or the obsidian version I am using. In panel.log I found only the two relevant entries as...
  2. Jürgen_T

    Resolved How to work with SSH Keys Manager

    Thank you very much indeed for your explanations! Your last hint let me check also the basics again and I found permissions 600 for .ssh . I changed it to 700, produced a further new key-pair (using putty) and ... now it works! (You saved my sunday jogging training:-))
  3. Jürgen_T

    Resolved DKIM fails

    2nd part as I missed the time limit for editing. 6. Wait and then test the result a) internally with XXX.MyDomain.com => YYY.MyDomain.com b) externally XXX.MyDomain.com to an E-Mailaddress where your can read the headers of your received E-Mail 7. Test your DKIM Konfiguration with an...
  4. Jürgen_T

    Resolved DKIM fails

    So, finally I got DKIM work and I would like to share here my lessons learnt. The problem was, that I did not know, that Plesk generates a new KEY-Pair each time you push the DKIM button in /Websites&Domains/(MyDomain)/E-Mail Konfiguration/DKIM. So, making an entry in an external DNServer and...
  5. Jürgen_T

    Resolved DKIM fails

    Found the failure now. The resolv.conf was the problem as this file is continously overwritten with the standard entries nameserver 127.0.0.53 options edns0 trust-ad search . If the following modification is available then DKIM works. nameserver 127.0.0.1 nameserver 127.0.0.53 options edns0...
  6. Jürgen_T

    Resolved DKIM fails

    I configured my new server again to use DKIM. When I follow the Plesk manual I have simply to go to the E-Mail menue located in my domain. When I choose DKIM a window pops up showing the key I had to copy/paste in my external DNServer. (All keys are anonymized) This is the key I found...
  7. Jürgen_T

    Resolved How to work with SSH Keys Manager

    By the way, yesterday I found this solution which did not work - obviously: How to provide access to domain in Plesk via SFTP using SSH keys instead of passwords? - Support Cases from Plesk Knowledge Base
  8. Jürgen_T

    Resolved How to work with SSH Keys Manager

    Thank you Peter! This explains it. Yesterday I found it a little bit strange to find no menue for the key manager. Thank you for clarification. However, to generate keys is not my problem. I use PUTTYgen und this works fine for "normal" users on my new server. But it does not work for the...
  9. Jürgen_T

    Resolved How to work with SSH Keys Manager

    I moved my Webspace to a new server and would like to get limited ssh-access just to my domain using the defined system user as established before. This worked fine with my old one for root and other users but currently I can only get access as root with a key-pair. For my domain I can get...
  10. Jürgen_T

    Resolved Unable to get key: Repository is not opened

    Unable to get key: Repository is not opened Still there since the update 18.0.53 /2 tonight
  11. Jürgen_T

    Issue New php-warning

    PHP Warning: Undefined property: Net_DNS2_RR_CNAME::$exchange; File: /opt/psa/admin/plib/modules/email-security/library/ConfigCheck.php, Line: 239 Still there since 18.0.53 update 2 tonight.
  12. Jürgen_T

    Issue New php-warning

    PHP Warning: Undefined property: Net_DNS2_RR_CNAME::$exchange; File: /opt/psa/admin/plib/modules/email-security/library/ConfigCheck.php, Line: 239 Still there since Plesk update to 18.0.53 tonight.
  13. Jürgen_T

    Resolved Unable to get key: Repository is not opened

    The bug ID: PPPM-13853 with the result: "Unable to get key: Repository is not opened" is still open since the update Plesk Obsidian 18.0.53 this night.
  14. Jürgen_T

    Resolved Unable to get key: Repository is not opened

    The bug ID: PPPM-13853 with the result: "Unable to get key: Repository is not opened" is still open since the update Plesk Obsidian 18.0.52.3 this night.
  15. Jürgen_T

    Issue New php-warning

    Product version: Plesk Obsidian 18.0.52.3 - No change since last update tonight. PHP Warning: Undefined property: Net_DNS2_RR_CNAME::$exchange; File: /opt/psa/admin/plib/modules/email-security/library/ConfigCheck.php, Line: 239 still is shown up.
  16. Jürgen_T

    Resolved Unable to connect to the server via IP6

    A little bit-and-byte-wonder appeared. I just removed the new firewall-rule concerning IP6. Applied this change again to the firewall and .... my domain continues to be reachable by the IP6-address. Thank you all for guideing me to this solution!
  17. Jürgen_T

    Resolved Unable to connect to the server via IP6

    I checked fail2ban. My IP6 is already on the whitelist. So, fail2ban was not the reason.
  18. Jürgen_T

    Resolved Unable to connect to the server via IP6

    I suppose, that this cannot be the final configuration as I opened all ports for IP6. But we found out, that is a firwall matter.
  19. Jürgen_T

    Resolved Unable to connect to the server via IP6

    Peter, I followed your recommendation and opened all ports for IP6/TCP. Now it works: IPv6 Ping Output: PING mail.tenckhoff.de(2a01:238:430e:9400:f421:da1d:bef8:c802 (2a01:238:430e:9400:f421:da1d:bef8:c802)) 32 data bytes 40 bytes from 2a01:238:430e:9400:f421:da1d:bef8:c802...
  20. Jürgen_T

    Resolved Unable to connect to the server via IP6

    Yes, it is 2.0.2-352
Back
Top