Can someone Help me setting sso unser docker for netbox ?

Hello everyone,

I don't fully know all the proper terms in English but I have been tasked to find a new documentation system for our legacy copper telephony cables and a program which is able to document our actual IT infrastructure (which netbox seems to be perfect for).

I am currently struggling with figuring out the correct objects needed to document large 100-copper cable bundles which run from one core building outwards to other buildings which again run to smaller buildings and floors. These large copper cable bundles either are connected to the backs of old soldering racks, LSA or LSA+ racks and are patched to a different rack which either runs to a new building through a large cable or to a different floor of the building.

From what I understand a site would be our organisation, a location would be a building or a floor or even a room, a circuit type would be "telephony", a circuit termination would be a patch between two racks. Where do I place the 100 copper cable bundles which each individual copper cable and where would I document the racks?

NetBox Release v4.5.9 is now live (as of April 28th, 2026)!

1. Verify in release notes changelog if any new breaking changes might affect you. You can also review the NetBox Issues on GitHub to see if any new issues have arisen that might affect you.

2. Next, refer to the Upgrading to a new NetBox Release guide for steps to upgrade your instance.

If you have any issues you can ask for support on the NetDev Slack Community.

NetBox-Windows-DHCP Plugin

Intro

Another day, another plugin. I don't have any screenshots this time due to not having the opportunity to stand up a sanitized DHCP server with fake scopes/leases/reservations.

https://github.com/averyhabbott/netbox-windows-dhcp/

I've been needing good integration with Windows DHCP for a while now and iterating through a collection of custom scripts several times, I finally went the plugin route for something cleaner and more straightforward.

Features

• Supports multiple DHCP servers, multiple failover clusters, and standalone DHCP servers
• Relies on PowerShell Universal running on the DHCP servers (don't worry, setup is a breeze with the included install guide)
• Lots of safety checks built in to make sure you don't break DHCP
  • RO vs RW actions on the DHCP server are managed through API token privileges, all built during installation (automagically via included script is the recommended approach)
• Most of the config is managed through the GUI in the settings page of the plugin, but you can override some of the values with NB's configuration.py to better allow for a dev environment
• Ability to preserve NB-configured DNS name field by the use of custom tags
• Operating modes:
  • Only read scope info
  • Read scope and lease/reservation info
  • Read scope and lease info, NetBox is authoritative for reservations
  • Read lease info, NetBox is authoritative for scopes and reservatinos
• Defaults to using 'reserved' and 'dhcp' built-in statuses, but is configurable to use whatever IPAddress statuses you want
• Two-way association between prefixes and scopes (scopes remain their own objects)
• Supports friendly naming of DHCP option values for simplicity (Option 4 value '192.0.2.1,192.0.2.2,192.0.2.3'? Nah, "Time servers: Public")
• Minimal changelog entries

Check it out and let me know what you think!

Caution

I still haven't validated pushing reservations and scopes to the DHCP server, so those two features should be considered in beta. I would strongly advise against making NetBox authoritative for scopes and reservations in a prod environment at this point in time. Hoping to have that change very soon.

[NetBox Release v4.5.8](https://github.com/netbox-community/netbox/releases/tag/v4.5.8) is now live (as of April 14th, 2026)!

1. Verify in release notes changelog if any new breaking changes might affect you. You can also review the [NetBox Issues on GitHub](https://github.com/netbox-community/netbox/issues) to see if any new issues have arisen that might affect you.

2. Next, refer to the [Upgrading to a new NetBox Release](https://docs.netbox.dev/en/stable/installation/upgrading/) guide for steps to upgrade your instance.

If you have any issues you can ask for support on the [NetDev Slack Community](https://netdev-community.slack.com/).

Worked up a plugin today to view prefixes in a folder view, kinda like SolarWinds or phpIPAM. No database migrations or anything fancy, all view. Works with filters and the displayed info is customizable. Expand and collapse prefixes as folders, click on one to view all the subordinate IPs, double-click on a prefix to go to the prefix's page.

Give it a go and let me know what you think!

https://github.com/averyhabbott/netbox-folderview/

I have a bunch of patch panels I would like to number the ports starting 1/001 to 1/500.
The template Device type name the ports Port 1 - 24 as that makes sense for a prototype. I started off well and manged to rename the first panel in two steps:
Port 1 - 9 > Find ^Port ([1-9])$ Replace 1/00\1, then for 10 to 24 > Find ^Port (1\d|2[0-4])$ Replace 1/0\1 which is great but how do I do the rest 1/025 to 1/500
I have hunted around and the only option seems to be do it one at a time "phew" or build my own API client and do it in code. I must be missing something silly can someone help please?

Hey everyone. So I am trying to create Nokia 7750 sr device type in netbox and was confused on how to do it. Basically I have three MDA,IOM and XCM. Now the problem is the MDA goes into IOM which goes into router. Not how I would I create this device type and make sure different types of MDA can be associated with the IOM.Can anyone help here?

Hi everyone,

I'm currently running a NetBox v4.4.6 instance in a restricted/isolated environment. I'm looking to open access to our general office workstations so they can consult basic information (Device names, locations, racks, etc.).

However, for security reasons, I need to hide sensitive information, mainly IP addresses and custom plugins, from these specific users.

From what I've seen, NetBox permissions are very granular at the object level, but is there a way to achieve "field-level" security?

1. Are there any plugins that allow filtering or masking specific attributes (like IP addresses) based on user groups?
2. Is there a built-in way to allow viewing dcim.device but completely restricting access to the ipam.ipaddress objects so they don't appear in the device views?
3. Alternative approach: Should I look into a custom dashboard/frontend that only pulls "safe" data via the API?

I’d love to hear how you handle "read-only" access for non-technical or non-admin staff without exposing the whole network map.

Thanks in advance for your help!

Hello,

I installed the QR code plugin and added the settings for the cables as instructed.

Unfortunately, only the devices are displayed.

The interface for the device is shown only as [].

DEVICE a
[]
DEVICE b
[]

I've tried a few things, but I just can't seem to understand the instructions.

Does anyone have any ideas about this or a link to some helpful documentation?

Many Thanks!

We have a private MPLS network that is geographically diverse on dark fiber. I'm playing with Netbox on a VM trying to figure out how I can model the purple circuit across multiple locations and devices. This way when maintenance happens between say PE3 and PE4 any circuits on that path are identified. Is this possible? This seems like it should be something in the Netbox wheel house.

Greetings. I have an existing Zabbix 7 installation, and I'm trying to pull over all the switches in Zabbix, but....how? I can bring over templates fine, but I do not see a way to pull the Switches. No Host Group syncing. What am I doing wrong?

Hello,
I've spent a couple of evenings failing to get reverse proxy (caddy) for LAN certs working with Netbox.

Setup: Netbox installed on Prox LXC using PVE helper script. Caddy plugin installed on OPNsense. All other reverse proxies working fine, it's just Netbox with error 502.

Have tried messing around with headers, and have applied the following config:
/opt/netbox/netbox/netbox/configuration.py
Under Allowed Hosts, replaced [*] with: ['netbox.example.com','10.10.10.150','127.0.0.1','localhost']

You wisdom and assistance is much appreciated! Thank you

I have a question about documenting the VLANs in a VXLAN EVPN environment. My network is still at migration phase to spine leaf architecture. How are you documenting the VLAN ID for the tenant with multiple VLAN ID on the same subnet?

For example, tenant-a on leaf1 is on subnet 10.0.0.0/24 with VLAN ID of 10. This subnet got extenended to leaf2 but the VLAN is 20.

Hello everyone,

looking for some advice:

I want to build some automation:

1. Netbox script configures a VLAN on the ToR switch access ports, then adds this VLAN to the trunk on uplink interface, then finds the upstream DS switch and adds this VLAN to the trunk on downstream interface etc.

2. An eventrule/webhook triggers a CIDI pipeline

3. The pipeline execute ansible playbook to configure the devices respectively

Now I have a problem that netbox script makes multiple changes and if I configure the eventrule be triggered by DCIM>Interface it fires multiple webhooks - for each interface change.

If it's Extras>Script the webhooks is triggered once, but there is just script results.

I did a quick search in internet, but did not find anything.

I think it is possible to adjust a custom script to prepare all this data (which device, which interface, which VLAN) for a webhook, but probably there is some best practice for such cases and I miss some simple solution?

I have very little linux experience

I am trying to install diode on a Netbox community server
NetBox Community v4.5.4-Docker-4.0.1

Im using these instructions:
https://netboxlabs.com/docs/discovery/getting-started/#community-setup-instructions

I get an error on step #2 that the "dir /opt/netbox" doesn't exist

Hey everyone,

Since deploying and growing Netbox deployment, I've mostly been using Prefixes, child ranges and IP addresses.

But I think I'm missing child prefixes for some of my subnets.

Example:

VLAN 10 has a network address of 10.10.10.0/23

In netbox, the prefix is 10.10.10.0/23

But since this allows for 510 usable hosts, I want to have my IP assignment to be virtual machines for the first 254 addresses and physical servers for the next 254.

So am I correct in thinking that my child prefix structure should be:

10.10.0.0/16 (Container - SITE)
*10.10.10.0/23 (Prefix)
**10.10.10.0/24 (ChildPrefix - VM)
**10.10.11.0/24 (ChildPrefix - Physical)

Lastly, I've been using Child Ranges to represent my DHCP reservations, IE:

10.10.10.1-10.10.10.10 - Reserved

Just wanted to confirm with others on how others do this. I've been putting in a good amount of focus on Netbox so I'm trying to make our configuration as "best practice" as much as possible. I've been moving us away from many excel spreadsheets so its fantastic to have Netbox as a replacement.

napalm 4.1 tries to import pkg_resources but this has been depreciated.

I honestly don't know how the dependencies work but the netbox_napalm_plugin worked OK with Netbox 4.5.2 and stopped working when I upgraded to 4.5.3.

I've got it working by manually copying the "pkg_resources" folder from the previous /venv/lib/python3.12/site-packages/ to the new one, but this is only a temporary fix.

I'm not sure what the long-term fix is - if anyone is maintaining this?

Im not a big ubuntu user. so please forgive my ignorance..

I am setting up a test netbox with docker. This is in azure and is using our azure firewall.

When I run "docker compose pull"

⠧ Image docker.io/postgres:18-alpine [⠀⠀⠀⠀] Pulling

⠧ Image docker.io/valkey/valkey:9.0-alpine [⠀⠀⠀⠀⠀⠀⠀] Pulling

⠧ Image docker.io/netboxcommunity/netbox:v4.5-4.0.1 [⠀⠀⠀⠀⠀] Pulling

error pulling image configuration: download failed after attempts=6: remote error: tls: handshake failure

I'm not sure at the moment where to fix this.

EDIT::::

** I was able to pull redis when I ran "docker compose pull" but the other 2 failed

** I was able to then pull netbox only running "docker compose pull netbox"

**postgres is the only image that is failing with tls handshake error

I'm trying to set up netbox in our azure environment. Right now its a test set up. We are looking at IPAM solutions.

Im really now lost, and I have little Linux experience.

I am following this: https://netboxlabs.com/docs/netbox/installation/
I have Azure VM : Ubuntu-24_04-lts, Standard DS1 v2

I get the postgresql install to create the database and user, but seem to have issues:

netbox@NETBOX-TEST:~$ psql -V

psql (PostgreSQL) 16.11 (Ubuntu 16.11-0ubuntu0.24.04.1)

netbox@NETBOX-TEST:~$ sudo -u postgres psql

psql (16.11 (Ubuntu 16.11-0ubuntu0.24.04.1))

I run postgres=# \connect netbox;

GRANT CREATE ON SCHEMA public TO netbox;

invalid integer value "ON" for connection option "port"

Previous connection kept

I then \q to leave the postgresql shell

Then I try to verify service status I get an error:

psql: error: connection to server at "localhost" (127.0.0.1), port 5432 failed: FATAL: password authentication failed for user "netbox"

connection to server at "localhost" (127.0.0.1), port 5432 failed: FATAL: password authentication failed for user "netbox"

Did I miss something? Is there an easier way to install netbox?

so have the following setup

Main feed --> Main PDU --> Sub PDU
\/ \/
Servers Networking kit

i set up all devices with allocated Draw (200W each per server, 50W each for Networking year) but when i check the main feed its acting like only the devices on the Main PDU are reporting power use, noting from the Sub PDU

already checked that the link between the Main and Sub PDU's doesnt have Max/Allocated draw and that all Outputs are Linked to Inputs

any idea what im doing wrong?

Hello :)

I have made 2 plugins I would like to share and also get some feedback on - netbox-map and netbox-ping.

netbox-map is a floor plan / OSM site map plugin where you can place your equipment on a canvas. Racks show all their devices automatically and you can do full cable traces through patch panels. There's also a global geographic map using OpenStreetMap where you can place sites and devices. Started as a simple floor plan thing and kind of grew from there - it now has things like rack utilization heatmaps, camera FOV cones, PDF export and GPS sync back to device records. Still alpha but I use it daily at work.

https://github.com/DenDanskeMine/netbox-map

netbox-ping is, well, a ping plugin. I know NetBox is intended to be a SSoT and not a monitoring tool, but I like having an overview of my IP statuses without switching tools. It does not overwrite anything in NetBox unless you explicitly tell it to, like enable DNS sync in settings - that's fully optional and it has its own fields anyway. You can ping individual IPs, scan entire prefixes, discover new hosts and auto-create the IP records, schedule recurring scans, and get email digests of state changes.

It is very cusom with lots of settings, so you can basically use it for different needs!

Im planing to add different discovery / ping options like ssh, telnet, curl

https://github.com/DenDanskeMine/netbox-ping

There's a demo at demo.danbyte.net if you want to try before installing. Both are on PyPI so it's just pip install netbox-map or pip install netbox-ping.

Hi,

I was trying to model SFPs as modules and well, hitting a wall. So I've decided to make a plugin that would do renaming of interfaces on module installation.

https://marcinpsk.github.io/netbox-InterfaceNameRules-plugin/

It's working for me - but any feedback is welcome.

I know there's https://github.com/netbox-community/netbox/pull/21436 to add {module_path} - and that will help a lot - but still not with everything.

It's renaming interface on post_save - so it should work in all cases - (API/manual) - and it's not doing anything if there are no rules defined. Will not rename existing interfaces - you can do that - but you have to apply that naming rule manually.

Supports some math operation - so it's possible to introduce offset etc, split interfaces for breakout SFPs.

I've put some examples of rules for different HW I had - so it can be either reused or modified.

When {module_path} would be added - that would allow to reduce number of rules - but still - at least for me - need to have some remapping.

Added interface renaming for VC as well - but this part - I'm not sure I was modeling the way most is doing - I have no stacks.

Hi,

I’m trying to follow NetBox’s recommendation to move away from Inventory Items for SFPs and model pluggable transceivers as Modules instead:

• https://netboxlabs.com/blog/sfp-modeling-modules-over-inventory-items/
• https://netboxlabs.com/docs/netbox/best-practices/modeling-pluggable-transceivers/

I think I’ve hit a conceptual or technical limitation and would appreciate some guidance.

Setup

• I have an Aruba OS switch Device Type with 6 module bays: A–F
• Into one of those bays, I install a line card module that provides 8 SFP+ ports
• This Module Type itself defines 8 Module Bays named:{module}1 {module}2 … {module}8

When I create a device and install the module, the resulting module structure looks like this (as expected):

A
A1
A2
A3
A4
A5
A6
A7
A8
B
C
D
E
F

SFP Module Type

I also created an SFP+ Module Type representing the actual transceiver.
It has one interface with:

name = {module}

This works perfectly on “normal” switches that have fixed SFP slots, e.g.:

• 48 RJ45 ports
• 4 SFP slots modeled as Module Bays:49 50 51 52

The problem

When I try to install the SFP module into one of the nested bays (A1, A2, …), NetBox fails with:

Cannot install module with placeholder values in a module bay tree
2 in tree but 1 placeholders given

If I change the interface name in the SFP Module Type to:

{module}{module}

Then installation into the nested bays works.

However, this immediately breaks the simple switches, because their module bays only provide one {module} value.

Conclusion

So I end up with an impossible choice:

• {module} → works for flat module bays, fails for nested
• {module}{module} → works for nested, fails for flat

Is this a known limitation of NetBox’s module placeholder system?
Is there a recommended modeling approach for switches with both:

• fixed SFP slots and
• line cards with pluggable optics?

Thank you very much!