Enable SSH Access on Artix Linux: A Runit Service Guide

Problem: SSH Won't Start After Installation

If you've installed OpenSSH on Artix Linux but can't connect remotely, the issue is likely that the sshd service isn't running. Unlike systemd-based systems that auto-enable many services, Artix's runit init system requires explicit service activation.

Prerequisites

• Artix Linux with runit as the init system (verify with ps -p 1 -o comm=, should return runit)
• Root or sudo access
• OpenSSH installed (sudo pacman -S openssh)

Procedure: Enable and Start the SSH Service

1. Navigate to the service directory

   cd /etc/sv

   Runit stores service definitions in /etc/sv. Verify sshd exists:

   ls -la /etc/sv/sshd

2. Enable the service

   sudo ln -s /etc/sv/sshd /etc/runit/supervise/sshd

   This creates the supervision link. Runit's three-stage model (boot, default, shutdown) uses symlinks in /etc/runit/supervise/ to determine which services to run.

3. Start the service

   sudo sv up sshd

   Use sv to control services: up starts, down stops, status checks state.

4. Verify the service is running

   sv status /etc/sv/sshd

   Expected output: /etc/sv/sshd up

Expected Checks

• Service status: sv status /etc/sv/sshd should show up
• Port listening: ss -tlnp | grep :22 should show sshd listening
• Process verification: pgrep -l sshd should list running sshd processes

Configuring SSH for Remote Access

Edit the SSH daemon configuration:

sudo nano /etc/ssh/sshd_config

Key settings to verify:

• Port 22 (or change to custom port)
• PermitRootLogin no (security best practice)
• PasswordAuthentication yes (or use key-based auth)

After configuration changes, restart the service:

sudo sv down sshd && sudo sv up sshd

Firewall Considerations

If using iptables or nftables, ensure port 22 is open:

sudo iptables -A INPUT -p tcp --dport 22 -j ACCEPT

Recovery Options

• Stop the service: sudo sv down sshd
• Disable on boot: sudo rm /etc/runit/supervise/sshd
• Check logs: sudo journalctl -u sshd (if using a logging service) or check /var/log/ for sshd logs

Verification Limitations

Note that some SSH implementations may require additional configuration for key exchange algorithms or cipher support. If connections fail after service activation, check client compatibility and review /etc/ssh/sshd_config for deprecated options.