monday 8am and im locked out of a new ec2 instance

lol this thread is gold

try turning off the BIOS first, fixed it for me good luck man!

yeahhh this. so much this fingers crossed 🤞

hmmm exact same thing happened to my gaming rig last month

ehh idk man that sounds like bad advice tbh idk maybe im wrong lol

oof have u checked ur linux settings? mine were reset after an update

yeahhh honestly just reset the DNS and save yourself the pain

hmmmm

hmmmm not sure about that everyone keeps saying this but nobody posts proof just my 2 cents

so annoyed rn ok this thread just saved my weekend

oh also i come back to this thread every week just for teh drama. make a backup before u touch the update, learned that the hard way

is authentication even worth bothernig with or should i just leave it ??

hmmmm ok ok this thread just saved my weekend. dumb question but how do i even check teh cable

hmmm came here to say exactly this. dumb question but how do i even check the fan curve

@leon.dalton84 works on paper, not in real life

been there man check the server log while you try to connect: sudo journalctl -u ssh -f (or -u sshd on RHEL family, /var/log/auth.log on older Debian/Ubuntu). It says exactly why: bad ownership, wrong user, key type not accepted.

lol same thing happened to me same issue here on my moms pc. glad im not the only one

make a backup before u touch the driver, learned that the hard way

xD