Some Images Don't Load on librechat.ai

[wldtazm4]

What happened?

Not sure if this is just for me, but some images are not loading correctly on the "https://www.librechat.ai/" site. I primarily use Chrome, but have tried Edge and Firefox as well. I have tried on multiple computers and on android phone (including different networks on the phone).

These only load after I refresh a couple times. I see this all over the docs site randomly, but here are a few examples:
https://www.librechat.ai/docs/features/rag_api
https://www.librechat.ai/docs/features/fork#visible-messages-only

This one doesn't load at all, might have to do with being updated today but thought I would mention it anyway (just in case): https://www.librechat.ai/docs/features/agents#agent-chain

I tried to view the agent chain image in a separate window and it showed this error: 402: PAYMENT_REQUIRED
Code: OPTIMIZED_IMAGE_REQUEST_PAYMENT_REQUIRED

If this is a "just me" problem, that's fine. Just wanted to report it if its not.

Also just wanted to thank you for all the work on this project. I have been loving it, and I am always excited for the features and releases you guys drop! Keep up the great work!

Version Information

ghcr.io/danny-avila/librechat-dev latest e4979ae60fba 3 hours ago 866MB
ghcr.io/danny-avila/librechat-rag-api-dev-lite latest 6550e7ddf180 11 days ago 1.3GB

Steps to Reproduce

1. Go to https://www.librechat.ai/
2. Clear browser cache.
3. Check some of the links provided above.
4. Some images do not load.
5. Refresh page a few times, then images usually load.

What browsers are you seeing the problem on?

Chrome

Relevant log output

Screenshots

Intermittent loading example:

Can't get to load at all example:

402 errors:

Console logs screenshot:

Code of Conduct

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

[danny-avila]

This image was recently added, so it will load in eventually when the CDN is able to serve it effectively.

[wldtazm4]

I figured that was the case for the second part (like I mentioned).

The first part of the issue has been ongoing for me, and those pages haven't been updated since at least February (that I can tell).