Hey guys.

I'm trying to make the connection between my system and Sourcehut. I created my Ssh key and added pub key to the Sourcehut. Added the private key with the ssh-add ~/.ssh/id_ed25519 code after the "eval" thing.

Whenever I try ssh git@sr.ht, it asks for password. I do not know what password it is and I'm entering my passphrase but it says permission denied.

On Github side, I managed everything without problem tho. Any hints?

EDIT: I removed Git and SSH keys completely. Reinstalled Git again. Followed the instructions step by step for the SSH keys and it worked this time. I have no idea what I did different this time but it works now after 3 hours of hell.. I suspect that I made a typo in config file in SSH directory. Thanks for comments guys! I love you all!

While I consider this resolved at time of posting, this is one of my weirder, more unexpected tech issues I've run into and I thought y'all might enjoy it.

I'd been having issues with my (Ubuntu) server where its services were unavailable, I couldn't SSH in, and USB devices plugged in after the issues started weren't connecting (mouse LED would light up, couldn't toggle keyboard locks or interface computer with the devices). These issues were becoming a near daily occurrence.

So after the most recent incident I decided to watch it boot. After grub, it would just hang at a black screen. So I opted for the recovery mode and after waiting some minutes for services to time out, I was given a terminal and used that to check my devices, sensors, etc and all were reading fine.

Frustrated, I started reviewing what else could have possibly changed with my setup, and I found that change in my hand. I use my server's front USBs as a low current charger and had recently got a new vape battery that was charging at that moment.

I unplugged the battery, rebooted, everything was fine. Plugged the battery in, everything locked up again immediately.

I had been using a spare cable, it had data wired. Swapping for the included power only cable, and no issues.

While I'm curious as to what exactly is happening and why, I'm satisfied enough concluding it is a cheap vape (I mean, I'm having to charge the sucker near daily after all) that is transmitting junk over data and the OS doesn't handle it appropriately. I'll pull logs or do another couple tests if other folks are curious as well though.

Oh, and the battery is a Bear Rootz Sol. Come to think of it, my other worst battery at holding a charge was also a Bear Rootz.