OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
network medium very-common DISPUTE

Reach a dev server, Samba share or other service on an Omarchy machine from the LAN

omarchyufwdesktoplaptop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

Re-read install/config/firewall.sh on 4.0.4-1: default deny incoming, LocalSend 53317 tcp and udp, two udp/53 Docker DNS rules, ufw-docker install, and ufw enabled at boot, as the cause says. /etc/ufw/applications.d/ufw-fileserver defines CIFS as 137,138/udp|139,445/tcp. omarchy-setup-security-sshd installs openssh, runs systemctl enable --now sshd.service, adds ufw limit 22/tcp, requires an authorized key, and writes /etc/ssh/sshd_config.d/10-omarchy-hardening.conf with PasswordAuthentication no, which the fix describes correctly. One gap remains: the 'keep password logins' alternative only adds a ufw rule. On a stock install openssh is present only as a dependency of gcr and nothing enables sshd.service, so that rule alone opens a port with no server behind it. The fix now enables sshd in that branch. Everything else is kept. Status stays corrected, so the previous audit's sshd findings remain on record. Not exercised. No firewall change was made on this machine.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.
RISK

A rule written as sudo ufw allow 3000 with no from opens the port to every network you join, including public Wi-Fi, and over IPv6 as well. Scope rules to the LAN subnet. The subnet differs between networks, so a rule for 192.168.1.0/24 does nothing at a network that uses 10.0.0.0/24.

Symptom

A service running on the Omarchy machine works on localhost but times out from every other device. Examples: npm run dev -- --host or python -m http.server opened from a phone, a Samba share for a Windows PC, Syncthing, a game server, Sunshine. There is no connection refused, just a hang. The same project worked on another distro. ss -tlnp shows the service listening on 0.0.0.0 or *.

Cause

Omarchy's installer runs ufw default deny incoming and enables ufw at boot. The only inbound rules it adds are LocalSend's port 53317 and udp/53 for Docker containers to the host. Any other inbound connection is dropped silently, which produces a timeout and not a refusal. omarchy-setup-security-sshd opens port 22 for SSH with ufw limit 22/tcp, but nothing opens ports for other services. Docker-published ports go through a separate DOCKER-USER chain managed by ufw-docker, so these INPUT rules do not govern them (see docker-published-ports-bypass-ufw).

Fix

Check the firewall and confirm the service listens on all addresses, not only 127.0.0.1:


sudo ufw status verbose
ss -tlnp | grep 3000

Find your LAN subnet and allow the port from the LAN only:


ip -4 route | grep -v default          # e.g. 192.168.1.0/24 dev wlp2s0
sudo ufw allow from 192.168.1.0/24 to any port 3000 proto tcp comment 'dev server'

A Samba server, using ufw's bundled CIFS profile (137,138/udp and 139,445/tcp):


sudo ufw allow from 192.168.1.0/24 to any app CIFS

SSH on Omarchy 4: the helper installs openssh, enables sshd, adds ufw limit 22/tcp, asks for a public key (from GitHub or pasted, or pass --key=), and then turns password logins off in /etc/ssh/sshd_config.d/10-omarchy-hardening.conf:


omarchy-setup-security-sshd

If you want password logins kept, start sshd and open the port yourself instead. A stock install has the openssh package but does not enable its server:


sudo systemctl enable --now sshd.service
sudo ufw limit from 192.168.1.0/24 to any port 22 proto tcp comment 'sshd lan'

Remove a rule when you are done:


sudo ufw status numbered
sudo ufw delete <number>

Plain Arch has no firewall enabled by default, so this applies only where ufw or firewalld was turned on.

Verify

From another device on the LAN, curl -v http://<omarchy-ip>:3000/ (or opening the share) connects. sudo ufw status numbered lists the rule scoped to your subnet.

Sources

omarchy-ufw-blocks-incoming-lan-services