<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Home-Server on Linux Café</title>
    <link>https://mrtomlinux.org/tags/home-server/</link>
    <description>Recent content in Home-Server on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 16 Sep 2026 08:51:00 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/home-server/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>I lost SSH access to my home server after accidentally setting /home/user to 777 – how I restored it with a live USB</title>
      <link>https://mrtomlinux.org/post/2026-09-16-i-lost-ssh-access-to-my-home-server-after-acc/</link>
      <pubDate>Wed, 16 Sep 2026 08:51:00 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-09-16-i-lost-ssh-access-to-my-home-server-after-acc/</guid>
      <description>&lt;p&gt;I hit a wall yesterday when I accidentally set &lt;code&gt;/home/user&lt;/code&gt; to 777 and lost SSH access.&lt;br&gt;&#xA;The server was a 2026‑era Debian‑based homebox running systemd‑managed services.&lt;br&gt;&#xA;SSH refuses to log in if any file under the user’s home directory is writable by others, so the key‑based login failed immediately.&lt;br&gt;&#xA;The only way to fix it was to boot from a live USB, mount the root filesystem, and restore the correct ownership and permissions.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
