TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Server access – There must be a better way

1 pointsby campervansabout 1 year ago
So I&#x27;ve setup a couple of servers on Hetzner. One in particular selfhosts Sentry, Grafana,(Prometheus and Loki).<p>My SSH key is provisioned...<p>I need help with DevOps... but there seems to be no simple way to provision another SSH key.<p>Support suggested this:<p>&quot;1. Go to the Rescue section of your server, but instead of the (reset root password) button, click the Activate Rescue &amp; Reset button. Your server will then boot into the rescue system. 2. Connect to your server via SSH using the Rescue credentials. 3. execute the following commands in Rescue: mount &#x2F;dev&#x2F;sda1 &#x2F;mnt chroot-prepare &#x2F;mnt chroot &#x2F;mnt From this point you can now navigate through the file structure of your Cloud Servers primary disc. SSH keys for the root user are stored in &#x2F;root&#x2F;.ssh&#x2F;authorized_keys.<p>4. Restart your server using the reboot command and log in using the new SSH key.&quot;<p>But seems pretty scary process on a server running multiple application.<p>There must be a better way!

2 comments

CoolColdabout 1 year ago
Seems like system administration stuff to add more keys, not yaml&#x2F;devops engineering.<p>If you rephrase your question and what prevents you to just add keys after provisioning finishes, I&#x27;ll try to help
warrenmabout 1 year ago
You already have your primary ssh key on each server?<p>Why not just push any other keys &quot;traditionally&quot; using scp?