[Bug]: Agent avatars not displaying in Pinned Agents sidebar (R2 Storage)

[RedwindA]

What happened?

Agent avatars fail to load in the "Pinned Agents" sidebar (left panel) and show as broken/empty icons. However, the exact same avatars display correctly within the Agent Buider.

When inspecting the network tab, the requests for these avatar images from the sidebar are returning NS_BINDING_ABORTED. It seems like the image requests are being triggered but cancelled or failing specifically in the sidebar context, while the R2 signed URLs work fine in the editor view.

Version Information

ghcr.io/danny-avila/lc-dev latest 5aa0de7f3c33 9 hours ago 1.67GB

Steps to Reproduce

1. Configure LibreChat to use Cloudflare R2 for image storage.
2. Create an Agent and upload an avatar image in the Agent Builder.
3. Pin the Agent so it appears in the left-hand sidebar.
4. Observe the sidebar: the avatar icon is missing or broken.
5. Open the Agent Builder for the same agent: the avatar displays correctly.

What browsers are you seeing the problem on?

Firefox and Edge

Relevant log output

- GET https://<R2_BUCKET_ID>.r2.cloudflarestorage.com/images/658fdd4baf8bf540fff54c3e/agent-agent JJutpEqB3WxCjHZnmHDEU-avatar-1766860608142.png?X-Amz-Alg... NS BINDING ABORTED

- GET https://<R2_BUCKET_ID>.r2.cloudflarestorage.com/images/658fdd4baf8bf540fff54c3e/agent-agent Bmw9s11A10v2DuZCgTw-y-avatar-1766860573728.png?X-Amz-Alg... NS BINDING ABORTED

- GET https://<R2_BUCKET_ID>.r2.cloudflarestorage.com/images/658fdd4baf8bf540fff54c3e/agent-agent Wmt9XpmYqprn29jrU2n7h-avatar-1766860417431.png?X-Amz-Alg... NS BINDING ABORTED

Screenshots

Code of Conduct

• I agree to follow this project's Code of Conduct

[danny-avila]

Should be fixed by #11241 once merged on main, now on dev.

Root cause: LibreChat periodically refreshes expiring S3 signed URLs. During refresh, extractKeyFromS3Url did not recognise the R2 hostname (<accountid>.r2.cloudflarestorage.com) as path-style, so it extracted my-bucket/images/user/avatar.png instead of images/user/avatar.png as the object key. A new signed URL was then generated with that wrong key, pointing to a non-existent object and returning a 404.

Why it works in Agent Builder but not the sidebar: The Agent Builder holds the original upload URL in component state for the duration of your session. The sidebar always reads the stored URL from the database, the one that has already been through the broken refresh cycle.

How it's fixed: Same fix as above, the key extraction now checks whether the URL path starts with AWS_BUCKET_NAME and strips it automatically. No config changes needed after updating to dev.

If avatars are still broken after updating, the stored URLs in your database were already corrupted by the old refresh logic. Re-uploading the affected agent avatars will regenerate clean URLs that refresh correctly going forward.

[danny-avila]

Also you may need AWS_FORCE_PATH_STYLE=true in your .env (just added)