# Lightbox not showing up on uploaded images after update

**URL:** <https://meta.discourse.org/t/lightbox-not-showing-up-on-uploaded-images-after-update/73009>\
**Category:** Self-hosting\
**Created:** [2017年十月29日 17:25 UTC](https://meta.discourse.org/t/lightbox-not-showing-up-on-uploaded-images-after-update/73009 "2017-10-29T17:25:24Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![ravor-org](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ravor-org/32/120172_2.png) [@ravor-org](https://meta.discourse.org/u/ravor-org)\
**Post date:** [2018年三月28日 15:31 UTC](https://meta.discourse.org/t/lightbox-not-showing-up-on-uploaded-images-after-update/73009/12 "2018-03-28T15:31:17Z")

</div>

I’ve just moved my docker image from a dedicated server to the outer proxy. The outer nginx is now connecting through sockets instead of forwarding https. Problem still persists. I’m still receiving errors like this (which seem to be issue):

```
Can't reach '/uploads/default/original/1X/988629194890bf9b48b914c8fe910e15c4ac1d27.jpg' to get its dimension.

```

The images are valid and accessible, so whats creating the issue here?

EDIT: I’ve dug a little deeper and added some debugging to `get_size` within the `lib/cooked_post_processor.rb` and found that this method is acquiring the images by http(s) instead of grabbing it directly from the filesystem. There was an DNS-misconfiguration within our DMZ-setup, so the FastImage lib could not access the files.

Could you extend `lib/cooked_post_processor.rb` to use the filesystem instead of http(s) if no external location (such as Amazon S3) is used? For my understanding it doesn’t make sense to download the image if it’s already stored on the server already? 😊

---

_[View the full topic](https://meta.discourse.org/t/lightbox-not-showing-up-on-uploaded-images-after-update/73009)._