openclaw - 💡(How to fix) Fix [Bug] Control UI 4.5: Media files show as blank - file:// path used instead of HTTP [1 comments, 2 participants]

TL;DR

The issue can be resolved by configuring the Control UI to use HTTP URLs for media instead of file:// URLs, potentially by updating the control-ui-config.json file or the gateway configuration.

Guidance

• Verify that the control-ui-config.json file is correctly configured and accessible via the expected URL, as the 404 error suggests a potential misconfiguration.
• Check the gateway configuration to ensure it is properly serving media files and the control-ui-config.json file, considering the loopback bind mode and version 2026.4.5.
• Investigate why the browser is attempting to load media via file:// protocol instead of an HTTP URL, which may involve updating the image generation tool or the Control UI to use the correct URL scheme.
• Test accessing the media files directly via their expected HTTP URLs to confirm they are being served correctly by the gateway.

Example

No specific code snippet is provided due to the lack of detailed implementation details in the issue, but an example of how media URLs might be correctly configured could involve changing src attributes in the DOM from file:///C:/... to http://127.0.0.1:18789/....

Notes

The solution may depend on specific details of the OpenClaw configuration and implementation, which are not fully provided in the issue. Additionally, browser security restrictions on loading local files via file:// protocol are a known issue and using HTTP URLs is the standard approach to avoid these restrictions.

Recommendation

Apply a workaround by configuring the Control UI and gateway to use HTTP URLs for media, as this directly addresses the identified issue of file:// URLs causing browser security restrictions and 404 errors.