<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel>
<title>natbox.io blog</title><link>https://natbox.io/blog</link><description>Tutorials, guides and news from natbox.io, small Linux servers from $1 a month.</description><language>en</language><atom:link href="https://natbox.io/blog/feed.xml" rel="self" type="application/rss+xml"/>
<item><title>Keep commands running after you disconnect, with tmux</title><link>https://natbox.io/blog/keep-commands-running-with-tmux</link><guid>https://natbox.io/blog/keep-commands-running-with-tmux</guid><pubDate>Thu, 05 Nov 2026 06:00:00 +0000</pubDate><category>Tutorial</category><description>Use tmux on your Linux server so long downloads, backups and scripts keep running when SSH drops or you close your laptop. Step by step, with screenshots.</description><enclosure url="https://natbox.io/assets/blog/keep-commands-running-with-tmux/cover.png" length="132254" type="image/png"/><content:encoded><![CDATA[<img class="post-cover" src="https://natbox.io/assets/blog/keep-commands-running-with-tmux/cover.png" alt="" width="1200" height="630">
    <p>You start a big download or a backup over SSH, your Wi-Fi drops, and the command dies with your connection. <strong>tmux</strong> fixes that: it keeps a terminal running on the server, so you can disconnect, go home, and pick it up again later exactly where it was.</p>
    <p class="small">About 5 minutes. Works on any natbox plan. Commands for Debian and Ubuntu; on AlmaLinux use <code>dnf install -y tmux</code>, on Alpine <code>apk add tmux</code>.</p>

    <h2 id="install">1. Install tmux and start a session</h2>
    <p>Log in to your server (<code>ssh root@natbox.io -p YOUR_PORT</code>), install tmux and start a session with a name you will remember:</p>
<pre><code>apt install -y tmux
tmux new -s download</code></pre>
    <figure class="shot"><img src="https://natbox.io/assets/blog/keep-commands-running-with-tmux/1-new-session.png" alt="Installing tmux and starting a session called download" width="927" height="188" loading="lazy"></figure>

    <h2 id="run">2. Run your long command inside it</h2>
    <p>You are now inside tmux: it looks like a normal terminal, with a green bar at the bottom showing the session name. Start anything that takes a while. Here we download a 756 MB Debian image:</p>
    <figure class="shot"><img src="https://natbox.io/assets/blog/keep-commands-running-with-tmux/2-running.png" alt="A curl download running inside a tmux session called download, with the green tmux status bar at the bottom" width="997" height="298" loading="lazy"><figcaption>The green bar shows you are inside tmux: session <code>download</code>, window 0.</figcaption></figure>

    <h2 id="detach">3. Detach, and log out if you like</h2>
    <p>Press <kbd>Ctrl</kbd>+<kbd>B</kbd>, let go, then press <kbd>D</kbd>. You are back in your normal shell, and tmux tells you the session is still alive. <code>tmux ls</code> lists your sessions. You can now close the window, log out, or lose your connection: the command keeps running on the server.</p>
    <figure class="shot"><img src="https://natbox.io/assets/blog/keep-commands-running-with-tmux/3-detach.png" alt="Detaching from tmux and listing sessions with tmux ls" width="788" height="254" loading="lazy"></figure>

    <h2 id="attach">4. Come back to it</h2>
    <p>Log in again, from any computer, and reattach:</p>
<pre><code>tmux attach -t download</code></pre>
    <p>Everything is where you left it. Our download had kept going and was at 94%:</p>
    <figure class="shot"><img src="https://natbox.io/assets/blog/keep-commands-running-with-tmux/4-reattach.png" alt="After reattaching, the download is at 94 percent" width="997" height="298" loading="lazy"></figure>
    <p>When the command has finished, type <code>exit</code> to close the session.</p>

    <h2 id="split">5. Bonus: two panes side by side</h2>
    <p>Inside tmux, <kbd>Ctrl</kbd>+<kbd>B</kbd> then <kbd>%</kbd> splits the window in two. Here the left pane follows an app's log with <code>journalctl -fu myapp</code> while the right pane checks memory and disk. <kbd>Ctrl</kbd>+<kbd>B</kbd> then an arrow key moves between panes.</p>
    <figure class="shot"><img src="https://natbox.io/assets/blog/keep-commands-running-with-tmux/5-split.png" alt="A tmux window split into two panes: an app log on the left, memory and disk checks on the right" width="1120" height="342" loading="lazy"></figure>

    <h2 id="keys">The keys you need</h2>
    <ul>
      <li><code>tmux new -s NAME</code>: start a session. <code>tmux ls</code>: list sessions. <code>tmux attach -t NAME</code>: go back in.</li>
      <li><kbd>Ctrl</kbd>+<kbd>B</kbd> then <kbd>D</kbd>: detach. <kbd>Ctrl</kbd>+<kbd>B</kbd> then <kbd>%</kbd> or <kbd>"</kbd>: split side by side or top and bottom.</li>
      <li><kbd>Ctrl</kbd>+<kbd>B</kbd> then <kbd>[</kbd>: scroll back with the arrow keys or Page Up; <kbd>Q</kbd> to stop scrolling.</li>
    </ul>

    <h2 id="when">tmux or a service?</h2>
    <p>tmux is for jobs you start by hand and want to watch: downloads, backups, updates, a game server console. Anything that should run all the time and start again after a reboot, such as a bot or a website, belongs in a systemd service instead: see <a href="https://natbox.io/guides/run-an-app">Keep an app running</a>. A tmux session does not survive a server restart.</p>
    <p>No server yet? <a href="https://natbox.io/free-vps-trial">Try one free for a month</a>.</p>
    <p class="callout tg-follow"><strong>Get new tutorials in Telegram.</strong> Follow <a href="https://t.me/natboxio">@natboxio</a>: every new post, plus short server tips.</p>]]></content:encoded></item>
<item><title>What&#x27;s new at natbox: Telegram bot, snapshots, keeping your trial and CaptchaBox</title><link>https://natbox.io/blog/whats-new-november-2026</link><guid>https://natbox.io/blog/whats-new-november-2026</guid><pubDate>Wed, 04 Nov 2026 06:00:00 +0000</pubDate><category>Update</category><description>New at natbox.io: manage servers from Telegram with @NatboxBot, take your own snapshots, keep your free trial server on a paid plan, PayPal from $1, and CaptchaBox.</description><enclosure url="https://natbox.io/assets/blog/whats-new-november-2026/cover.png" length="132970" type="image/png"/><content:encoded><![CDATA[<img class="post-cover" src="https://natbox.io/assets/blog/whats-new-november-2026/cover.png" alt="" width="1200" height="630">
    <p>A lot has changed in the client area over the last few days. Here is everything new, and where to find it.</p>

    <h2 id="telegram">Manage your servers from Telegram</h2>
    <p><a href="https://t.me/NatboxBot">@NatboxBot</a> lets you check and control your servers from Telegram. Link it from the <a href="https://my.natbox.io/telegram">Telegram page</a> in the client area (account menu, then <strong>Telegram</strong>). After that you can:</p>
    <ul>
      <li>see each server's status, SSH command, ports, IPv6 address, traffic and paid-until date;</li>
      <li>start, stop and restart a server (stop and restart ask you first);</li>
      <li>pay an unpaid invoice from your account credit, or open it on the website to pay another way;</li>
      <li>get notices for new invoices, payments, support replies, and when a server is set up or a trial is about to end.</li>
    </ul>
    <figure class="shot"><a href="https://t.me/NatboxBot"><img src="https://natbox.io/assets/blog/whats-new-november-2026/telegram.png" alt="@NatboxBot in Telegram: server status, SSH command, traffic, and Restart and Stop buttons" width="1280" height="720" loading="lazy"></a></figure>
    <p>The bot also has a small app (the <strong>Open app</strong> button) with the same features. You can even create an account in the bot. For safety the bot never shows passwords and cannot reinstall a server, and there are no payments inside Telegram.</p>

    <h2 id="snapshots">Snapshots you control</h2>
    <p>The new <strong>Snapshots</strong> tab on each server saves the server exactly as it is, for example before a big update, and lets you go back to it later. You can keep 1 snapshot on the free trial and the VPN plan, 2 on Nano, 3 on Box and Box CPU, and 5 on Box Plus. Snapshots use your server's disk space and are stored on the same machine, so keep your own off-site backups as well. The <a href="https://natbox.io/guides/backups">backups guide</a> shows how.</p>

    <h2 id="keep-trial">Keep your free trial server</h2>
    <p>If you like your free trial, you no longer need to start again on a new server. Open the trial in the client area and choose a paid plan to keep it, with all your files and settings. We also email you 7 days and 2 days before a trial ends, so it never ends by surprise.</p>

    <h2 id="paypal">PayPal from $1</h2>
    <p>You can now pay with PayPal from $1, so a single month of Nano or Box can be paid directly. Crypto payments start at $3, and account credit works for any amount. The VPN plan and burner servers have their own payment options, listed in the <a href="https://natbox.io/docs">docs</a>.</p>

    <h2 id="captchabox">CaptchaBox: a free captcha for your own sites</h2>
    <p><a href="https://captcha.natbox.io/">CaptchaBox</a> keeps bots out of your website's forms without image puzzles, cookies or Google. Visitors' browsers solve a small puzzle in the background, and your server checks the answer. It is free for 10,000 checks a month, and switching from reCAPTCHA is easy because the server check uses the same answer format. We use it on our own sign-in and sign-up pages.</p>

    <figure class="shot"><a href="https://captcha.natbox.io/"><img src="https://natbox.io/assets/video/captchabox-ad-poster.png" alt="CaptchaBox: a free captcha with no puzzles and no cookies" width="1280" height="720" loading="lazy"></a><figcaption>Watch CaptchaBox in one minute on <a href="https://captcha.natbox.io/">captcha.natbox.io</a>.</figcaption></figure>

    <h2 id="next">What's next</h2>
    <p>Follow this blog for tutorials and news, or subscribe with the <a href="https://natbox.io/blog/feed.xml">RSS feed</a>. You can also watch our <a href="https://natbox.io/video">videos</a>. Questions or ideas: <a href="https://my.natbox.io/tickets/create">open a ticket</a>.</p>
    <p class="callout tg-follow"><strong>Get new tutorials in Telegram.</strong> Follow <a href="https://t.me/natboxio">@natboxio</a>: every new post, plus short server tips.</p>]]></content:encoded></item>
<item><title>Welcome to the natbox blog, and our new video library</title><link>https://natbox.io/blog/welcome-and-videos</link><guid>https://natbox.io/blog/welcome-and-videos</guid><pubDate>Wed, 04 Nov 2026 06:00:00 +0000</pubDate><category>Announcement</category><description>natbox.io now has a blog for tutorials, guides and news, and a video library with tutorials for your first server and for hosting a Discord bot.</description><enclosure url="https://natbox.io/assets/blog/welcome-and-videos/cover.png" length="132383" type="image/png"/><content:encoded><![CDATA[<img class="post-cover" src="https://natbox.io/assets/blog/welcome-and-videos/cover.png" alt="" width="1200" height="630">
    <p>natbox runs small Linux servers with root over SSH, your own block of IPv4 ports and a routed /80 of IPv6, from $1.00 a month. This blog is where we will post step-by-step tutorials, longer guides, and news when something changes on our side.</p>

    <h2 id="what">What you will find here</h2>
    <ul>
      <li><strong>Tutorials:</strong> one task from start to finish, with every command, written for a natbox server but useful on any Linux VPS.</li>
      <li><strong>Guides:</strong> the background to the tutorials, such as how NAT ports and IPv6 work, and how to choose a plan.</li>
      <li><strong>Announcements and updates:</strong> new features, changes to plans, and anything that affects your server.</li>
    </ul>
    <p>Our reference guides stay in <a href="https://natbox.io/guides">Guides</a>, and the basics of your account are in the <a href="https://natbox.io/docs">docs</a>. Blog posts link to them rather than repeat them.</p>

    <h2 id="videos">New: videos</h2>
    <p>We have also put all our videos on one page: <a href="https://natbox.io/video">natbox.io/video</a>. They play from our own server, with no YouTube embed and no cookies, and the longer ones have English captions.</p>
    <figure class="shot"><a href="https://natbox.io/video#first-server"><img src="https://natbox.io/assets/video/natbox-tutorial-first-server-poster.png" alt="Video thumbnail: Free Linux server plus SSH in 2 minutes" width="1280" height="720" loading="lazy"></a><figcaption>Our first-server tutorial. Watch it on the <a href="https://natbox.io/video#first-server">video page</a>.</figcaption></figure>
    <ul>
      <li><a href="https://natbox.io/video#first-server">Get a free server and log in over SSH</a> (2:10): start a free trial, log in, change your password, and see how your ports and IPv6 work.</li>
      <li><a href="https://natbox.io/video#discord-bot">Host a Discord bot 24/7</a> (1:39): install a bot, keep its token safe, and run it as a systemd service that restarts by itself.</li>
      <li><a href="https://natbox.io/video#shorts">Three Shorts</a> of under 35 seconds, including <a href="https://natbox.io/nat-vps">what a NAT VPS is</a>.</li>
    </ul>

    <h2 id="follow">Follow along</h2>
    <p>Add <a href="https://natbox.io/blog/feed.xml">natbox.io/blog/feed.xml</a> to your feed reader, or follow us on <a href="https://x.com/natboxio">X</a> and <a href="https://www.youtube.com/@natboxio">YouTube</a>. If there is a tutorial you would like to see, <a href="https://my.natbox.io/tickets/create">open a ticket</a> or email support@natbox.io.</p>
    <p>New to natbox? <a href="https://natbox.io/free-vps-trial">Try a server free for a month</a>.</p>
    <p class="callout tg-follow"><strong>Get new tutorials in Telegram.</strong> Follow <a href="https://t.me/natboxio">@natboxio</a>: every new post, plus short server tips.</p>]]></content:encoded></item>
</channel></rss>
