Search results

Wow - it works! Thank you!

I didn't find the reason but found a simple solution. Once I start a ssh-session then I see only a simple $ as prompt. The command bash does the trick. Now the arrow-keys work as expected.

I changed the ssh port from standard 22 to XXXX. The ssh-terminal in PLESK does not use the new port but failed now continously trying to connect to port 22. Where can I change in Plesk the ssh-port used by the ssh-terminal, too?

Where do I find the .bashrc for the ssh-terminal as provided by Plesk? I would like to use the arrow-keys to scroll through the recent commands etc. i.e. If there is none, where should I save a .bashrc?

Great, thanks for your help!

Oops - you are right, I didn`t know this switch and, as in your example the ssh-key switch is available here for me as well. By the way using this key-manager I see the fingerprint of one installed key. Is this the one I have installed manually? And further, I could add a key. Would this key be...

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...

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:-))

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...

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...

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...

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...

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

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...

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...

Unable to get key: Repository is not opened Still there since the update 18.0.53 /2 tonight

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.

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.

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.

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.