• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Issue Get public key CLI error

Edi Duluman

Basic Pleskian
Hello!

I just wanted to run the following, to get my public key for a domain and I got the following error:
Code:
# plesk ext git --get-public-key -domain agency.as
Method Modules_Git_ApiCli::getPublicKeyCommand() does not exist exit status 3

Debian 8.6, Plesk 17.0.7 #6

As a related question, do you know where the public keys are located ?
I want to grab one's fingerprint but I don't know where those are stored.

Cheers!
 
Hi UFH! Thanks for the fast reply!

Gotcha! Didn't think about it this way.

Regarding my second question, do you have any advice ? I want to get a key's fingerprint using ssh-keygen to send it to GitHub's support as when I'm trying to add the key was generated in Plesk when creating the repo, it says Key is already in use, which is a bug from their end as I github ran into some issues when I wanted to add my key the first time.

So, now they're asking me for the key's fingerprint and I don't know how to find it. Also asked Plesk Documentation via Disqus, but I am yet to get a reply there.

Cheers!
 
Hi Edi Duluman,

if you want to get the key's fingerprint, you would use the command:

ssh-keygen -lf /path/to/ssh/key/which/you/generated/normally/named/with/the/ending/".pub"
 
Hello!

I don't think I made myself clear enough, sorry. I want to get the fingerprint of the key which Plesk ( GUI ) generated for my domain when I set up Git onto a domain. Chose Remote Repository, wrote the [email protected]:User/Repo.git address then Plesk gave me the public key which I needed to add in my Github repo.

So, I wanted to know where are those keys located, or, if possible how to force Plesk into regenerating it so I can add it inside Git ( as they say my key is already in use, though I have just created it last night, before trying to add it )
 
Hi Edi Duluman,

o.k. some basic knowledge here:

Your "Git" - settings can be viewed at "Home > Subscriptions > YOUR-DOMAIN.COM > ( depending (sub)domain, where it states: Enabled ) Git > Repository Settings"

On your server, you can view the public+private - keys at "/var/www/vhosts/YOUR-DOMAIN.COM/.ssh"​
 
Thanks! Where is this basic knowledge located, I am yet to find it in the Plesk Documentation.

When creating a Git repo from Plesk GUI I get the same public key for a domain, as well as it's subdomain. Is this expected behaviour ? How am I supposed to use Github on a domain with one repo, and a subdomain of the same domain, on another repo, if the keys are the same ?

Code:
domain.com
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQCpgakI6CipUakonAOjtiMzebQrYA6+7MmMSLUzTdYt65C0njNTed5NHS2jlEFts66g6OYq1LKlZSIC6prpeROaPBCfBaNVf6T4p5GnTasi5AII1tg2AI3fuyG0bjO4vHtep0Hf6EDcRbVFuOcvvhCu5Ye5F27JLO5wB8Nd/J7HeLpkUBR+OEBrYQLRWPA3Sr8eev71PxQhtjRYM1kr/c/yvGOrEy/qqqLKrWkVvBDU7iFUkO3Hl2IPlL2R87cHp8zlMUS0c/rWPJSOLNjaC14IifAiANvL6pfIVhr9cbBSrgvFwHHx2mrtBvSOGeQvXDqMcD2RLyqwWmrNV/1gjbwQGvc8r2qi3jEdeNuAb/I7MhIL7WnWlLIXSpgNETMIzMa04zJX1kMd96V1HHqoQUZrtNELVTVIKDUIGRcCUngx295jO5trfIJ41Q4r8MKC1F0qNI3CgcTK2O3i45rwj68e05FEPMX4NWVCo2TopAi8dpz9px2x6APiPG39bUbxHrKvv4DQHkRLeI1vI+0cYAifOK7Eheh6UAxDW5Yml3VWc0yEB18lzYGuDaqquCFevAL7nzYd30jBpGKn5of6WIW2HoxpEzqRAGfC52sOJShCsiA7QnM3bM/UnBhnhmGuFCsq/7P4rGn0oTh1ntnTC9iL3/wvuDVppZmZLQ4GHWuoew==

chat.subdomain.com
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQCpgakI6CipUakonAOjtiMzebQrYA6+7MmMSLUzTdYt65C0njNTed5NHS2jlEFts66g6OYq1LKlZSIC6prpeROaPBCfBaNVf6T4p5GnTasi5AII1tg2AI3fuyG0bjO4vHtep0Hf6EDcRbVFuOcvvhCu5Ye5F27JLO5wB8Nd/J7HeLpkUBR+OEBrYQLRWPA3Sr8eev71PxQhtjRYM1kr/c/yvGOrEy/qqqLKrWkVvBDU7iFUkO3Hl2IPlL2R87cHp8zlMUS0c/rWPJSOLNjaC14IifAiANvL6pfIVhr9cbBSrgvFwHHx2mrtBvSOGeQvXDqMcD2RLyqwWmrNV/1gjbwQGvc8r2qi3jEdeNuAb/I7MhIL7WnWlLIXSpgNETMIzMa04zJX1kMd96V1HHqoQUZrtNELVTVIKDUIGRcCUngx295jO5trfIJ41Q4r8MKC1F0qNI3CgcTK2O3i45rwj68e05FEPMX4NWVCo2TopAi8dpz9px2x6APiPG39bUbxHrKvv4DQHkRLeI1vI+0cYAifOK7Eheh6UAxDW5Yml3VWc0yEB18lzYGuDaqquCFevAL7nzYd30jBpGKn5of6WIW2HoxpEzqRAGfC52sOJShCsiA7QnM3bM/UnBhnhmGuFCsq/7P4rGn0oTh1ntnTC9iL3/wvuDVppZmZLQ4GHWuoew==
 
Back
Top