Rack Images not showing.

[ssigle]

I am having an issue with my rack images not showing in Netbox v3.3.6, Python v3.8.10.

I've tried to select Images, and Images and Labels and neither will display my racks. Is there a way to fix this? Or has anyone had a similar issue?

When I click Download SVG, the rack does show in a new window. So it seems there's just an issue with the page.

I've tried creating new racks and I am still having the same issue as well.

[candlerb]

Works for me. Which browser are you using? Can you try opening your browser's developer console and then refreshing the page - do you see any errors in the browser console?

[candlerb]

And just to be clear, the page you're looking at is /dcim/racks/NNN/ ?

Also: the rack image is one of those few places where Netbox web rendering calls back to its own API endpoints. Look at the page source and you should see something like this where the rack image goes:

<object data="/api/dcim/racks/1/elevation/?face=front&amp;render=svg" class="rack_elevation">...</object>

However, the button to "Download SVG" is the same:

<a class="btn btn-outline-primary btn-sm" href="/api/dcim/racks/1/elevation/?face=front&amp;render=svg">
        <i class="mdi mdi-file-download"></i> Download SVG
    </a>

[ssigle]

This is the only issue appearing in the console.

Currently, I am looking at my /dcim/racks/2/ page, but now as I am looking through things.. It's also not showing the images for the cable traces as well.

Yes, I am seeing the and Elements.

[candlerb]

Can you try the "console" tab rather than "issues"? And is there a "network" tab which shows external accesses?

Then you can see whether the /api/dcim/racks/N/elevation/ endpoint is being accessed, and if it is, what the response code is.

[ssigle]

Sorry, I don't exactly know where to go to tell if it is being accessed.. but I can browse to that and it gives me a HTTP 200 OK.

[ssigle]

I'll dig into my webserver settings and see if I am missing something.

[ssigle]

Issue is with my ssl config... You can close this. I just removed the line and I'll work on that later.

Thanks for the help!

[hennning]

@ssigle I have the same issue as you.
What did you do to solve the issue?

I'm running standard docker install, but I'm running it behind a traefik proxy if that makes any difference.

[candlerb]

As was already explained, you need to look in your browser's developer tools:

• in the console, look for Javascript or HTTP errors
• in the network tab, look to see what response you're getting to the /api/dcim/racks/NNN/elevation/?face=front&render=svg request.

Then it should be possible to work out what's going on.

[ssigle]

@ssigle I have the same issue as you. What did you do to solve the issue?

I'm running standard docker install, but I'm running it behind a traefik proxy if that makes any difference.

It ended up being how I setup my SSL config in the webserver. I commented it out for now until I have time to work on it.

[ssigle]

I forgot to add, I am using brave browser.

[ghost]

As @ssigle, I was having the same issue as before. After an extended amount of time, I was able to find a solution to this problem. This solution may help.

So, how did I find the solution?
After reading through the post, and following the @candlerb steps, I noticed that under the Element referring to the object type, I wasn't getting the expected 200 OK status, but a (blocked:other) instead.

Subsequently, I did exactly what @ssigle did to "temporarily solve" his problem, which was to disable SSL:443 under my nginx.conf file. Lo and behold, the problem got solved, so I knew that there was something going on with SSL.

My next step was to enable both HTTP and HTTPS, so that I could login to the netbox by using SSL and Plain-Text.

On one Tab within my Google Chrome, I accessed my netbox using: http://127.0.0.1/. Additionally, on a different Tab, I also accessed my netbox using https://127.0.0.1/

After successfully login into the website, I started comparing both Network Elements to see what was the Response header when attempting to do the API GET, to display the server rack image.

I found out about a header named: X-Frame-Options and here is what I saw:

-For the http connection: X-Frame-Options: SAMEORIGIN
-For the https connection: X-Frame-Options: DENY

It was a curious finding, and after researching the X-Frame-Option and from where this header was coming from, then I traced back the trail back to the ssl.config that I have created to be used alongside my nginx config file when using the Diffie-hellmen group. Inside the ssl_config file, I found this:

$ sudo vim ssl_config.conf

....
add_header X-Frame-Options DENY;
add_header X-Content-Type-Options nosniff;

ssl_dhparam /etc/ssl/certs/dhparam.pem

Bob's your uncle! I commented the line containing: "#add_header X-Frame-Options DENY", reload nginx and the problem finally got solved, the rack images are not being displayed using HTTPS.

[goteamkor]

thank you. i was having the exact same issue. I commented out the same line and started working for me too.
your post should be marked as the answer.