Outbound proxy

The Proxy page (/system/proxy) governs how the server establishes outbound connections — for licence activation, captcha verification or AI providers, for instance. Changes take effect immediately; no restart is needed.

Mode

Mode	Behaviour
System setting (default)	Uses the operating system’s proxy, or the HTTP_PROXY/HTTPS_PROXY variables.
No proxy	Always connects directly and ignores any proxy environment variables that are set.
Manual	Uses the address and credentials given below.

Manual configuration

The fields are active in Manual mode only:

Field	Meaning
Proxy address	The full URL with scheme and port, http://proxy.example.local:3128 for example
Exceptions (bypass)	Comma-separated hosts that bypass the proxy; wildcards are permitted (*.example.local, for instance). Prefilled with localhost,127.0.0.1,::1.
Bypass the proxy for local addresses	Host names without a dot (intranet names) are connected directly.
Use the service account’s credentials	Authenticate at the proxy with the service’s Windows identity (NTLM/Kerberos) instead of a user name and password.
User name / password	The proxy credentials; domain accounts as DOMAIN\user. A password that is already stored is shown as “(stored – leave empty to keep)” — leaving it empty keeps it, entering something overwrites it.

Warning

Without an encryption master key configured, the page warns that the proxy password would be stored in plain text in system.db. In production environments, set Velkaris:Encryption:MasterKey or the environment variable VELKARIS_ENCRYPTION_KEY.

The connection test

The “Connection test” card checks the current form values — including unsaved ones. Without a test address, the licence activation address is used (the call that has to pass through the proxy in practice). The result appears with the elapsed time and, where applicable, the HTTP status; typical messages are:

Message	Cause and remedy
“Connection successful – the proxy passes the request through.”	All is well.
“The host name could not be resolved…”	Check the spelling and DNS.
“No connection could be established…”	Check the address, port and firewall.
“The TLS connection failed…”	Often an untrusted certificate on the proxy.
“The proxy refused the sign-in (407)…”	Check the user name and password.
“Timed out after 10 seconds…”	The proxy is not responding.

Save applies the values permanently (from then on they override the values from the server configuration); Reset discards the form changes. Saving is recorded with the audit entry proxy.update, and every test with proxy.test.