VeilNet Portal Configuration #
Once your VeilNet Portal is deployed, you may want to customize its behavior or manage its settings. Most Portal configuration is done via environment variables passed at container startup, either through docker run or in your docker-compose.yaml.
This guide outlines the available configuration options and how to adjust them safely.
| Variable | Description | Example |
|---|---|---|
VEILNET_ANCHOR_NAME | Display name of your portal in the Console | my-home-portal |
VEILNET_DOMAIN_NAME | Domain name associated with the portal (must match Console config) | merlion |
VEILNET_REGION | Region this portal belongs to (must match selected region) | sg / us / uk / au |
VEILNET_ANCHOR_TOKEN | Secret token generated by Console for authentication | (auto-generated) |
VEILNET_GUARDIAN_URL | URL of the VeilNet coordination server | https://guardian.veilnet.org |
PUBLIC | Whether this portal is public or private (true or false) | true |
⚠️ Important: These values must match what’s in your downloaded manifest from the Console. Manual modification may invalidate your Portal’s signature.
Updating Portal Configuration #
If you need to change any of these values:
Docker: Stop and remove the running container, then re-run it with updated values.
Docker Compose: Edit
docker-compose.yamland run:
docker compose down
docker compose up -d
⚠️ Region Mismatch Warning #
When configuring your VeilNet Portal, it is critical that the VEILNET_REGION environment variable matches the actual geographic region where the Portal is hosted.
For example:
If you’re hosting a Portal on a server physically located in the UK, you must set region as UK.
🚫 We do NOT collect your location #
VeilNet does not track, store, or process any user or server location data.
Instead, regional validation is performed indirectly through standard metadata headers inserted by Cloudflare during HTTPS requests to the Guardian service. These headers reflect the approximate server origin only at the infrastructure level and are never stored, analyzed, or linked to your account.
This ensures:
No user-level geolocation
No IP tracking by VeilNet
100% privacy-preserving enforcement
Why it matters: #
Incorrect region settings may result in:
Traffic being routed inefficiently
Portals failing to link with domains in that region
Performance penalties or disconnections
✅ Always configure VEILNET_REGION according to the actual location of your server to ensure smooth operation and proper domain assignment — without ever compromising your privacy.
