# Our discourse Images are not lightboxed

**URL:** <https://meta.discourse.org/t/our-discourse-images-are-not-lightboxed/84004>\
**Category:** Product Support\
**Created:** [27 maart 2018 om 23:47 UTC](https://meta.discourse.org/t/our-discourse-images-are-not-lightboxed/84004 "2018-03-27T23:47:09Z")\
**Posts on this page:** 1\
**Showing post:** 29

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [8 juli 2020 om 04:44 UTC](https://meta.discourse.org/t/our-discourse-images-are-not-lightboxed/84004/29 "2020-07-08T04:44:44Z")

</div>

> [@codinghorror](#):
>
> I agree, can launcher be modified to warn about this or block it next week

This appears to be specific to non-standard installs that simultaneously:

- Didn’t use `./discourse-setup` and created a yml file manually

- Are using a reverse proxy

- This reverse proxy is magically configured using a docker container name

I’d advise against changing the current deterministic container name for everyone to address this corner case, unless it can also happens by simply adding an extra dot to the yml file name.

---

_[View the full topic](https://meta.discourse.org/t/our-discourse-images-are-not-lightboxed/84004)._
