Overview
Most settings in Teramind On-Premises apply immediately after you save them on the dashboard. However, a small number of settings trigger an automatic full Teramind restart when saved. This restart typically takes around 5 minutes, during which the dashboard will be temporarily unavailable.
Use this article to identify those settings, plan changes during a maintenance window if needed, and understand what to expect after saving.
Settings That Trigger a Full Server Restart
A full server restart is triggered after saving any of the following settings:
Setting | Dashboard Location |
Hostname | |
Maximum daily alerts count | |
User notification alert threshold | |
Log alert threshold |
If a save action includes any of the above settings together with other settings (e.g., Settings That Restart Specific Services or Settings That Do Not Require a Full Restart), the entire save operation will still trigger a full restart.
The following sections describe why the restart is needed and what you can expect:
Hostname
Changing the hostname updates how your Teramind server is accessed, including your dashboard URL, SSL certificate, and the endpoints your agents connect to. Because this affects core service configuration, Teramind must restart to apply the new value.
After saving, the dashboard may briefly disconnect. Wait for the system to finish restarting before verifying that the new hostname is accessible and that agents are still connecting normally.
Maximum Daily Alerts Count
This setting limits how many alerts of a given type can be logged each day. It can also be configured at the rule level in Advanced mode, in the Choose maximum number of saved alerts per day field.
Because the behavior rule engine caches this threshold, Teramind restarts after saving so the updated value can be applied system-wide.
User Notification Alert Threshold
This setting controls the minimum time between Warn or Block alerts shown to monitored users. If it is set to 0, all applicable alerts are shown immediately.
Similar to other alert settings, the behavior rule engine caches this threshold, Teramind restarts after saving so the updated value can be applied system-wide.
Log Alert Threshold
This setting controls the minimum time between logged alert events. If it is set to 0, alerts are logged without rate limiting.
Similar to other alert settings, the behavior rule engine caches this threshold, Teramind restarts after saving so the updated value can be applied system-wide.
Settings That Restart Specific Services Only
The following settings restart only certain service containers instead of the entire server. These changes can still cause brief interruptions, but they are narrower in scope than a full restart.
Setting | Where to find it | Impact |
Management interface port / Load balancer port | Restarts web and server-related services (e.g., | |
Enable multi-node / Enable SSH access / Allow new nodes | Restarts security and node-related services (e.g., | |
SSL keys | Restarts web and server-related services after keys are validated and saved (e.g., |
Settings That Do Not Require a Full Restart
Most settings apply without a full Teramind restart. Common examples include:
SMTP and email settings
Authentication, 2FA, SSO, SAML, and password policy settings
Session and cookie timeout settings
Locale settings such as timezone, language, NTP, and currency
OCR and Agent Settings
Alert templates, daily digest options, and license overutilization email settings
Most other Alerts settings except the three alert threshold fields listed above
What to Do After Saving a Restart-Triggering Setting
Wait for the restart to complete. This typically takes a few minutes.
Confirm the dashboard is accessible again.
Re-open the relevant Configurations > Settings page(s) and verify the new values were saved.
Check System > System Health for any issues.
If you changed the hostname, confirm the new address is reachable and that agents are still reporting normally.
Tips: If uptime is important for your environment, schedule these changes during a maintenance window to reduce user impact.
Frequently Asked Questions
How do I know a restart is happening?
The dashboard may become briefly unavailable after you save one of the restart-triggering settings. Access should return automatically when services are back online.
Does this apply to Teramind Cloud?
No. This behavior applies to Teramind On-Premises/Private Cloud deployments.
Can I avoid the restart?
No. These specific settings require a restart before the new values can take effect.