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

Rack Elevations mapping issue to attached devices #6689

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

Originally created by @MatthewKahle on GitHub (Jul 20, 2022).

NetBox version

v3.2.5

Python version

3.8

Steps to Reproduce

Under the tab 'Rack Elevations' all the assets mapped to a Rack contains old IP address and non domain/URL if setting a new IP on the host of netbox.

Expected Behavior

When resetting my netbox instance to a new IP address, and adding a domain name. All links should work with new IP address or domain name.

Observed Behavior

When I first install netbox, I installed on a host that had DHCP configured. When I statically set to a different IP address that I wanted, I noticed that the assets that can be clicked on in rack view 'Rack Elevations' contained the old IP which the page will time out since that IP address is no longer in use.

Originally created by @MatthewKahle on GitHub (Jul 20, 2022). ### NetBox version v3.2.5 ### Python version 3.8 ### Steps to Reproduce Under the tab 'Rack Elevations' all the assets mapped to a Rack contains old IP address and non domain/URL if setting a new IP on the host of netbox. ### Expected Behavior When resetting my netbox instance to a new IP address, and adding a domain name. All links should work with new IP address or domain name. ### Observed Behavior When I first install netbox, I installed on a host that had DHCP configured. When I statically set to a different IP address that I wanted, I noticed that the assets that can be clicked on in rack view 'Rack Elevations' contained the old IP which the page will time out since that IP address is no longer in use.
adam added the type: bugstatus: revisions needed labels 2025-12-29 19:43:59 +01:00
adam closed this issue 2025-12-29 19:43:59 +01:00
adam commented 2025-12-29 19:44:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 20, 2022):

Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

@jeremystretch commented on GitHub (Jul 20, 2022): Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.
adam commented 2025-12-29 19:44:00 +01:00
Author
Owner
Copy Link

@bkakakym commented on GitHub (Jul 22, 2022):

I have same problem:
Netbox version 3.2.7
Python version 3.9.9

I have such network structure:
Reverse_proxy host( with Nginx listening white IP address and ssl with a domain name attached to it) <> Netbox host(with nginx reverse proxyng to gunicorn port) with a local(gray IP address)

In configuration.py I have ALLOWED_HOSTS = ['example.com', '192.168.25.21']

in rack overview and in rack elevations all url`s to device are using gray ip like http://192.168.25.21/dcim/devices/304/ - non like expected https://example.com/dcim/devices/304/

@bkakakym commented on GitHub (Jul 22, 2022): I have same problem: Netbox version 3.2.7 Python version 3.9.9 I have such network structure: Reverse_proxy host( with Nginx listening white IP address and ssl with a domain name attached to it) <> Netbox host(with nginx reverse proxyng to gunicorn port) with a local(gray IP address) In configuration.py I have ALLOWED_HOSTS = ['example.com', '192.168.25.21'] in rack overview and in rack elevations all url`s to device are using gray ip like http://192.168.25.21/dcim/devices/304/ - non like expected https://example.com/dcim/devices/304/
adam commented 2025-12-29 19:44:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 22, 2022):

This is a configuration issue. Please see this answer in the wiki, and reference the installation instructions for the correct configuration.

@jeremystretch commented on GitHub (Jul 22, 2022): This is a configuration issue. Please see [this answer](https://github.com/netbox-community/netbox/wiki/Common-Issues#rack-elevation-links-use-wrong-domain) in the wiki, and reference the installation instructions for the correct configuration.
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 status: revisions needed type: bug
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#6689
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?