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

View Layout/Rendering Issues #1925

New Issue
Closed
opened 2025-12-29 17:20:37 +01:00 by adam · 5 comments
adam commented 2025-12-29 17:20:37 +01:00
Owner
Copy Link

Originally created by @mikeloosbrock on GitHub (Aug 9, 2018).

I'm having several Django view layout/rendering issues after upgrading from v2.3.3 to v2.4.2. These display issues are replicated in multiple browsers, on multiple machines. Sample screenshot attached.

Upgrade procedure (per the documentation):
$ cd /opt/netbox
$ git checkout master
$ git pull origin master
$ ./upgrade.sh
$ sudo supervisorctl restart netbox

I also tried this in case it's a python module version compatibility issue:
$ pip install -r requirements.txt --upgrade --upgrade-strategy eager

netbox-render-bug

Originally created by @mikeloosbrock on GitHub (Aug 9, 2018). I'm having several Django view layout/rendering issues after upgrading from v2.3.3 to v2.4.2. These display issues are replicated in multiple browsers, on multiple machines. Sample screenshot attached. Upgrade procedure (per the documentation): $ cd /opt/netbox $ git checkout master $ git pull origin master $ ./upgrade.sh $ sudo supervisorctl restart netbox I also tried this in case it's a python module version compatibility issue: $ pip install -r requirements.txt --upgrade --upgrade-strategy eager ![netbox-render-bug](https://user-images.githubusercontent.com/15373437/43868220-30c1d21a-9b32-11e8-8e96-d6a2be9b8fb6.png)
adam closed this issue 2025-12-29 17:20:37 +01:00
adam commented 2025-12-29 17:20:38 +01:00
Author
Owner
Copy Link

@anhnvme commented on GitHub (Aug 9, 2018):

did you run supervisorctl restart netbox ?

@anhnvme commented on GitHub (Aug 9, 2018): did you run `supervisorctl restart netbox` ?
adam commented 2025-12-29 17:20:38 +01:00
Author
Owner
Copy Link

@mikeloosbrock commented on GitHub (Aug 9, 2018):

Yes, I did indeed restart netbox with supervisorctl. I should have stated that earlier. I've edited my OP to reflect that.

@mikeloosbrock commented on GitHub (Aug 9, 2018): Yes, I did indeed restart netbox with supervisorctl. I should have stated that earlier. I've edited my OP to reflect that.
adam commented 2025-12-29 17:20:38 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 9, 2018):

Your installation is missing a static file named /static/css/base.css. Try running python3 manage.py collectstatic. Please post to the mailing list if you need further assistance with this.

@jeremystretch commented on GitHub (Aug 9, 2018): Your installation is missing a static file named `/static/css/base.css`. Try running `python3 manage.py collectstatic`. Please post to the [mailing list](https://groups.google.com/forum/#!forum/netbox-discuss) if you need further assistance with this.
adam commented 2025-12-29 17:20:38 +01:00
Author
Owner
Copy Link

@mikeloosbrock commented on GitHub (Aug 9, 2018):

I actually tried manage.py collectstatic after my OP and before @jeremystretch's response. The static file /static/css/base.css does exist.

In terms of etiquette, am I supposed to ask about these sorts of things on the mailing list first, and only bring them here if the mailing list decides it's a bug?

@mikeloosbrock commented on GitHub (Aug 9, 2018): I actually tried `manage.py collectstatic` after my OP and before @jeremystretch's response. The static file `/static/css/base.css` does exist. In terms of etiquette, am I supposed to ask about these sorts of things on the mailing list first, and only bring them here if the mailing list decides it's a bug?
adam commented 2025-12-29 17:20:38 +01:00
Author
Owner
Copy Link

@mikeloosbrock commented on GitHub (Aug 10, 2018):

For anyone else who may come across this issue...

The permissions on /opt/netbox/netbox/static/ seemed to have changed after the upgrade such that nginx could no longer serve up content from that directory. After issuing chgrp www-data -R /opt/netbox/netbox/static, nginx could once again access the static files, and the netbox web ui then rendered correctly.

@mikeloosbrock commented on GitHub (Aug 10, 2018): For anyone else who may come across this issue... The permissions on /opt/netbox/netbox/static/ seemed to have changed after the upgrade such that nginx could no longer serve up content from that directory. After issuing `chgrp www-data -R /opt/netbox/netbox/static`, nginx could once again access the static files, and the netbox web ui then rendered correctly.
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#1925
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?