Network requirements
{/* notion-sync: page_id=1df1928df74d80d6b4eec3ba8028c32c /} {/ Notion is the source of truth: https://app.notion.com/p/1df1928df74d80d6b4eec3ba8028c32c — re-sync from Notion before treating this file as authoritative. */}
Requirements when installing a Welotec (or equivalent IPC) on the customer network to run Roasthubs:
- A static IP address for the Linux host (so the instance can be reached on the local network).
- Inbound and outbound UDP ports 443 and 7844 (authenticated remote overlay). This overlay is replacing the previous VPN path for private access. New installs should use the current overlay only.
- Outbound HTTPS (TCP 443) so the host can pull application images and verify image signatures at deploy time.
We also prefer a static IP so the instance is reachable on the LAN. If there is no external (WAN) connection, there is no loss of on-site product functionality — roasting and control on the local network do not depend on remote access, image pulls, or the public internet. External connectivity is for remote access, updates, and signature verification. Please reserve an address and share it with Roasthubs before install.
LAN impact / shared-network behaviour (CRA Annex I §9)
Roasthubs applies rate limiting but only on incoming traffic. There is no guarantee that the edge can be isolated on the customer LAN unless the client provides a firewall and isolates the device themselves. This is a documented limitation — not an outbound rate-limit claim and not a client firewall SLA.
Host firewall posture: the edge host uses a default-deny inbound firewall — only services required for the product are allowed; other inbound traffic is refused. Management and metrics interfaces are not left open on the general LAN by default. Customer-side LAN isolation remains a separate residual — do not treat the host firewall as a client firewall SLA.
Custom hostname (summary)
For a customer-facing hostname, Roasthubs configures an authenticated tunnel and a proxied DNS name. If you need the app on a non-Roasthubs domain, provide DNS records as instructed during install (typically a CNAME plus any validation TXT Cloudflare requires for a custom hostname). Pointing customers only at a raw tunnel identifier is not supported.
Network design notes
Desired access patterns (plan with Roasthubs at install):
- Operator access to the application on the LAN (and via the authenticated remote overlay when WAN is available)
- PLC / OT network access where the site uses plant equipment with Roasthubs
- Prefer separate plant and management paths where the customer network allows — full LAN isolation remains a customer firewall responsibility
Share the planned addressing with Roasthubs before install.