SSR CLI login fails using console, SSH or Conductor remote (web) login.

• SSR cli (console or SSH) login fails while SSR is running normally
• Rebooting SSR, login works for a few minutes, if login is attempted as soon as login prompt is available, before stopping again
• Radius authentication server is configured in the conductor (even if not used for SSR cli login)

Check the radius server timeout in Conductor. It must be shorter than the router CLI login timeout (default 60s)

The Radius server timeout is impacted by the number of radius servers configured + retry time. If no "accept" response from radius server (for the local accounts) The timeout for each radius server multiplied by number of retries (likely 3) must be less than the login timeout 60s

a radius server timeout set to 12s is likely good.