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

Elevation Image Links Not Working Behind Reverse Proxy #5893

New Issue
Closed
opened 2025-12-29 19:33:56 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:33:56 +01:00
Owner
Copy Link

Originally created by @FreeWillyB on GitHub (Jan 6, 2022).

NetBox version

v3.1.0 Docker

Python version

3.9

Steps to Reproduce

Use a reverse proxy to access the Netbox Docker. View the elevation of the rack and hover over the devices in the rack and you'll notice that the URL is for "localhost:8000" instead of the URL of the reverse proxy.

Commenting out lines #60 and #225 in "/netbox/dcim/api/views.py" and then restarting the docker eliminated the issue.

Expected Behavior

When accessing netbox at https://netbox.mydomain.com, the links for the devices on the elevations should be something like "https://netbox.mydomain.com/dcim/devices/100/"

Observed Behavior

The link instead has a URL of "http://localhost:8000/dcim/devices/100/"

Originally created by @FreeWillyB on GitHub (Jan 6, 2022). ### NetBox version v3.1.0 Docker ### Python version 3.9 ### Steps to Reproduce Use a reverse proxy to access the Netbox Docker. View the elevation of the rack and hover over the devices in the rack and you'll notice that the URL is for "localhost:8000" instead of the URL of the reverse proxy. Commenting out lines #60 and #225 in "/netbox/dcim/api/views.py" and then restarting the docker eliminated the issue. ### Expected Behavior When accessing netbox at https://netbox.mydomain.com, the links for the devices on the elevations should be something like "https://netbox.mydomain.com/dcim/devices/100/" ### Observed Behavior The link instead has a URL of "http://localhost:8000/dcim/devices/100/"
adam closed this issue 2025-12-29 19:33:57 +01:00
adam commented 2025-12-29 19:33:57 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 6, 2022):

Use a reverse proxy to access the Netbox Docker.

This repo does not accept issues for the netbox-docker project. If you believe you've encountered a bug, please open an issue there.

@jeremystretch commented on GitHub (Jan 6, 2022): > Use a reverse proxy to access the Netbox Docker. This repo does not accept issues for the [netbox-docker](https://github.com/netbox-community/netbox-docker) project. If you believe you've encountered a bug, please open an issue there.
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#5893
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?