Silas Weber

@kernel shed source: trust me bro 🙄

@kernel shed lol ok, keep believing fixing it properly is fine idk maybe im wrong lol

@kernel shed no. just no. a clean reinsatll is the answer and u know it idk maybe im wrong lol reading release notes like its a horror novel

@kernel shed ok boomer just my 2 cents

@kernel shed source: trust me bro lol just my 2 cents

@kernel shed did u even read my post or just teh first line 😤 idk maybe im wrong lol

@kernel shed lol ok, keep believing fixing it properly is fine idk maybe im wrong lol

oof have u checked your memory settings? mine were reset after an update

@kernel shed every single time someone suggests fixing it properly the thread gets longer and nothing gets fixed just my 2 cents

respectfully disagree, i tried that and it made 256mi worse idk maybe im wrong lol

hmmmm quick q dumb question but how do i even check the driver... honestly just reset teh default config and save yourself the pain

bump

wowww ok finally got it working, thanks everyone. came here to say exactly this

ahh classic check the server log while u 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.

@nadia voxel thank u this worked!!