Getting Invalid Transport session Errors on Standard instance

1

I deployed a Chainlit application a couple of weeks ago. When I began stress testing it broke down and triggered a restart on the instance. Looking at the Event logs, I noticed that it exceeded its instance’s memory so I upgraded my plan from Starter to Standard with 2GB RAM. However I am now getting this error:

2024-10-15 14:36:12 - Invalid transport for session w3u81wy30FWnm2EpAAAA (further occurrences of this error will be logged with level INFO)

Oct 15 03:36:12 PM Invalid transport for session w3u81wy30FWnm2EpAAAA (further occurrences of this error will be logged with level INFO)

Oct 15 04:34:02 PM Invalid session YL_SAYqEyFJLrLgnAAAC (further occurrences of this error will be logged with level INFO)

Oct 15 04:34:02 PM2024-10-15 15:34:02 - Invalid session YL_SAYqEyFJLrLgnAAAC (further occurrences of this error will be logged with level INFO)

Why is this happening and how can I resolve it?

2

Hi Elvis,

Based on that error, it looks like Chainlit might be using socketio or maybe you’re using its Copilot feature.

I found this GitHub issue: https://github.com/Chainlit/chainlit/issues/1279 which mentions sticky sessions, which, unfortunately, we don’t support today.

I’d encourage you to submit a feature request at https://feedback.render.com/features/p/sticky-session.

We rely heavily on customer feedback as a part of our planning and product roadmap process, so capturing interest on the feature request page is very helpful.

Regards,

Matt

3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.