Applications

Published applications let users open a private web application at an address of its own, such as crm.apps.example.com, from any browser. Nothing is installed on the device: no desktop client, no browser extension. The user signs in at the Workplace once, and every request then travels through that user's own private connection to the application.

This suits contractors, partners, personal devices and phones, and any web application you want to reach from anywhere without exposing it to the internet. With restrictions, the application's pages carry a watermark, mask sensitive data and block copying, printing, downloads and uploads, in any browser. The address answers only signed-in users the application admits. Everyone else is sent to the sign-in, and an address nobody published answers There is no application at this address.

You publish applications under Network > Applications. Administrators manage them; users see the applications they may open in the Workplace.

How it works

  1. An administrator turns publishing on for the account and publishes an application: an address, a target such as http://10.1.2.3:8080, and the groups that may open it.
  2. The address points at the Netzilo reverse proxy through a wildcard DNS record for the application domain. On Netzilo Cloud that is *.netzilo.app, already in place. On a self-hosted server it is *.apps.example.com pointing at the server.
  3. A user opens https://crm.apps.example.com/. The reverse proxy has no session for that browser, so it sends the user to the Workplace. The Workplace signs the user in if needed, checks that the address is one the user may open, and hands the sign-in back to the application's address.
  4. The reverse proxy asks the management server to admit the user: first the application's groups, then the application's own posture checks. Admitted, it sets a session cookie for that address only. The Workplace dialog shows Logging in while the user's private connection comes up, then opens the application.
  5. From then on every request on that address goes through the user's tunnel: a virtual peer in the user's account, named vp-<n>-RPROXY, with that user's policies, routes and DNS. The target is reached through that tunnel and nowhere else, so the user reaches exactly what their policies allow.
  6. The application receives two headers naming the user, X-Netzilo-User-Id and X-Netzilo-User-Email, and the published address in X-Forwarded-Host. With Forward the user's credential on, it also receives the user's token as Authorization: Bearer. Redirects and cookies the application sets for its internal name are rewritten to the published address. The target's certificate is not verified, so self-signed and internal certificates work.
  7. A sign-in lasts 12 hours per address and is checked again with the management server every 10 minutes. A changed group or posture check, or a blocked user, takes effect within that interval. A change to the application itself takes effect within about 40 seconds. A sign-in token that management no longer accepts ends the session at once. After 60 minutes without traffic the tunnel stops and starts again on the next request, as the same peer.
  8. When the application has restrictions, the reverse proxy adds a small Netzilo script to each page it serves, and the script applies them in the page. Without restrictions nothing is added and pages pass through as the application sent them.

Published never means public. The application's groups decide who may open it. The user's policies decide whether their tunnel reaches the target. A user admitted to an application whose policies do not reach the target sees Access Failed, not the page.

Before you start

  • A wildcard DNS record. On Netzilo Cloud, *.netzilo.app already points at the reverse proxy. On a self-hosted server, create *.apps.example.com pointing at the server's public IP, using a domain other than the server's own.
  • A route and a policy to the target. The target's network must be a route distributed to a group the user is in, allowed by a policy from one of the user's groups. See Routes and Policies. Publishing adds no permissions of its own.
  • Posture checks in the right place. Requirements on the user's device go on the application itself and are judged at its door, see Posture checks on the application. Posture checks on the policies that reach the target are judged against the user's reverse-proxy peer, which is not a managed endpoint, see Posture checks for reverse-proxy peers.

Step 1: Allow published applications for the account

Go to Settings > Permissions and turn on Allow published applications.

The Permissions tab under Settings, with Allow published applications on and the application domain apps.example.com with the address 203.0.113.10 under Application domains

Under Application domains, add the domains you publish under, each with the address its wildcard record points at. On Netzilo Cloud add netzilo.app with the address that anything.netzilo.app resolves to. On a self-hosted server add the domain you gave the installer, with the server's public IP.

Click Verify on a row to check the DNS record. Management resolves a random name under the domain through public resolvers and reports whether the wildcard points to the reverse proxy, points elsewhere, or is missing. It is a check, not a gate: you can save a domain before its record exists.

Click Save Changes. Turning the switch on or off is recorded in Activity > Events.

While the switch is off nothing is published, and the Applications page says Publishing is turned off for this tenant, so these applications are not reachable. Existing applications keep their settings and come back when it is turned on again. A server upgraded to this release starts with the switch off. See Permissions.

Rules for application domains:

  • On Netzilo Cloud, and on any self-hosted server with more than one account, every published address must be a name under one of the account's application domains.
  • An application domain belongs to one account. A domain another account already uses, or a name under or above it, is refused. The shared Cloud domain netzilo.app is the exception every account adds.
  • Do not use the server's own domain, nor anything under netzilo.network. Names there are resolved inside every tunnel and would never reach the reverse proxy.

Step 2: Publish an application

Go to Network > Applications. The table lists each application's name, Address, Target, Groups and Posture Checks, with an Active switch per row. Filter by All, Active or Inactive and by group, or search by application, address, target or group.

The Applications page under Network, listing two published applications, Grafana at grafana.apps.example.com and LLM Gateway at llm.apps.example.com, with their targets, groups and the Add Application button

Click Add Application. The Create New Published Application dialog has four tabs: Application, Posture Checks, Restrictions and Name & Description.

The Create New Published Application dialog on the Application tab, with the tabs Application, Posture Checks, Restrictions and Name and Description, the address crm.apps.example.com marked Available, points to the Netzilo reverse proxy, the target http://10.1.2.3:8080, the group Employees, Send the address as Host header off, Forward the user's credential off and Enable Application on

FieldWhat to enter
AddressThe label of the address, with one of your application domains picked as suffix, for example crm and .apps.example.com. Choose Custom address in the picker to type a full hostname. No https://, no path. As you type, the check answers Available (with points to the gateway, but points elsewhere or no DNS record yet, none of which blocks saving), Unavailable when the address is already published by any account, Invalid, or Not under an application domain.
TargetWhere the reverse proxy forwards to, through the user's private connection: http:// or https://, a host name or IP address, an optional port, no path. A name is resolved by the user's tunnel, so an internal name works when the user's DNS settings resolve it. Loopback, link-local and cloud metadata addresses are refused.
GroupsWho may open the application. The user must be in one of these groups. Empty means nobody.
Send the address as Host headerOff by default: the target sees its own host name. Turn it on for applications that compare the Host header with the address they are published under.
Forward the user's credentialOff by default. On, the reverse proxy sends the signed-in user's token to the application as Authorization: Bearer, for applications that verify users with Netzilo themselves, such as a Netzilo AI Gateway, see Publish an AI Gateway. Leave it off for every other application: the token is the user's Netzilo credential.
Trusted ProxiesEmpty by default. The addresses of web proxies that forward their users to this application and name each user, as IP addresses or CIDR ranges separated by commas, for example 203.0.113.10, 198.51.100.0/24. See Through a web proxy. Leave it empty when no proxy forwards users here.
Enable ApplicationAn application that is off is kept but not served. Its address answers There is no application at this address.

Continue leads through the tabs in order: Posture Checks, then Restrictions, then Name & Description. Both middle tabs are optional; leave them empty and continue.

On Posture Checks you require something of the user's device.

The Posture Checks tab of the application dialog with one check, Require Netzilo workspace, described as The device runs the Netzilo Enterprise Workspace, and Posture Check Evaluation set to All

Click Browse Checks to attach existing checks, or New Posture Check to create one. Posture Check Evaluation decides whether All checks must pass (the default) or Any one is enough, as on a policy. Leave the tab empty for no device requirement. How the checks are judged is described under Posture checks on the application.

On Restrictions you protect the data the application shows: watermark, redaction, clipboard, printing, downloads, uploads and blocked addresses. See Restrictions.

On Name & Description, enter the Name of the Application, which the Workplace tile and the activity log show and which must be unique in the account, and an optional description. Click Add Application.

The Applications table shows the number of posture checks per row. A posture check that an application uses cannot be deleted while it is in use; the Posture Checks page lists the applications that use it.

An address is unique across the whole server, first come, first served. On Netzilo Cloud every account publishes under the shared netzilo.app, so choose distinctive labels such as grafana-acme.

A new address answers within a minute of saving. On a self-hosted server with Let's Encrypt, the certificate for the name is obtained on the first visit, which can take a few seconds.

Publishing, updating and unpublishing an application are recorded in Activity > Events as Application published, Published application updated and Application unpublished.

To change an application, click Edit (the pencil) on its row; to remove it, click the bin and confirm. Its address stops answering.

What users see

The Workplace shows every application the user may open as a tile under Applications, next to the bookmarks and shortcuts. Opening a tile goes to the application's address in a new tab.

The Workplace Applications section with five application tiles, among them the published application Corporate File Server(Published), each with an Online or Offline status

On the first open, and again after 12 hours, the user sees the Workplace's sign-in dialog. A user who is not signed in at the Workplace signs in there first and is brought back. The dialog shows Logging in while the user's private connection comes up, a few seconds, or 10 to 20 seconds the first time in an hour while the user's peer registers. Then the application opens.

The Workplace sign-in dialog with the Netzilo logo, a spinner, the heading Logging in and the text Please wait while we complete the login process

The dialog saysMeaning
Access Denied — Your account is not allowed to open the addressThe user is in none of the application's groups, or publishing is off for the account. Only an administrator can change this.
Access Denied — because posture check (name) failed. Reason: (reason)The user is admitted, but the device failed one of the application's posture checks. The reason names the failing rule, for example Peer is not using Netzilo Enterprise Workspace. See Posture checks on the application.
Additional Protection Required — the address requires the Netzilo browser extensionThe only thing standing between the user and the application is the Netzilo browser extension in this browser. The dialog offers to add it, or to connect an installed one to this server, and opens the application again once the extension answers.
Access Failed — the address took too long to answer or did not answerThe user is signed in and admitted, but the application could not be reached through the user's private connection. See Troubleshooting.
This sign-in is no longer valid. Open the application again.The sign-in link was older than 10 minutes or used twice. Opening the application again starts a fresh one.

A second application opened from the same browser needs no new sign-in. A bookmark to the application works: the cookie on the application's address carries the session, and the Workplace is only needed to sign in.

Signing out of the Workplace ends the Workplace session and, in the same browser, every published application's session of that user. The applications ask for a sign-in again at once. A session that is not signed out ends after 12 hours, or within 10 minutes of the user's login being revoked.

On an application with restrictions, the pages may carry a watermark and a gray border, show masked data and display a Netzilo notice when something is blocked, see In the browser.

Users with the Netzilo desktop client, and users on phones, use published applications the same way. The browser goes to the published address, and the reverse proxy carries the request.

Posture checks on the application

The posture checks chosen on the application are judged at the door: when the user signs in at the application's address, before a session exists. They apply to the device the browser runs on, which may or may not have the Netzilo client. This is different from the checks on policies, which are judged against the user's reverse-proxy peer once the session runs, see Posture checks for reverse-proxy peers.

What the door knows about the device. The Workplace's sign-in dialog collects the evidence and hands it to the application's address with the sign-in. Management judges it; the reverse proxy holds no posture logic of its own.

EvidenceWhere it comes fromRules it serves
Operating system and version, browser, public addressThe sign-in request: the browser's client hints and User-Agent, and the connection. Chrome and Edge report the real OS version. Firefox and Safari report macOS as 10.15 and Windows as 10.0.Operating System, Country & Region, Peer Network Range
The Netzilo browser extensionThe extension in this browser answers the Workplace page. When it has a gateway session, the sign-in names that session's device and management verifies it against the live session.Netzilo Extension
The Netzilo Enterprise BrowserThe browser identifies itself in its User-Agent; nothing is installed or asked. It also satisfies the Netzilo Extension rule.Enterprise Browser, Netzilo Extension
The device's own postureThe Netzilo client running on the device, asked by the Workplace page over its local connection, the same posture the client reports for its peer: firewall, antivirus, disk encryption, screen lock, OS updates, virtual device, device integrity, Enterprise Workspace, registry, file and process results. A Netzilo Workspace reports its own posture, including that it is the Workspace, whether or not it is registered as a peer.Endpoint Security Settings, Enterprise Workspace, Virtual Device, Device Integrity, Registry Key & Value, File & Folder, Running Processes

Without a Netzilo client on the device, the rules in the last row fail, as they do for any browser. The posture is what the device reports about itself, as a peer's posture is. The Netzilo Gateway rule never passes at the door; it is for policies that admit browser sessions of a gateway.

All or any. With all (the default) every chosen check must pass. With any one, a single passing check admits the user. A check is a group of rules, and every rule in a check must pass for the check to pass.

When it is judged. At every sign-in, that is on the first open and again after 12 hours, and whenever the Workplace sends the user through the sign-in again. A running session is re-checked with management every 10 minutes with the evidence of its sign-in, so a change to the application's checks or groups takes effect within that interval, while a change on the device itself is seen at the next sign-in.

What the user sees when a check fails is Access Denied with the check's name and the failing rule's reason. When the extension alone is missing, the dialog shows Additional Protection Required instead and offers to add or connect the extension, then tries again by itself. See What users see.

Activity. Every decision at the door is recorded under Activity > Events:

EventWhenCategory
Application access allowedA sign-in passed, once per sign-in. Re-checks of a running session are not recorded while it still passes.Access Control
Application access denied by postureA sign-in, or the re-check of a running session, failed a posture check. The event names the check and the reason.Policy Violation
Application access denied: not admittedA signed-in user asked for an address none of their groups is admitted to, or an address where nothing is published.Access Control

Each event names the user, the application and its address, the device's public address with its location, operating system and browser. The activity page's code filter finds them quickly: on a busy account they are soon pushed down by routine events.

Restrictions

Restrictions protect the data an application shows, inside its own pages, in any browser and with nothing installed on the device. They are the kinds of rules the Netzilo browser extension applies to web domains through a profile, set here for one application and its users.

Open the application's Restrictions tab. Each card turns one restriction on; a card with settings opens a dialog, the others switch on and off with a click. ON marks the ones in force. Save the application to apply them.

The Restrictions tab of the application dialog with eight cards: Redact Data, Add Watermark, Restrict Clipboard, Restrict Printing, Restrict Downloads, Restrict Uploads and Show Gray Border marked ON, and Block URLs marked OFF

RestrictionWhat it does in the application's pages
Redact DataMasks text that matches a pattern before it is displayed. Each rule has a Pattern, a Mask with text and how many characters to keep at the end (Last): \b4[0-9]{15}\b with •••• and 4 shows a card number as •••• 1111. Only text shown on the page is masked. Form fields, rich-text and code editors, and graphics are left alone, so a value the user edits and saves is never changed.
Add WatermarkDraws a text over every page, Sparse (five marks) or Dense (a tiled pattern). %netzilo.username%, %netzilo.ip% and %netzilo.region% are filled in for each user when they sign in: their name, public address and city. %date% and %time% show the current date and time, %newline% breaks the line. The watermark cannot be selected, copied or found with the browser's search.
Restrict ClipboardBlocks copying, cutting and dragging text, images and links out of the application, including copies the page makes itself. Pasting into the application stays possible, and dragging the application's own items, such as cards on a board, keeps working.
Restrict PrintingA printed page shows Printing is restricted by your organization. instead of the content. Ctrl+P and Cmd+P are blocked; the application's own shortcuts with Shift are not.
Restrict Downloadsall blocks every download, or patterns block files whose name or address matches. A download is a link marked for download, a file the page builds itself, a save dialog, or a link to the application whose path ends in a document or archive extension such as .pdf, .csv, .xlsx or .zip. Links to pages of the application and links to other sites are never blocked.
Restrict Uploadsall blocks every file, or patterns block files whose name matches, for example \.(exe|zip)$. It covers files chosen in a file field, dropped or pasted onto the page, and files the page's scripts send. A blocked upload reaches the application as a refused request, so the page shows its own error.
Block URLsPatterns on the full address of a page of the application, for example /admin/. A blocked page is not shown: the user sees Access restricted with a Go back button, also when a single-page application changes its address without loading a page. Links to blocked addresses do nothing.
Show Gray BorderFrames the application's pages with a gray border, so users see at a glance that the page is protected.

Patterns are regular expressions as browsers evaluate them. Patterns for downloads, uploads and addresses ignore case; a redaction pattern is case-sensitive unless written as /pattern/i. The dialog refuses a pattern the browser cannot use and a pattern with a repeated group inside a repetition, such as (a+)+, which can make a page hang, and shows Not a valid pattern under it.

The Restrict Uploads dialog with one rule, the pattern \.(exe|zip)$, an Add Rule button and Save

In the browser

The application looks and works as before, with the restrictions in force. The page below has a watermark, a gray border and two redaction rules for card numbers and IBANs; the user tried to copy a cell.

An example CRM page published as an application: card numbers and IBANs shown as four dots and their last four digits, the watermark Confidential, alice@example.com, the date and time repeated across the page, a gray border, and two Netzilo notices at the bottom right, Your organization restricts viewing sensitive data on this application and Your organization restricts copying and dragging content from this application

When a restriction stops something, a Netzilo notice appears at the bottom right for ten seconds: Your organization restricts copying and dragging content from this application, ... printing this content, ... downloading files from this application, ... uploading files to this application, ... access to this address, or, the first time data is masked on a page, ... viewing sensitive data on this application.

How restrictions are applied

  • Only applications with restrictions are touched. For such an application the reverse proxy adds a small Netzilo script to each page a browser opens, pages in frames included. The script and its icons are served from the application's own address under /.netzilo/dlp/. Nothing else is read or changed: API calls, files, images and streams pass through as the application sent them. An application without restrictions is served exactly as before.
  • Every signed-in browser. Restrictions apply in every browser, with or without the Netzilo extension or the Enterprise Browser; their own profile rules apply as well. Scripts and services that call the application with a token get no pages and no restrictions.
  • The application's Content-Security-Policy is kept. It is extended only by what the Netzilo script needs: the script itself, its reports and its icons, each by its own path. A page whose policy allows no scripts at all is served unchanged, without restrictions.
  • Changes reach users without a new sign-in. Protected pages are always fetched fresh, and a saved change reaches the next page the user opens, within about a minute. A page that is already open keeps the restrictions it was loaded with until it is reloaded.
  • A page that cannot be protected safely is served unchanged. That is a response that is not an HTML page (a file, JSON, an image), a page in UTF-16, a page compressed in a format other than gzip, or a page whose start does not arrive within two seconds. On a self-hosted server the reverse proxy's log counts these, see Published applications on your server.

Activity

Every action a restriction stops is recorded under Activity > Events, with the same events the browser extension records, so one search finds both:

EventCodeRecorded when
Copy/Paste blockedbrowser.data.clipboard.blockedA copy, cut or drag was blocked.
Printing blockedbrowser.data.print.blockedThe user tried to print.
Sensitive data redactedbrowser.data.redactedA redaction rule masked text on a page, once per rule and page.
Download blockedbrowser.download.fileA download was blocked.
Upload blockedbrowser.upload.fileAn upload was blocked.
Blocked URLbrowser.url.blockedA blocked address was opened.

The event names the user, the file or the pattern, the page's address without its query, and the browser, for example Blocked downloading statement.pdf on https://crm.apps.example.com/accounts from Chrome 130 on macOS 15.1. The page reports what it stopped, up to 30 events a minute per page.

Limits

Restrictions work inside the page. They deter and record; they are not a boundary against a user who controls their own browser and turns the script off with developer tools. Screenshots and screen sharing are not prevented; for that, require the Enterprise Browser or Enterprise Workspace. Not covered are downloads the server starts without a link the page sees, such as a file sent back after a form is submitted, pages an application serves from its own offline cache, the page returned after a form is submitted, and frames from other sites.

Scripts and services

A script, a monitoring job or a service can call a published application without a browser by sending a Netzilo credential on every request:

curl https://grafana.apps.example.com/api/health \
  -H "Authorization: Bearer nzl_..."

The bearer is the caller's personal access token, or a token from your identity provider. The reverse proxy consumes it: the application does not receive this Authorization header. When the application expects a bearer token of its own, send the Netzilo credential as Proxy-Authorization: Bearer nzl_... instead and the application's own Authorization header passes through as sent:

curl https://grafana.apps.example.com/api/dashboards \
  -H "Proxy-Authorization: Bearer nzl_..." \
  -H "Authorization: Bearer <the application's own token>"

Proxy-Authorization works only when nothing in front of the reverse proxy removes it. Caddy, which fronts the reverse proxy on a self-hosted server, removes it like other proxies do, so there the Netzilo credential goes in Authorization and the application cannot receive a bearer token of its own. The X-Netzilo-Bearer header of earlier releases is no longer read. Restrictions do not apply to scripts and services: they receive no pages.

The credential is checked like a browser sign-in, and its owner must be admitted to the application. The owner is the user the application sees. Answers to a caller without a browser are JSON: 401 when the credential is refused, 403 when the owner is not allowed to open the application, 404 when there is no application at the address, 429 after 20 refused credentials from one address in 5 minutes, and 503 with a Retry-After header while the tunnel is not up yet. Every answer carries an X-Request-Id header.

Create the token as the user the application should see. Users create their own tokens in the user menu under Profile Settings, see Profile Settings. For a service account, create an agent under Team > Agents and a token for it, see Agents. A token reaches every application its owner is admitted to, from anywhere, so treat it like a password.

Through a web proxy

Your organization's web proxy can send its users to a published application and tell the reverse proxy who each user is. Nothing changes on the devices: the proxy authenticates the user as it already does, and the application sees that user as if they had signed in themselves. The typical use is an AI Gateway behind a secure web gateway such as Squid, Zscaler, Netskope, Skyhigh or Broadcom ProxySG.

On every request the proxy sends:

HeaderValue
AuthorizationBearer <token>: a token of a service user of your account, the proxy's own credential
X-Authenticated-UserThe email address of the user the proxy authenticated

To set it up:

  1. Under Team > Agents, create a service user with the role Admin for the proxy and a token for it, see Agents. The token's name names the users' tunnels, for example Skyhigh Prod.
  2. Edit the application and enter the proxy's outgoing addresses under Trusted Proxies.
  3. Make sure the proxy's users exist in Netzilo with the role User, with the email address the proxy sends, and are in one of the application's groups. Users synchronized from the identity provider that both the proxy and Netzilo use have the same address on both sides.
  4. Configure the proxy to send the two headers.

The reverse proxy believes the user's name only when both hold: the request comes from an address under Trusted Proxies, and the token is a service user's. It then looks the email address up among your account's users and works as that user's own token would: it checks the user's admission and the application's posture checks, and starts the user's own tunnel. The service user creates one personal access token per user, named after the proxy's token and valid for a year, and the reverse proxy reuses it from then on, also after a restart. You see these tokens under the user's Access Tokens. Deleting one is harmless: the next request gets a new one.

The proxy sendsAnswer
The token and the email of a user of the accountThe application, served as that user
An email that belongs to no user, to a blocked user, or to two users403 unknown user
An email of an Admin or Owner403 this user cannot be served through a proxy. Only users with the role User are served this way.
The token without X-Authenticated-User403 a trusted proxy must name the user in X-Authenticated-User
A token that is refused401 credential refused
The headers from an address that is not under Trusted ProxiesThe name is ignored: the request is the token's own, and the service user is normally not admitted (403)

X-Authenticated-User is never forwarded to the application, whoever sends it. A user's own token with an X-Authenticated-User header is that user, never the one named.

Refusals of a named user do not count against the proxy's address. Many users share it, so one user's bad request does not block the others.

Reverse-proxy peers in the Peers list

Each user's tunnel appears under Endpoint > Peers as a peer named vp-<n>-RPROXY.

The peer detail page of a user's reverse-proxy peer, shown here as edge-proxy-1, with the owner alice@example.com, the public IP address 203.0.113.13, the operating system macOS 10.15.7, the browser Chrome 152.0.7977.130, a security score of C and the agent version 5.1.571

  • One per user. All of a user's browsers and API clients share the tunnel, from any address and operating system. The peer shows the address and operating system of the latest browser it served, and location and operating-system posture are judged on that.
  • One more per user and web proxy. A user served through a web proxy gets a tunnel of their own for that proxy, named after the proxy's token, for example vp-skyhigh-prod-RPROXY. Every user behind the proxy has a peer of that name, each owned by its user, so the Peers list shows which users came through which proxy.
  • The peer comes back. After the idle stop or a restart of the reverse proxy the same vp-<n>-RPROXY reconnects instead of a new number appearing. An identity unused for 30 days is dropped.
  • What it shows. The user's public IP address and location, the operating system and version the browser reported when the user signed in, and the reverse proxy's version as the agent version. The Netzilo Gateway indicator in the security score is lit, as it is for browser sessions.
  • Sessions. The peer's page lists every session the tunnel served: the application and its hostname, the source IP, the client (a browser, an agent such as Claude Code or an agent built with the Netzilo SDK, or another program by its name) with its version, and when it was first and last seen. A session used in the last 15 minutes is live and has a green dot. In the Peers list, N sessions under Last seen counts the live ones; hover over the peer's name to see them. A peer keeps at most 50 sessions, and a session unseen for 30 days is dropped.

The page of the reverse-proxy peer vp-129-RPROXY with its Sessions panel listing three sessions of the application LLM Gateway at llm.apps.example.com from 203.0.113.14: claude-cli 2.1.0, DevOps Agent and Netzilo Enterprise Browser, each with its first and last seen time

  • Cleanup. The peers are kept while offline, so a returning user's tunnel logs in again instead of registering anew. Peer inactivity expiration, when it is on for the account, removes them like any other offline peer, and they register again under the same name on the next use.
  • Not a browser session. The peer is the user's tunnel, not a browser with the extension. It does not appear in the Workplace's Private access status.

Posture checks for reverse-proxy peers

Posture checks on the policies that reach the target are evaluated against the user's reverse-proxy peer, after the door has admitted the user. Requirements on the device belong on the application, see Posture checks on the application.

CheckEvaluated against
Operating SystemThe operating system and version the browser reported at sign-in. Chrome and Edge report the real version. Firefox and Safari report macOS as 10.15 and Windows as 10.0, so a minimum above those values blocks them.
Netzilo Client VersionThe reverse proxy's version.
Country & RegionThe location of the user's public IP address.
Peer Network RangeThe user's public IP address.
Netzilo GatewayPasses, as it does for browser sessions.
Process, Endpoint Security Settings such as firewall, antivirus or disk encryption, and the device items of Advanced Endpoint SettingsAlways fail. A reverse-proxy peer is not a managed endpoint.

To let browser users reach a target that desktop users reach only with endpoint checks, give them a separate policy without those checks, or with location, network range and operating system checks only. When a session starts, the activity log records Peer access blocked for each policy whose checks it fails. These events show the design working, not a fault.

Publish an AI Gateway

A Netzilo AI Gateway can be published like any other application, so that users and their AI tools reach it from anywhere without a public port on the gateway host:

  1. Under Network > Applications, click Add Application.
  2. Address: a name under one of your application domains, for example aigw.apps.example.com.
  3. Target: the gateway peer's address with its port, for example http://<gateway-name>.netzilo.network:8447.
  4. Groups: the groups of the users who call the gateway.
  5. Turn Forward the user's credential on. The gateway identifies each caller from the token; with the switch off it receives no credential and refuses the request.

Callers send their Netzilo token as Authorization: Bearer. The published address also serves the sign-in that MCP connectors and Claude Desktop use. The full setup is in AI Gateway.

Self-hosted servers

On a self-hosted Netzilo Server the reverse proxy runs as the reverse-proxy container behind Caddy on port 443. The installer adds it when you give it an applications domain, and a server installed without one can get it later. The domain, certificates, adding it to an older server, its options and its logs are in Published applications on your server.

The reverse proxy and the clientless-access gateway are two containers with two purposes. The gateway serves browsers that carry the Netzilo browser extension, see Clientless Access. The reverse proxy serves published applications to browsers with nothing installed.

Troubleshooting

There is no application at this address. Publishing is off under Settings > Permissions, the application is disabled or deleted, or the address differs from the one published. A newly saved address can take up to a minute to answer.

The address does not resolve, or the browser shows a certificate error. Check the wildcard record with Verify under Settings > Permissions. On a self-hosted server with Let's Encrypt, the first visit to a new application obtains its certificate; try again after a few seconds. A certificate you provided must cover the wildcard.

Access Denied, your account is not allowed to open the address. The user is in none of the application's groups. Add the group, or turn publishing on. An existing session follows within 10 minutes; a new sign-in at once. The event Application access denied: not admitted records the attempt.

Access Denied because a posture check failed. The event Application access denied by posture names the check and the reason. Then:

  • Peer is not using Netzilo Enterprise Workspace, from a device that is in the Workspace. The door learns this from the Netzilo client inside the Workspace. The client must be current: an older client answers nothing, and the rule fails as for a plain browser. Update the client in the Workspace and sign in again.
  • Peer is not using Netzilo Enterprise Browser, from the Enterprise Browser. The browser is recognized by its own User-Agent. Check that the user is really in the Enterprise Browser, not in another browser on the same computer.
  • An antivirus is not active, Disk encryption is not enabled and the other endpoint rules, from a device with the Netzilo client. The device reports these the same way it does for its peer: compare the indicators on its peer page. Without a client on the device these rules always fail.
  • Peer is not a Netzilo gateway session. The Netzilo Gateway rule never passes at the door. Remove it from the application's checks; it is for policies.
  • The check passes on the device now but the session is still refused. A running session is judged on its sign-in's evidence. Have the user sign out of the Workplace and open the application again.

Additional Protection Required. The application requires the Netzilo browser extension and this browser has none, or one that follows another server. The dialog offers to add it, or to connect it to this server, and opens the application again when it answers. An old extension that cannot be connected from the dialog is updated or connected from its own popup.

Access Failed. The user is signed in and admitted, but the target is not reachable through the user's tunnel. Check, in this order:

  • The route. The target's network is a route distributed to one of the user's groups.
  • The policy. A policy from one of the user's groups allows the target.
  • Posture checks. The policy's checks can pass for a reverse-proxy peer. Endpoint checks never do, and an OS minimum above what the browser reports blocks it. See Posture checks for reverse-proxy peers.
  • The target. The address and port are right and the application is up. A name is resolved by the user's DNS settings, not by the server.
  • The peer. Look for the user's vp-<n>-RPROXY peer under Endpoint > Peers and check that it is connected.

The same user reaching the target with the Netzilo client proves the route and the policy.

Stuck at Logging in. The user's tunnel cannot connect, or management is unreachable from the reverse proxy. On a self-hosted server, check the reverse-proxy container's log while the user retries.

The sign-in did not come from the Workplace. On a self-hosted server the --workplace-url option does not match the address users sign in at. Set it to the server's address, scheme and host exactly, and recreate the container. See Published applications on your server.

Sign-in expired. The sign-in link was older than 10 minutes, was used twice, or the browser blocks cookies for the application's address. Open the application from the Workplace tile again.

The application loads, but links, redirects or its own login go to an internal name. The application builds absolute URLs from its configured base address. Set that to the published address, or turn on Send the address as Host header for the application.

The application works for some users only. The users' groups admit them differently, or their policies reach the target differently.

A script gets 401 with a valid token. The token is expired or revoked, or its owner is blocked. A script still sending X-Netzilo-Bearer must send Authorization: Bearer instead. A token sent in Proxy-Authorization is removed by Caddy and most other proxies in front of the reverse proxy: send it in Authorization.

A published AI Gateway refuses every request. Forward the user's credential is off, so the gateway receives no token. Turn it on for that application. Test with a GET to /v1/models first: a failed POST gets an HTML error page, a GET the JSON answer.

Users behind a web proxy get 403 not allowed to open this application. The request did not come from an address under Trusted Proxies, so the reverse proxy ignored the name and judged the proxy's own token. Add the proxy's outgoing addresses to Trusted Proxies; a change takes effect within a minute. On a self-hosted server the reverse proxy must see the proxy's real address, see Published applications on your server.

A user behind a web proxy gets 403 unknown user or this user cannot be served through a proxy. The email address the proxy sends belongs to no user of the account, to a blocked user, or to two users; or the user is an Admin or Owner. Compare the address with the user under Team > Users.

A web proxy's users get 503 the user's credential is being renewed. The user's token made for the proxy was deleted. The next request gets a new one.

After a restart every user is sent through the Workplace again. Sessions live in the reverse proxy's memory. This is expected, and silent while the Workplace session is alive.

A restriction does not apply on a page. Check that the application was saved with the restriction ON, and reload the page: an open page keeps the restrictions it was loaded with. Pages that are not HTML, or whose policy allows no scripts, are served unchanged. On a self-hosted server the reverse proxy's log says why a page was passed through, see Logs and health.

A link or button no longer works on a restricted application. Restrict Downloads blocks links whose path ends in a document or archive extension; Block URLs blocks every address its patterns match. Narrow the pattern, or use patterns instead of all.

Users see masked text where they should not. A redaction pattern matches more than intended. Test it against sample text, and anchor it, for example with \b at both ends.