openclaw - 💡(How to fix) Fix Webchat HTTP 401 on __openclaw/ routes after session compaction [1 participants]

TL;DR

The 401 errors in the OpenClaw webchat UI after session compaction may be related to authentication issues caused by the rate-limited auth profile "minimax" during compaction.

Guidance

• Verify that the auth profile "minimax" is correctly configured and not causing issues with authentication during session compaction.
• Check the Gateway Log for any specific error messages related to authentication or rate limiting that may indicate the root cause of the 401 errors.
• Test the webchat UI with a different auth profile to see if the issue persists, which could help determine if the problem is specific to the "minimax" profile.
• Consider temporarily disabling rate limiting on the "minimax" auth profile to see if it resolves the issue, which could help confirm if rate limiting is the cause.

Example

No code snippet is provided as there is no clear indication of a specific code issue.

Notes

The issue seems to be related to the interaction between session compaction, the "minimax" auth profile, and rate limiting. The fact that WebSocket connections work fine but HTTP requests for static resources fail with 401 errors suggests an issue with how authentication is handled during session compaction.

Recommendation

Apply a workaround by temporarily disabling rate limiting on the "minimax" auth profile to see if it resolves the issue, as this could help determine if rate limiting is the cause of the 401 errors.