Allowed networks and TLS
Weik.io 2026.2The hub can admit only the address ranges you list. Its one published port accepts only TLS 1.2 and 1.3 with AEAD cipher suites.
On this page
The hub publishes only TCP port 443. To keep the hub off the open internet, list the networks it admits on that port, such as your offices and your pipelines’ runners. Your agents’ hosts go on the list too.
Limit access to your networks#
The list is a setting, so changing it needs no file edit and no restart:
$ weikio settings set --allowed-networks 203.0.113.7/32,198.51.100.0/24Write each entry as a range with its prefix length, so a single address is 203.0.113.7/32, or 2001:db8::7/128 in IPv6.
To keep the list in Git, set allowedNetworks in the settings document and apply it with weikio apply -f. In the admin UI, Settings › Platform › Installation shows the list.
weikio settings set --no-allowed-networks removes the list. With no list every address reaches the hub, as it does after install.
Only callers from the networks on the list can use the hub:
- The admin UI
- The API
- The
weikioCLI - Sign-in
- The agents’ links
- The agents’ telemetry
A caller outside the list gets 403 Forbidden. On the agents’ telemetry it gets 503 Service Unavailable instead, so the agent keeps its telemetry to send later. Each server applies a change within seconds. If a server hasn’t applied it within two minutes, Settings › Operations › Health shows it.
The list doesn’t apply to /readyz/node and /healthz on the admin UI’s name, so the load balancer’s check and your check from outside keep working. It doesn’t apply to a certificate authority’s check of a name either, so certificates renew.
Gateway hostnames don’t use this list. Each gateway has its own --networks, as Gateways and hostnames describes.
Keep yourself in#
You can’t make a change that shuts out the address you send it from. The error message shows that address. weikio settings get and the Settings page show the address you reach Weik.io from. A private address there, such as 10.0.0.5, may belong to Docker or to a load balancer and not to your computer.
On one server, Docker passes every IPv6 caller and every program on the server itself to the hub from one of the server’s addresses, 172.16.250.128 by default. A list with that address lets all of them in.
- On one server, list the IPv4 addresses of your computers and make the change from another computer over IPv4.
- On several servers, set
WEIKIO_BALANCER_ADDRESSESin each server’s.envbefore you set allowed networks, so the hub sees each caller’s address through the PROXY protocol.
While the list has the server’s own address, both the reply to each change and Settings › Operations › Health warn about it.
Agents on the list#
An agent connects and sends its telemetry from the address of its host, so that address goes on the list. Weik.io accepts a change that leaves an agent outside the list, but the reply and Settings › Operations › Health show the agent and the address it sends telemetry from.
An agent outside the list keeps its telemetry on its disk while it can’t reach the hub, and sends it with the original times once the list has its address.
Behind a CDN, the list applies to the caller’s address that the CDN passes on. Put the CDN’s ranges in WEIKIO_EDGE_RANGES and not on the list, as Behind a CDN describes.
Locked out#
If you’re locked out, run this on any of the hub’s servers, in that server’s stack folder:
$ docker compose run --rm infra weikio-backend networks add <your address>/32 --reason "<why>"You don’t need to sign in to run it. It prints The hub's allowed networks are now <ranges>. Each server applies them within seconds. To remove the whole list instead, run networks clear. The audit trail records both as an AllowedNetworksChanged entry that has the settings before and after.
TLS on port 443#
The terminator handles TLS for the hub’s two names, as the gateway does for every gateway hostname. Both accept only TLS 1.2 and 1.3, and on TLS 1.2 they accept only AEAD suites, which means AES-GCM or ChaCha20. A client that supports only CBC suites on TLS 1.2, such as Safari 8 on iOS 8 or OS X 10.10, can’t connect. weikio-backend doctor reaches the public address the way a browser does and checks the reply and the certificate in its public address row. It uses only TLS 1.2 or 1.3.
You don’t place certificate files. As Certificates describes, Weik.io obtains and renews every certificate from a certificate authority:
- Let’s Encrypt
- Your ACME authority
- Weik.io’s own certificate authority
The message server publishes no port, because every agent reaches it over the WebSocket link on port 443. On a hub of several servers, the links between the servers use TLS too.
The session cookie#
The admin UI is served from the same address as the API, so it needs no CORS and no cross-site cookie. Its session cookie has the __Host- prefix.
Sign-in rate limit#
The terminator accepts a burst of 5 sign-in attempts and then 10 a minute per caller address.