NeoAnd/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2025-07-16 04:02:52 -06:00
Code Issues Actions 7 Packages Projects Releases Wiki Activity

Updated Common Issues (markdown)

Jeremy Stretch 2021-06-14 14:23:11 -04:00
parent aa4b409a4c
commit cea731de16
1 changed files with 14 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
Common-Issues.md

@ -1,6 +1,7 @@
* [ProgrammingError Exception Following a Recent Upgrade](#programmingerror-exception-following-a-recent-upgrade)
* [502 Bad Gateway Error When Calling NAPALM API](#502-bad-gateway-error-when-calling-napalm-api)
* [Rack Elevations Do Not Display](#rack-elevations-do-not-display-v27)
* [Rack Elevation Links use Wrong Domain](#rack-elevation-links-use-wrong-domain)
## ProgrammingError Exception Following a Recent Upgrade
@ -32,4 +33,16 @@ If the direct API call is successful but the images don't appear on the rack pag
### Recommended Solution
Inspect the configuration of your HTTP daemon (e.g. nginx or Apache) and remove any statements which statically set the `X-Frame-Options` header.
Inspect the configuration of your HTTP daemon (e.g. nginx or Apache) and remove any statements which statically set the `X-Frame-Options` header.
## Rack Elevation Links use Wrong Domain
### What's Happening
NetBox runs as a [WSGI application](https://en.wikipedia.org/wiki/Web_Server_Gateway_Interface) behind front-end HTTP server (e.g. Apache or nginx), which serves as a reverse proxy. Because NetBox doesn't have direct access to the raw HTTP request, it relies on the HTTP server to forward important details, such as the requested host and the HTTP protocol in use. If these details are not correctly forwarded to NetBox, NetBox will be unable to render absolute URLs (those which start with `https://`, as opposed to a relative URL).
For most hyperlinks, NetBox uses relative links. However, in a few specific instances, such as when rendering rack elevations, NetBox must use absolute URLs. This is because the rack elevations are actually embedded SVG images: Since these images might also appear outside the NetBox UI, absolute URLs must be used. If the HTTP frontend has not been configured to correctly relay the necessary information about the incoming HTTP request, these links will use the IP address of the backend service rather than the requested host or IP address.
### Recommended Solution
This is a simple fix. Just ensure that your HTTP server is sending the `X-Forwarded-Proto` and `X-Forwarded-Host` HTTP headers on requests being proxied via WSGI. Example configurations for both [nginx](https://github.com/netbox-community/netbox/blob/master/contrib/nginx.conf) and [Apache](https://github.com/netbox-community/netbox/blob/master/contrib/apache.conf) are included for your reference.