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

Home page doesn't load post power failure #6688

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

Originally created by @svetlinski on GitHub (Jul 19, 2022).

NetBox version

v3.1.6

Python version

3.8

Steps to Reproduce

Open the home page

Expected Behavior

Home page to load without issues

Observed Behavior

Had a power outage recently, since server is back, I am unable to get to the main page at all.
Page doesn't load, displays an error about CSS files:
image
I have tried the below:
Changing the nginx user to www-data; changing permissions for the media and static folders to 775, 777 for the www-data user; restarting nginx, netbox and netbox-rq processess
Changing the nginx user to root; changing permissions for the media and static folders to 775, 777 for the www-data user; restarting nginx, netbox and netbox-rq processess
Changing the nginx user to netbox; changing permissions for the media and static folders to 775, 777 for the www-data user; restarting nginx, netbox and netbox-rq processess
I have also tried restoring 2 previous backups, it makes no difference at all.
I read all the available discussions online and they didn't help, especially not the one about chown of the folders. Now, I am stuck for any other ideas.
Any help is more than welcome.
Thanks in advance.

Originally created by @svetlinski on GitHub (Jul 19, 2022). ### NetBox version v3.1.6 ### Python version 3.8 ### Steps to Reproduce Open the home page ### Expected Behavior Home page to load without issues ### Observed Behavior Had a power outage recently, since server is back, I am unable to get to the main page at all. Page doesn't load, displays an error about CSS files: ![image](https://user-images.githubusercontent.com/99681269/179854435-7c01f268-5ac0-482d-90fd-d9ddeefd8116.png) I have tried the below: Changing the nginx user to www-data; changing permissions for the media and static folders to 775, 777 for the www-data user; restarting nginx, netbox and netbox-rq processess Changing the nginx user to root; changing permissions for the media and static folders to 775, 777 for the www-data user; restarting nginx, netbox and netbox-rq processess Changing the nginx user to netbox; changing permissions for the media and static folders to 775, 777 for the www-data user; restarting nginx, netbox and netbox-rq processess I have also tried restoring 2 previous backups, it makes no difference at all. I read all the available discussions online and they didn't help, especially not the one about chown of the folders. Now, I am stuck for any other ideas. Any help is more than welcome. Thanks in advance.
adam closed this issue 2025-12-29 19:43:59 +01:00
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#6688
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?