Configure Sites
Set who may publish, how the proxy behaves and how long visitors stay signed in.
Where the settings are
An administrator edits instance-wide settings in the plugin details under Settings → Plugins. They apply to every Site served through the proxy, with no per-Site override.
Numeric fields show their unit beside the input: sign-in validity in hours, proxy sizes in MiB, and timeouts and the HTTPS lifetime in seconds. Titled groups start open and remember whether you closed them, and the help icon holds the long explanation.
Publishing
| Setting | Key | Default | What it controls |
|---|---|---|---|
| Default visibility | defaultVisibility |
Private | Starting access for a new Site: private, Project members or signed-in accounts. |
| Allow public sites | allowPublicSites |
On | Whether someone can make a Site public. |
| Who may publish | publishers |
Every account | Every account, or administrators only. |
Limits
| Setting | Key | Default | What it controls |
|---|---|---|---|
| Sites per account | maxSitesPerAccount |
20 | Maximum number of Sites per account, from 1 to 500. |
Reverse proxy
| Setting | Key | Default | Valid values |
|---|---|---|---|
| Upload size | maxRequestBodyMb |
Unlimited | 0 to 65536 MiB; zero means no limit. |
| Inactivity timeout | idleTimeoutSeconds |
3600 seconds | 1 to 86400 whole seconds. |
| Connection timeout | connectTimeoutSeconds |
60 seconds | 1 to 75 whole seconds. |
| WebSocket and Upgrade | allowUpgrade |
On | On or off. |
| Response size | proxyMaxResponseMb |
Unlimited | 0 to 65536 MiB; zero means no limit. |
| Gzip compression | gzip |
Off | On or off. |
| Require HTTPS in browsers | hsts |
Off | On or off. |
| HTTPS policy lifetime | hstsMaxAgeSeconds |
31536000 seconds | 0 to 63072000 whole seconds. |
The inactivity timeout measures time without data, not the total length of a request, so an active upload, download or event stream may continue past it. The connection timeout limits how long connecting to the application may take. A response that crosses a nonzero size limit is closed instead of returning as a truncated success.
WebSocket and Upgrade allows application protocol upgrades, including WebSocket, after the usual Site access checks. With Gzip compression on, eligible responses are compressed when the browser accepts gzip, and already compressed responses pass through unchanged.
Require HTTPS in browsers tells browsers to use HTTPS for the Site, without subdomains. Browsers keep the policy for its lifetime even after you switch the setting off, and a lifetime of zero clears it.
Access
| Setting | Key | Default | What it controls |
|---|---|---|---|
| Sign-in validity | sessionTtlHours |
12 hours | How long a visitor stays signed in, from 1 to 720 hours. |
| Sites DNS destination | gatewayDnsTarget |
Not set | Hostname or IP address for public DNS; empty uses the Chetty app hostname. |
| Contact email for certificates | contactEmail |
Not set | Address sent to the certificate authority for issuance and expiry notices. |
Removing access still applies immediately, whatever the sign-in validity says. Certificates need a contact email.
The DNS destination must reach this Chetty host directly; an external proxy needs its own TLS support.