sec: trusted interface does not require openfirewall ports #2
Labels
No labels
area/documentation
area/networking
bug
feature
host
ame
host
arashi
host
kariru
host
kaze
host
sakura
hosts
all
host
sora
host
tsuki
host
tsuru
host
yuki
priority
1
priority
2
priority
3
status
blocked
status
needs-research
styling
treewide
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: notohh/snowflake#2
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
ef82734585/hosts/sora/services/uptimekuma.nix (L2)
since you're binding to
100.87.54.48
there's really no reason to open the firewall if your reverse proxy has a tailscale interface on it or your desktop/laptop has tailscale interface.tailscale is an overlay/flat-layer-2 network. the only firewalling is using the acl's
in traefik you would just set the service lb to 100.87.54.48 and call it good.
of course leaving it will not hurt anything, but it's just extra config that's likely not needed.
uptime-kuma isnt proxied on sora just yet, so this does need to stay open for the time being. will close once its proxied though.
when i close 4000, i actually cant access the dashboard for
uptime-kuma
from tailscale, but can accessstatus.notohh.dev
.closing this now, reopening 4000 since i cant seem to access the dashboard from anywhere when its closed.
status.notohh.dev
is only a frontend and cant actually control anything, which is why i need to be able to access the dashboard