# Links to preview files don't work in webui?

**URL:** <https://discuss.ipfs.tech/t/links-to-preview-files-dont-work-in-webui/7933>\
**Category:** Help\
**Created:** [May 7, 2020, 6:23pm UTC](https://discuss.ipfs.tech/t/links-to-preview-files-dont-work-in-webui/7933 "2020-05-07T18:23:32Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![MidnightLightning](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/midnightlightning/32/2651_2.png) [@MidnightLightning](https://discuss.ipfs.tech/u/MidnightLightning)\
**Post date:** [May 7, 2020, 6:23pm UTC](https://discuss.ipfs.tech/t/links-to-preview-files-dont-work-in-webui/7933/1 "2020-05-07T18:23:32Z")

</div>

I am running IPFS in a Docker container on a separate computer within my home network, and in setting the CORS headers settings to use the host computer’s local IP address of “192.168.0.100” and API configurations to use “0.0.0.0” (, I can get “[http://192.168.0.100:5001/webui](http://192.168.0.100:5001/webui)” to resolve properly from another computer on the network, but if I navigate into the “Files” section, and click on a JPEG that’s saved there, the UI shows a broken image because it’s trying to load “[http://0.0.0.0:8080/ipfs/Qm](http://0.0.0.0:8080/ipfs/Qm)…”. So it appears to be using the wrong IP address to try and fetch the image.

How can I configure this instance to not use “0.0.0.0” (the “use all IPs” config option), and not “localhost” but use “192.168.0.100”, the IP of the Docker host machine? If I put “/ip4/192.168.0.100/tcp/5001”, as the “API” config setting, then the webui doesn’t work at all (appears to be failing since “192.168.0.100” is not an IP address that the Docker Container can see?).