Version 1.0.0 behind Traefik reverse proxy does not serve static files

[ziggekatten]

Trying to get the new version running behind Traefik on Docker, where i use http://server/ipam/ url for Netbox

Now, in earlier versions, I had a nginx.conf with adoption to the BASE_PATH=ipam/ in Netbox ENV

Since nginx is removed i favor for nginx-unit, i suspect there is some config issue on my side. Anyone that have done 1.0 behind Traefik?

[ziggekatten]

And I found oout what is happening.

The section in nginx-unit.json appends the BASE_PATH to the share statement. Using BASE_PATH=netbox and a nginx-unit.json config with below works:

"routes": [
{
"match": {
"uri": "/netbox/static/*"
},
"action": {
"share": "/opt/netbox"
}
}

How on earth do i get nginx unit not to behave like that? We use various URLs and base paths http://server/ipam-dev, http://server/ipam-test ,http://server/ipam-prod) etc, and was very simple with the old nginx.conf as a docker config for each instance. Cant find to set Unit to use a specific directory

[ziggekatten]

FYI, I ended up with adding a Traefik rule n my deployment, so that I still use ngninx and a shared static folder. Only solution I found to the issue

[TheNetworkGuy]

FYI i'm struggling with the exact same issue. Running netbox-docker behind a reverse proxy with URL test123.org.local/netbox. Setting the BASE_PATH does not work and results in a static media failure.

After manually adjusting the nginx-unit.json file in the container i'm unable to fix the situation. I guess i'll revert back to 0.27 but this is a real shame.

If any of the maintainers need extra information in regards to configuration or logs etc i would happy to assist. I'm not that confident with nginx-unit files so its a bit difficult for me to make a final solution.

[ziggekatten]

I removed the static serving from unit, added a traditional ngninx container for static serving, and mount a shared nfs resource for static files in the netbox containers.

So, I still use unit on the netbox containers, since it's WAY more stable than earlier implementation with gunicorn. Especially under load where api calls would give erratic 500 errors, we no longer have these issues.

[7oku]

We actually just faced the same issue and found a pretty simple solution:

In docker-compose.yml disable traefik for the netbox worker:

  netbox-worker:
    <<: *netbox
    depends_on:
    - redis
    entrypoint:
    - /opt/netbox/venv/bin/python
    - /opt/netbox/netbox/manage.py
    command:
    - rqworker
    ports: []
    deploy:
      labels:
        - traefik.enable=false

After nginx is removed you have 2 endpoints which traefik is loadbalancing to: the netbox container and the netbox-worker container. These both however are constructed from a template and your traefik rules are applied to both of them resulting in both of them to be targeted by traefik, while only the netbox container serves the files.

Disabling trafik and thus overriding the templated rules directs all traffic to the netbox container and things work like expected.

[s0p4L1n3]

@rock7632 I’ll give you my full docker compose file on Monday when I get back to my computer 👍

[rock7632]

@s0p4L1n3 Thanks

[s0p4L1n3]

@rock7632 https://github.com/s0p4L1n3/netbox-docker-traefik-TLS/blob/main/docker-compose.yml

[rock7632]

Thanks. Let me try it out

[rock7632]

@s0p4L1n3 This worked for me. Thank you so much!

[ziggekatten]

Did anyone succeed with this? The suggestion to disable traefik did nothing. I never got it working, and with the latest 1.4 version I'm unable to use a shared volume for static files as the required user 101 have no write permissions on my NFS volume. This Unit stuff stinks big time

[kale1d0code]

I've been trying a few things to get netbox to work with traefik

as well as the above suggestion for disabling traefik on the worker
I also tried using the stripprefix middleware which removes the base_path before sending it onto the netbox container

services:
  netbox:
  ...
  labels:
  ...
  - 'traefik.http.middlewares.<MIDDLEWARE_NAME>.stripprefix.prefixes=/netbox'
  - 'traefik.http.routers.netbox.middlewares=<MIDDLEWARE_NAME>@docker,...'
  ...

this fixes the static file warning and I can get to the UI
but this then causes any part of the app you try to go to serve a netbox 404 page.

hoping this is something to go on

next thing I'm going to try is seeing if I can get the middleware only to run on static assets

[sfulham]

I'm also getting the same issue, but I'm proxying it with a subdomain, rather than a path, and I get the same issue. Although, according to the network tab in Chrome, two of the static assets load, and then the rest timeout with a 504. Any ideas?

[courtland]

I ran into this as well today. The problem is that the django application is aware of BASE_PATH however the static assets and nginx-unit are not. I worked around this by using a replacepathregex rule in Traefik in addition to the Router rule that has the PathPrefix. For example, replacing /netbox/static with /static ensures that nginx-unit routes static asset requests correctly, and the app URL/routes are left alone.

I would think changing nginx-unit config to include the desired path prefix in the static route would also work.

[courtland]

FWIW this is also discussed in #650 with similar resolution / workaround options.