# Images not showing because relative asset path in WYSIWYG content

**URL:** <https://discourse.getcockpit.com/t/images-not-showing-because-relative-asset-path-in-wysiwyg-content/1049>\
**Category:** Support\
**Created:** [October 7, 2019, 9:53pm UTC](https://discourse.getcockpit.com/t/images-not-showing-because-relative-asset-path-in-wysiwyg-content/1049 "2019-10-07T21:53:40Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![pauloamgomes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.getcockpit.com/pauloamgomes/32/48_2.png) [@pauloamgomes](https://discourse.getcockpit.com/u/pauloamgomes)\
**Post date:** [October 8, 2019, 4:24pm UTC](https://discourse.getcockpit.com/t/images-not-showing-because-relative-asset-path-in-wysiwyg-content/1049/4 "2019-10-08T16:24:55Z")

</div>

It’s not a good practice to store the full image path in the field (what happens if you need to change the domain?)

Is your static website served by you (e.g. using nginx or apache)?  
If so, you can setup some rewrite rules that will serve the static images, something similar to:

```auto
location /storage/ {
  root /var/www/cockpit/storage;
}

```

---

_[View the full topic](https://discourse.getcockpit.com/t/images-not-showing-because-relative-asset-path-in-wysiwyg-content/1049)._