Netbox GUI messed up a few minutes after accessing it for the first time

[it-nugget]

Hi all,

I have installed and configured Netbox successfully and navigated properly to the IP address of the server where it is hosted to access it. In the beginning everything was working properly, so I was clicking and playing around, but after a few minuted the GUI became messed up, without any changes from my side.

Please have a look at the image provided below and advise.

Thank you.

[it-nugget]

Apologies, forgot to mention the version, that would be NetBox v2.0.2.

Thank you.

[dcam...@digitalocean.com]

That looks like your browser is failing to load the css for the page. Does it clear up when you force a refresh of the page?

If not, you can get more information about the error by opening up the developer console in your browser. The hotkey is Option-Command-I or Alt-Control-I depending on your OS, if I recall correctly. Then open the "network" tab and refresh. The line for the css file should be red.

Are you seeing this error with a full install including Apache or Nginx? The server logs for either of those might have clues for why the css is failing too. When you install in that way, the web server (i.e. Apache or Nginx) are serving the css directly.

[it-nugget]

You are right, you have pointed me to the correct direction and I just realized that the path in the apache conf. does not point to the correct Netbox path, because when extracted, the files are located in netbox-2.0.2 and not netbox.

Thank you though, much appreciated.

[Jivor 50]

I am having the same issue. Mine shows the correct version at the bottom of the screen. I have went into /etc/supervisor/conf.d and sudo nano netbox.conf to point to the latest version I am using (2.0.1) and my gunicorn_config.py is also pointing to the latest version but I am getting the same view of server screen as posted in thread. I have completed sudo service supervisor restart and also sudo supervisorctl restart netbox. Using nginx. Still same screen. Not sure what to do next? Any help is appreciated.

[dcam...@digitalocean.com]

Hi Jivor

Thinking of a bullet list of things to check:

• Have you run the collectstatic task[1] with the manage.py script? When you do this it prints the path where it is collecting the static files.
• Does this path match the alias line in your nginx config[2]? This is where the previous poster has an issue because they had extracted from a tarball so one segment of the path was different.
• Are you hitting the nginx instance with your browser, and not the backend python processes directly? In the documented install the difference is the port: http://localhost vs http://localhost:8001
• Which error do you get if you try to hit a static resource directly? For example http://localhost/static/img/netbox_logo.png should give you the netbox logo. If you do see an error for this url, then the error itself and the nginx logs may give more information.

At this point it is more an nginx issue and somewhat out of the scope of this group. File permissions are something to watch out for:

http://stackoverflow.com/questions/6795350/nginx-403-forbidden-for-all-files

[1] https://netbox.readthedocs.io/en/stable/installation/netbox/#collect-static-files

[2] https://netbox.readthedocs.io/en/stable/installation/web-server/#option-a-nginx