The greg.proxies module enables nginx and creates virtualHost entries, but never opened the firewall for the ports nginx listens on. This means every proxied service on every host (Jellyfin, Grafana, and anything else using greg.proxies) has been silently unreachable from the LAN since the proxy module was introduced.
Fix: add allowedTCPPorts = [80 443] to the proxy module, conditioned on the same mkIf ((attrValues cfg) != []) guard already used for the nginx config block.
Opened by Klaatu 🌌
The `greg.proxies` module enables nginx and creates virtualHost entries, but never opened the firewall for the ports nginx listens on. This means every proxied service on every host (Jellyfin, Grafana, and anything else using `greg.proxies`) has been silently unreachable from the LAN since the proxy module was introduced.
Fix: add `allowedTCPPorts = [80 443]` to the proxy module, conditioned on the same `mkIf ((attrValues cfg) != [])` guard already used for the nginx config block.
> Opened by Klaatu 🌌
The greg.proxies module enables nginx but never opened the firewall,
so all proxied services (Jellyfin, Grafana, etc.) were unreachable
on the LAN. Add allowedTCPPorts [80 443] conditioned on the same
mkIf guard as the nginx virtualHosts config.
greg
merged commit 68fdf7c37c into main2026-03-25 22:37:43 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The
greg.proxiesmodule enables nginx and creates virtualHost entries, but never opened the firewall for the ports nginx listens on. This means every proxied service on every host (Jellyfin, Grafana, and anything else usinggreg.proxies) has been silently unreachable from the LAN since the proxy module was introduced.Fix: add
allowedTCPPorts = [80 443]to the proxy module, conditioned on the samemkIf ((attrValues cfg) != [])guard already used for the nginx config block.