Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[BUG] Fails to start after update

Open
#68 3 comments 0 reactions 1 assignee View on GitHub

@alex-phillips is already working on this.

Since May 19, 2025.

Assessment

This issue has not been assessed yet.

Description

work-in-progress
Is there an existing issue for this?
  • I have searched the existing issues
Current Behavior

I just tried updating from v4.1.11-ls249 to v4.2.0-ls250 and I get a bunch of errors and can't access Netbox. I can revert back to the older image and it starts right up.

Expected Behavior

No response

Steps To Reproduce
  1. Change compose file to point to v4.2.0-ls250 image.
  2. Re-pull and deploy containers
Environment
- OS: Docker on Ubuntu
- How docker service was installed: apt
CPU architecture

x86-64

Docker creation
version: "3.7"
services:
  db:
    image: postgres:15-alpine
    restart: unless-stopped
    volumes:
      - db-data:/var/lib/postgresql/data
    environment:
      - POSTGRES_PASSWORD=${POSTGRES_PASSWORD}
      - POSTGRES_DB=netbox
      - POSTGRES_USER=netbox

  redis:
    image: redis:7-alpine
    command: redis-server
    restart: always
    volumes:
      - redis-data:/data

  app:
    image: lscr.io/linuxserver/netbox:v4.2.0-ls250
    container_name: netbox
    environment:
      - TZ=America/Chicago
      - SUPERUSER_EMAIL=${SUPERUSER_EMAIL}
      - SUPERUSER_PASSWORD=${SUPERUSER_PASSWORD}
      - ALLOWED_HOST=${DOMAIN}
      - DB_NAME=netbox
      - DB_USER=netbox
      - DB_PASSWORD=${POSTGRES_PASSWORD}
      - DB_HOST=db
      - DB_PORT=5432
      - REDIS_HOST=redis
      - REDIS_PORT=6379
      - REDIS_DB_TASK=0 # Database ID for tasks
      - REDIS_DB_CACHE=1 # Database ID for cache
      - REMOTE_AUTH_BACKEND='netbox.authentication.LDAPBackend'
      - REMOTE_AUTH_HEADER='HTTP_REMOTE_USER'
      - REMOTE_AUTH_AUTO_CREATE_USER=True
    volumes:
      - app-data:/config
      - app-requirements:/app/netbox
    ports:
      - 13031:8000
    depends_on:
      - db
      - redis
    restart: unless-stopped

volumes:
  db-data:
    driver: local
  app-data:
    driver: local
  app-requirements:
    driver: local
  redis-data:
    driver: local
Container logs
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/lsiopy/lib/python3.12/site-packages/django/core/handlers/wsgi.py", line 124, in __call__
    response = self.get_response(request)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lsiopy/lib/python3.12/site-packages/django/core/handlers/base.py", line 140, in get_response
    response = self._middleware_chain(request)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lsiopy/lib/python3.12/site-packages/django/core/handlers/exception.py", line 57, in inner
    response = response_for_exception(request, exc)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lsiopy/lib/python3.12/site-packages/django/core/handlers/exception.py", line 140, in response_for_exception
    response = handle_uncaught_exception(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lsiopy/lib/python3.12/site-packages/django/core/handlers/exception.py", line 184, in handle_uncaught_exception
    callback = resolver.resolve_error_handler(500)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lsiopy/lib/python3.12/site-packages/django/urls/resolvers.py", line 732, in resolve_error_handler
    callback = getattr(self.urlconf_module, "handler%s" % view_type, None)
                       ^^^^^^^^^^^^^^^^^^^
  File "/lsiopy/lib/python3.12/site-packages/django/utils/functional.py", line 47, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
                                         ^^^^^^^^^^^^^^^^^^^
  File "/lsiopy/lib/python3.12/site-packages/django/urls/resolvers.py", line 711, in urlconf_module
    return import_module(self.urlconf_name)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/importlib/__init__.py", line 90, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 999, in exec_module
  File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
  File "/app/netbox/netbox/netbox/urls.py", line 8, in <module>
    from account.views import LoginView, LogoutView
  File "/app/netbox/netbox/account/views.py", line 26, in <module>
    from netbox.views import generic
  File "/app/netbox/netbox/netbox/views/generic/__init__.py", line 2, in <module>
    from .feature_views import *
  File "/app/netbox/netbox/netbox/views/generic/feature_views.py", line 11, in <module>
    from extras import forms, tables
  File "/app/netbox/netbox/extras/forms/__init__.py", line 4, in <module>
    from .bulk_import import *
  File "/app/netbox/netbox/extras/forms/bulk_import.py", line 181, in <module>
    class EventRuleImportForm(NetBoxModelImportForm):
  File "/lsiopy/lib/python3.12/site-packages/django/forms/models.py", line 312, in __new__
    fields = fields_for_model(
             ^^^^^^^^^^^^^^^^^
  File "/lsiopy/lib/python3.12/site-packages/django/forms/models.py", line 207, in fields_for_model
    raise FieldError(
django.core.exceptions.FieldError: 'action_object' cannot be specified for EventRule model form as it is a non-editable field
[pid: 193|app: 0|req: 2/2] 172.19.0.1 () {56 vars in 1108 bytes} [Mon Feb 17 13:41:46 2025] GET /favicon.ico => generated 0 bytes in 63 msecs (HTTP/1.1 500) 0 headers in 0 bytes (0 switches on core 0)
Dominant language
Python
Stars
128
Forks
21
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.