starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

The links in the "Elevation" part are broken #4982

New Issue
Closed
opened 2025-12-29 19:22:50 +01:00 by adam · 3 comments
adam commented 2025-12-29 19:22:50 +01:00
Owner
Copy Link

Originally created by @quentindavid on GitHub (Jun 9, 2021).

NetBox version

v2.11.6

Python version

3.6

Steps to Reproduce

  1. Go in Elevation menu
  2. Point on any device within a rack and note it's link URL

Expected Behavior

You should see the reverse proxy URL ie https://reverse-proxy-url/dcim/devices/556/

Observed Behavior

http://ip_of_backend/dcim/devices/556/

In the devices list, the links are working properly.

Originally created by @quentindavid on GitHub (Jun 9, 2021). ### NetBox version v2.11.6 ### Python version 3.6 ### Steps to Reproduce 1. Go in Elevation menu 2. Point on any device within a rack and note it's link URL ### Expected Behavior You should see the reverse proxy URL ie https://reverse-proxy-url/dcim/devices/556/ ### Observed Behavior http://ip_of_backend/dcim/devices/556/ In the devices list, the links are working properly.
adam closed this issue 2025-12-29 19:22:51 +01:00
adam commented 2025-12-29 19:22:51 +01:00
Author
Owner
Copy Link

@quentindavid commented on GitHub (Jun 9, 2021):

Same issue when you are in the "Racks" page, you select a rack. Then you have a visual illustration of the rack, and the link are wrong when you click on any device within the rack.

@quentindavid commented on GitHub (Jun 9, 2021): Same issue when you are in the "Racks" page, you select a rack. Then you have a visual illustration of the rack, and the link are wrong when you click on any device within the rack.
adam commented 2025-12-29 19:22:52 +01:00
Author
Owner
Copy Link

@quentindavid commented on GitHub (Jun 9, 2021):

Well, it seems to be fixed if the value "ALLOWED_HOSTS" in the configuration page corresponds to the reverse-proxy front URL.

Which is still weird is that all URL are not consistent.

@quentindavid commented on GitHub (Jun 9, 2021): Well, it seems to be fixed if the value "ALLOWED_HOSTS" in the configuration page corresponds to the reverse-proxy front URL. Which is still weird is that all URL are not consistent.
adam commented 2025-12-29 19:22:52 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 9, 2021):

NetBox doesn't inherently know what hostnames for which it may receive requests; this information must be forwarded to it by the HTTP frontend (e.g. nginx or Apache) in order to generate correct absolute URLs. See our sample nginx and Apache configs for reference.

Most URLs in the UI are relative to the path root (/). The rack elevations use absolute links because each elevation is actually an SVG image.

@jeremystretch commented on GitHub (Jun 9, 2021): NetBox doesn't inherently know what hostnames for which it may receive requests; this information must be forwarded to it by the HTTP frontend (e.g. nginx or Apache) in order to generate correct absolute URLs. See our [sample nginx and Apache configs](https://github.com/netbox-community/netbox/tree/develop/contrib) for reference. Most URLs in the UI are relative to the path root (`/`). The rack elevations use absolute links because each elevation is actually an SVG image.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#4982
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?