Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Config Stuck on Registering SSH #436

Open
kewtz opened this issue Jan 17, 2024 · 2 comments
Open

Config Stuck on Registering SSH #436

kewtz opened this issue Jan 17, 2024 · 2 comments

Comments

@kewtz
Copy link

kewtz commented Jan 17, 2024 •
edited

Have 2 fresh pi-hole installs via Proxmox containers, service is running on both, gravity-sync installed on both.

» Gravity Sync Remote Host Settings

› Remote Pi-hole host address

? IP: 192.168.0.211

✓ Saving 192.168.0.211 host to gravity-sync.conf

› Remote Pi-hole host username

? User: root

✓ Saving root@192.168.0.211 to gravity-sync.conf

» Gravity Sync SSH Key Settings

✓ Generating new SSH key

✓ Moving private key to /etc/gravity-sync/gravity-sync.rsa

✓ Moving public key to /etc/gravity-sync/gravity-sync.rsa.pub

✓ Loading gravity-sync.conf

› Registering SSH key to 192.168.0.211

/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/etc/gravity-sync/gravity-sync.rsa.pub"

root@192.168.0.211's password: 

Permission denied, please try again.

I'm stuck here, I know the root password...but the config seems to be expecting something else? Is it looking for the public key of the other machine?
@kevinreck
Copy link

kevinreck commented Feb 1, 2024 •
edited

Kewtz - Did you check that your second node's (192.168.0.211) /etc/ssh/sshd_config has both of these settings to allow the root user to log in?

PasswordAuthentication yes
PermitRootLogin yes

Make sure to enable this setting too
PubkeyAuthentication yes

Reminder to restart the ssh daemon. You can remove the PasswordAuthentication afterwards

@kewtz
Copy link
Author

kewtz commented Feb 11, 2024

I did verify this on the .211 node.
I also reset the root password on both to ensure that wasn't the problem, I continue to get permission denied.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kevinreck @kewtz