You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am hosting chainlit on a kubernetes (envoy+istio) server on 1 pod and connected to okta. But since I migrated to chainlit 2.0, users get disconnected every two hours. I also updated the config with increased timeout for the two config available:
# Duration (in seconds) during which the session is saved when the connection is lost
session_timeout = 3600 # 1 hour, but also tested running it with session_timeout = 28800, 8 hours without seeing improvements
# Duration (in seconds) of the user session expiry
user_session_timeout = 86400 # 1 day
I am not using sticky sessions for now.
Are there other configuration that I'm missing?
The text was updated successfully, but these errors were encountered:
[1] Allow user session timeout to be configurable - This thread discusses the ability to configure user session timeouts, which may relate to your issue with frequent disconnections after the upgrade.
I am hosting chainlit on a kubernetes (envoy+istio) server on 1 pod and connected to okta. But since I migrated to chainlit 2.0, users get disconnected every two hours. I also updated the config with increased timeout for the two config available:
I am not using sticky sessions for now.
Are there other configuration that I'm missing?
The text was updated successfully, but these errors were encountered: