Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

ESXi "SSH for the host has been enabled": decide, then switch the service off or set its policy

Technical article
VMware

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

The yellow warning "SSH for the host has been enabled" on an ESXi host's summary page means the SSH service is running on that host. A matching warning, "ESXi Shell for the Host has been enabled", appears when the local shell is on. Broadcom KB 367599 calls these messages "a proactive security measure" that informs administrators that remote access is enabled. The first decision is whether anyone needs SSH on this host right now. If not, stop the service. If yes, record why, and decide whether to keep the warning.

What the warning means

KB 367599, "Warning for Shell and SSH being enabled appears on host summary page" (Updated On: 03-04-2026), says that disabling Remote SSH and the ESXi Shell removes the messages from the host. It also describes a setting that hides them: UserVars.SuppressShellWarning, changed from 0 to 1 in the host's Advanced System Settings, or with vim-cmd hostsvc/advopt/update UserVars.SuppressShellWarning long 1. The KB gives long 0 to turn the warnings back on.

The TechDocs vSphere 8.0 page "Activate or Deactivate an ESXi Service" (Last Updated November 19, 2026) lists the ESXi Shell and SSH with a default of Stopped. It also says "Activating services affects the security of your host. Do not activate a service unless strictly necessary." The page "Activate Access to the ESXi Shell Using the vSphere Client" says: "Do not activate remote access to the host using SSH unless special circumstances require it."

Three settings decide how long SSH stays on and whether it returns after a reboot:

  • Startup policy: per the TechDocs services page, "Start and stop with host" starts the service shortly after the host starts; "Start and stop manually" keeps the state you set; "Start and stop with port usage" ties the service to whether its port is open. Changing the policy is separate from the one-time Start, Stop or Restart buttons.
  • UserVars.ESXiShellTimeOut: the TechDocs advanced settings page says it "Sets the time in seconds a login shell waits for login", that 0 deactivates the timeout, and that the default is 0.
  • UserVars.ESXiShellInteractiveTimeOut: the idle time in seconds before an interactive shell is logged out; default 0, and it applies to new sessions only.

Likely causes

Cause What you see How to confirm
SSH was started for a task and not stopped Warning; service Running; policy "Start and stop manually" Configure, System, Services shows SSH Running
SSH set to start with the host Warning returns after every reboot Services page shows policy "Start and stop with host"
ESXi Shell also running Two warnings Services page shows ESXi Shell Running
SSH stops by itself after a set time SSH works, then stops UserVars.ESXiShellTimeOut is not 0; KB 441004 found 3600
Host profile refuses a timeout together with automatic start Profile edit or apply fails KB 438124 error text on the host profile
Warning suppressed earlier SSH is running but no warning appears UserVars.SuppressShellWarning is 1

Prove the cause before changing anything

All read-only.

1. Read the services. In the vSphere Client, browse to the host, open Configure, then Services under System (TechDocs). Note, for SSH and for ESXi Shell, the status (Running or Stopped) and the startup policy.

2. Read the three settings. In Configure, System, Advanced System Settings, filter for UserVars.SuppressShellWarning, UserVars.ESXiShellTimeOut and UserVars.ESXiShellInteractiveTimeOut, and write down each value.

3. Read the shell log. KB 441004 shows lines in /var/run/log/shell.log such as "SSH login enabled" and "SSH login disabled" with timestamps. They show when the service was turned on and off.

4. Ask who needs SSH. Backup, monitoring, patching tools and support staff may rely on it. A stop that breaks a job is avoidable if you ask first.

A good result is a clear owner and reason for the running service, or no one who needs it. A bad result is an unexplained running service on a host that is not in a support window.

Fix

Stop SSH and the ESXi Shell

Disruptive step: stopping SSH ends open SSH sessions and breaks any tool or script that connects over SSH, and changing the startup policy to "Start and stop manually" (Edit Startup Policy) changes whether the service returns after a reboot, which is how the warning stops coming back when the policy was "Start and stop with host". Save first: write down the current status and startup policy of both services, and ask the people and tools that connect over SSH. Back out: set the startup policy back to the recorded value with Edit Startup Policy and choose Start.

In the vSphere Client, select the service on the host's Services page and choose Stop. TechDocs says to set the startup policy with Edit Startup Policy. The two TechDocs pages differ on what "Start and stop manually" does after a reboot. The services page says the host "preserves the user-determined service settings" and that a service left running is started again when the host is powered on. The page on activating access to the ESXi Shell says: "When you select Start and stop manually, the service does not start when you reboot the host. If you want the service to start when you reboot the host, select Start and stop with host." Check on your own host which one happens before you rely on either. Stop the service first, then set the policy.

Keep SSH, with the warning

If SSH must stay on, leave the warning in place. It is the on-screen reminder that remote access is open, and it is the proactive measure KB 367599 describes.

Keep SSH and suppress the warning

Risk: a suppressed warning removes the reminder, so an SSH service left running by mistake goes unnoticed. Save first: record the current UserVars.SuppressShellWarning value (the KB's states are 0 and 1), and write down the host, the reason and who will check the Services page. Back out: set the value back to the recorded one, with vim-cmd hostsvc/advopt/update UserVars.SuppressShellWarning long 0 for the KB's case of turning the warnings back on, or through Advanced System Settings.

If your process requires it, KB 367599 gives the setting above. The one setting hides both the SSH and the ESXi Shell warnings. Hiding the message does not close SSH: the service stays reachable. To set it, open Configure, System, Advanced System Settings in the vSphere Client and change UserVars.SuppressShellWarning from 0 to 1, or connect to the host over SSH using root credentials, as KB 367599 says, and run:

vim-cmd hostsvc/advopt/update UserVars.SuppressShellWarning long 1

SSH switches off after an hour

KB 441004 (Updated On: 05-27-2026, ESXi 8.x) found SSH stopping 60 minutes after it was enabled, even with the policy "Start and stop with host", because ESXiShellTimeOut was 3600. The arithmetic is 3600 seconds / 60 = 60 minutes. The KB's fix is to set the value to 0, which disables the timeout, and to ensure the service is set to start and stop with the host.

Risk: a value of 0 removes the automatic switch-off, which is a hardening control, and with the policy "Start and stop with host" SSH is on after every boot with no automatic switch-off. KB 438124 below says a configured shell timeout cannot be combined with automatic start in a host profile; neither KB says whether 0 counts as configured, so check the profile edit after you change the value. Save first: record the current value (3600 in the KB's case). Back out: set UserVars.ESXiShellTimeOut back to the recorded number.

Host profile conflict

KB 438124 (Updated On: 05-06-2026) says that when UserVars.ESXiShellTimeOut is configured, the ESXi Shell (TSM) and SSH (TSM-SSH) services cannot be set to start automatically in a host profile. Its fix is to set both services' startup policy to "Start and stop manually" (or off), uncheck the start-service box for both, save the host profile and apply it. Risk: applying a host profile changes the host's configuration. Save first: export or note the profile's current service settings. Back out: edit the profile back to the noted settings and apply it again; this works only if the noted settings still pass validation.

Example (illustrative): esx01 shows "SSH for the host has been enabled". The Services page shows SSH Running with the policy "Start and stop manually". shell.log shows "SSH login enabled" two weeks ago. The engineer who needed it has finished. The administrator notes both services' state, stops SSH, leaves the policy on manual, and the warning clears. esx02 runs a nightly tool that needs SSH. Its policy is "Start and stop with host" and the warning stays, with a note in the runbook saying why.

Confirm the fix

  1. The Services page shows SSH Stopped (or Running by intent), with the policy you chose.
  2. The host summary no longer shows the warning, unless SSH is meant to be on.
  3. Jobs that used SSH still work, or have been moved to another method.
  4. If you changed a timeout, wait out the timeout period once and check the service state.

What to watch afterwards

  • Check the Services page across all hosts on a schedule, especially if the warning is suppressed anywhere.
  • Record the UserVars.SuppressShellWarning value of each host in your change records.
  • Keep the SSH policy and timeouts in your host profile or build standard so every host matches.

Risks and limits

  • These commands have not been run or lab-tested.
  • KB 367599 labels its vim-cmd steps "esxcli" and uses a configuration path from an older client. The steps here use the TechDocs path (Configure, System, Advanced System Settings) and the KB's command exactly.
  • UserVars.SuppressShellWarning is not listed in the TechDocs "Partial List of Security Advanced System Settings". Its description comes from KB 367599 only.
  • The TechDocs services page lists the default status of SSH (Stopped) and calls "Start and stop with port usage" "The default setting for these services", but it gives no startup policy for SSH on its own. Read the policy on each host.
  • Lockdown mode and key-based SSH are separate topics.

Sources