Trying to add a Config Revision (GUI) throws a server error page

[OdieArbuckle]

Deployment Type

Self-hosted

NetBox Version

v4.3.3

Python Version

3.12

Steps to Reproduce

Upgrade from v3.7.2 > v4.3.3
I tried to add a config revision via Admin > Configuration History > Add
I intended to put netbox in maintenance mode but it threw a server error page, clicking the Add button.

Expected Behavior

Open a new config revision, being able to edit the config revision and save it.

Observed Behavior

<class 'django.template.exceptions.TemplateDoesNotExist'>

django/forms/widgets/number.html

Python version: 3.12.10
NetBox version: 4.3.3
Plugins: None installed

[OdieArbuckle]

It appears this is happening for almost every object viewing: racks, device types, inventory items, front/rear ports,...

[OdieArbuckle]

Really strange, I did have to install the postgres-devel package and python header files, however, apart from that, there wasn't any issue with the upgrade script as far as I can tell...You can login to the application, netbox service seems to be running normally.

I upgraded from v3.7.2 to v4.3.3.

[OdieArbuckle]

System status/config export in json

    "netbox_release": {
        "version": "4.3.3",
        "edition": "Community",
        "published": "2025-06-26T00:00:00",
        "designation": null,
        "build": null,
        "features": {
            "commercial": false,
            "help_center": false
        }
    },
    "django_version": "5.2.3",
    "python_version": "3.12.10",
    "postgresql_version": "PostgreSQL 15.13 on x86_64-pc-linux-gnu, compiled by gcc",
    "database_name": "netbox",
    "database_size": "122 MB",
    "rq_worker_count": 1,
    "plugins": [],
    "config": {
        "ALLOWED_URL_SCHEMES": [
            "file",
            "ftp",
            "ftps",
            "http",
            "https",
            "irc",
            "mailto",
            "sftp",
            "ssh",
            "tel",
            "telnet",
            "tftp",
            "vnc",
            "xmpp"
        ],
        "BANNER_BOTTOM": "",
        "BANNER_LOGIN": "",
        "BANNER_MAINTENANCE": "NetBox is currently in maintenance mode. Functionality may be limited.",
        "BANNER_TOP": "",
        "CHANGELOG_RETENTION": 0,
        "CUSTOM_VALIDATORS": {},
        "DEFAULT_USER_PREFERENCES": {},
        "ENFORCE_GLOBAL_UNIQUE": true,
        "GRAPHQL_ENABLED": true,
        "JOB_RETENTION": 90,
        "MAINTENANCE_MODE": false,
        "MAPS_URL": "https://maps.google.com/?q=",
        "MAX_PAGE_SIZE": 1000,
        "PAGINATE_COUNT": 50,
        "POWERFEED_DEFAULT_AMPERAGE": 16,
        "POWERFEED_DEFAULT_MAX_UTILIZATION": 32,
        "POWERFEED_DEFAULT_VOLTAGE": 229,
        "PREFER_IPV4": false,
        "PROTECTION_RULES": {},
        "RACK_ELEVATION_DEFAULT_UNIT_HEIGHT": 22,
        "RACK_ELEVATION_DEFAULT_UNIT_WIDTH": 220
    }
}

[arthanson]

@OdieArbuckle That is strange and we are not seeing that behavior. The template does not exist sounds like a there are some missing template files possibly which would point to either files missing or a configuration issue. I would suggest closing this an opening this up as a discussion as it would be to a wider audience and get more suggestions on potential ways to track this down.

The template is question that you posted is django/forms/widgets/number.html which points to a django installation issue or path issue, maybe try re-installing django and see if that helps.

[mjpereira602]

@OdieArbuckle Did you upgrade 3.7.2 -> 3.7.8 -> 4.3.3 or did you try to go directly from 3.7.2 -> 4.3.3 ? The latter is not supposed to work.

[OdieArbuckle]

@mjpereira602 ,
I'm afraid I upgraded from v3.7.2 to v4.3.3 directly. To be honest I checked the requirements for the core applications such as python, redis etc but didn't read ALL the release notes. Furthermore, the official upgrade guide doesn't actually state any issue upgrading from 3.x to 4.x.

Might be a plan to have like a linked page to the release notes each time something "breaks" your application, I guess?

Do I have any options for fixing this in place? Instead of restoring a backup and upgrading to v3.7.8 first?

[mjpereira602]

@OdieArbuckle Upgrading between major versions is documented here https://github.com/netbox-community/netbox/blob/main/docs/installation/upgrading.md .

I'm just a user not a developer but I think you're going to have to restore and step migrate.

[jeremystretch]

I'm afraid I upgraded from v3.7.2 to v4.3.3 directly

Upgrading from v3.7 to any v4.x release is supported.

[OdieArbuckle]

@jeremystretch that would 've been my understanding too.
It's unclear to me whether is this a bug now or due to another dependency on my particular system distro.(RHEL8) As far as I can tell, the upgrade script ran fine. Before that, I had 1 or 2 packages which needed to be installed like postgres-devel and python headers but that was about it. I can logon to netbox and the services status seem all good too. Don't really know what to check next, I guess opening it as a discussion might help as I've seen some very similar Django related errors pop up in the past.

[jeremystretch]

I suggest you try re-installing NetBox and re-running the upgrade script to ensure NetBox and all its dependencies are installed correctly. Beyond that it's going to be difficult to determine what went wrong.

[OdieArbuckle]

I'm restoring to a previous backup before the upgrade, so let's close this discussion. It remains strange indeed.