Question
Permission Denied (Pubkey) whilst deploying Terragraph
- Posted on May 13, 2023
- Ubuntu 18.04
Asked by 1d6ce141ab5444dfb1ea2dd29cf4b1
Good afternoon!
We’re currently attempting to deploy Terragraph on a node. We keep getting the following error when running the initial config file.
root@terragraph-01:~# root@terragraph-01:~# ./nms install -f config.yml
root@FQDN: Permission denied (publickey).
Here is our /etc/hosts
127.0.0.1 localhost
PublicIP terragraph-01
PublicIP FQDN
I’ve blocked out our FQDN however it is pingable and confirmed to be the same box we’re running the script on. How can we get it to force it to use the same credentials that are already being used? We’re logged into root using a key on my Laptop.
Many thanks in advance for your help!
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Get our biweekly newsletter
Sign up for Infrastructure as a Newsletter.
Hollie's Hub for Good
Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.
Become a contributor
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Hi there,
As you are running the the installer locally on the Droplet and it is trying to make a loopback SSH connection to the same Droplet locally, what you could do is to generate a new SSH key on the Droplet using the
ssh-keygencommand, and then add the public SSH key to the~/.ssh/authorized_keysfile:That way, you will be able to SSH to the Droplet itself allowing the installer to make that loopback SSH connection.
Let me know how it goes!
Best,
Bobby
Hello @1d6ce141ab5444dfb1ea2dd29cf4b1
You can ensure that the ssh public key is present in the ssh authorized_keys file on the node. This will resolve the ```` Permission denied (public key)` error.
If the issue persists, please consult the authentication log for more details by running:
For more information on how to set up SSH keys on DigitalOcean, please refer to this documentation.
Hope that this helps!