Server Error

[coffeeman88]

Hi Community! I'm playing with https://demo.netbox.dev/ and whatever module I'm trying to pick I'm always ending with Server Error page and below info message:

A database programming error was detected while processing this request. Common causes include the following:

Database migrations missing. When upgrading to a new NetBox release, the upgrade script must be run to apply any new database migrations. You can run migrations manually by executing python3 manage.py migrate from the command line.

Unsupported PostgreSQL version. Ensure that PostgreSQL version 15 or later is in use. You can check this by connecting to the database using NetBox's credentials and issuing a query for SELECT VERSION().

The complete exception is provided below:

<class 'django.db.utils.ProgrammingError'>

column extras_customfield.status does not exist
LINE 1: ...ted_object_type_id", "extras_customfield"."name", "extras_cu...
^

Python version: 3.12.3
NetBox version: 4.7.0
Plugins:
netbox_demo: 0.5.0
The request which yielded the above error is shown below:

GET https://demo.netbox.dev/dcim/module-types/

If further assistance is required, please post to the NetBox discussion forum on GitHub.e:

Could you please help me overcoming this issue?

Thanks a lot!

Marcin

[goutamadwant]

This error points to a schema mismatch on the demo server, not something you can fix in your browser. NetBox's extras.0144_customfield_status migration adds exactly the extras_customfield.status column named in your traceback. The running application expects it, but the database it queried did not have it.

Because you're using demo.netbox.dev, the migration instructions on the error page are for the demo operator, not for you. They need to check the deployed version's migration state against the database actually used by the web process and complete the upgrade if necessary. Creating a local NetBox installation or changing your account settings won't repair that hosted database.

The contribution guide says the demo is rebuilt nightly, so it's worth retrying after its next rebuild. That isn't a guarantee of recovery; if it persists, the timestamp and exact URL will help the operator correlate the failure.

[coffeeman88]

Thanks for the response, I've created a second account and it worked.