Server Error then login with superuser Account #10611

Closed
opened 2025-12-29 21:33:41 +01:00 by adam · 7 comments
Owner

Originally created by @deeconwastaken on GitHub (Jan 7, 2025).

Originally assigned to: @tobiasge on GitHub.

Deployment Type

Self-hosted

Triage priority

N/A

NetBox Version

v4.2.0

Python Version

3.10

Steps to Reproduce

1- Update to v4.2.0
2. Try to login with a superuser account

Expected Behavior

Should be able to login with a superuser account

Observed Behavior

Login with a "normal" useraccount is possible, with a superuser account we get the following error message

Screenshot 2025-01-07 093138

Originally created by @deeconwastaken on GitHub (Jan 7, 2025). Originally assigned to: @tobiasge on GitHub. ### Deployment Type Self-hosted ### Triage priority N/A ### NetBox Version v4.2.0 ### Python Version 3.10 ### Steps to Reproduce 1- Update to v4.2.0 2. Try to login with a superuser account ### Expected Behavior Should be able to login with a superuser account ### Observed Behavior Login with a "normal" useraccount is possible, with a superuser account we get the following error message ![Screenshot 2025-01-07 093138](https://github.com/user-attachments/assets/432575ff-7cf4-4b76-a1b6-993ce4f4f76b)
adam added the type: bugstatus: acceptedseverity: high labels 2025-12-29 21:33:41 +01:00
adam closed this issue 2025-12-29 21:33:41 +01:00
Author
Owner

@christianhennen commented on GitHub (Jan 7, 2025):

Same here, with any local or LDAP user: https://github.com/netbox-community/netbox/discussions/18313

@christianhennen commented on GitHub (Jan 7, 2025): Same here, with any local or LDAP user: https://github.com/netbox-community/netbox/discussions/18313
Author
Owner

@tobiasge commented on GitHub (Jan 7, 2025):

I'm also seeing this error with users from Django Socialauth (Entra ID). I have prepared a PR that should fix the problem: https://github.com/netbox-community/netbox/pull/18315

@tobiasge commented on GitHub (Jan 7, 2025): I'm also seeing this error with users from Django Socialauth (Entra ID). I have prepared a PR that should fix the problem: https://github.com/netbox-community/netbox/pull/18315
Author
Owner

@christianhennen commented on GitHub (Jan 7, 2025):

Jep, when commenting out this line it works again as well.

@christianhennen commented on GitHub (Jan 7, 2025): Jep, when commenting out this line it works again as well.
Author
Owner

@TheGuardianLight commented on GitHub (Jan 7, 2025):

I have the same error. How did you manage to avoid this issue ? (if so)

@TheGuardianLight commented on GitHub (Jan 7, 2025): I have the same error. How did you manage to avoid this issue ? (if so)
Author
Owner

@TheGuardianLight commented on GitHub (Jan 7, 2025):

How did you manage to avoid this issue ?

Nevermind, I just edited widget.py to apply the modification that @tobiasge commited

@TheGuardianLight commented on GitHub (Jan 7, 2025): > How did you manage to avoid this issue ? Nevermind, I just edited widget.py to apply the modification that @tobiasge commited
Author
Owner

@hexa2k9 commented on GitHub (Jan 7, 2025):

Another workaround (I applied this manually to the affected users) is to modify the netbox.public.extras_dashboard table data and include "requires_internet": false on the affected users config Field.

This certainly won't work at scale but the number of users who use feeds on their dashboard was small so it was suitable to do.

The "fixed" content would look like that in my case:

    [...]
    "d2d10a29-a2e5-4d8d-822c-e9d7ef0f812a": {
        "class": "extras.RSSFeedWidget",
        "color": "",
        "title": "Netbox Releases",
        "config": {
            "feed_url": "https://github.com/netbox-community/netbox/releases.atom",
            "max_entries": 3,
            "cache_timeout": 3600,
            "requires_internet": false
        }
    }
    [...]
@hexa2k9 commented on GitHub (Jan 7, 2025): Another workaround (I applied this manually to the affected users) is to modify the `netbox.public.extras_dashboard` table data and include `"requires_internet": false` on the affected users `config` Field. This certainly won't work at scale but the number of users who use feeds on their dashboard was small so it was suitable to do. The "fixed" content would look like that in my case: ```json [...] "d2d10a29-a2e5-4d8d-822c-e9d7ef0f812a": { "class": "extras.RSSFeedWidget", "color": "", "title": "Netbox Releases", "config": { "feed_url": "https://github.com/netbox-community/netbox/releases.atom", "max_entries": 3, "cache_timeout": 3600, "requires_internet": false } } [...] ```
Author
Owner

@deeconwastaken commented on GitHub (Jan 7, 2025):

https://github.com/netbox-community/netbox/discussions/18313

Looks like it can be fixed by reseting the dashboard

@deeconwastaken commented on GitHub (Jan 7, 2025): [https://github.com/netbox-community/netbox/discussions/18313](https://github.com/netbox-community/netbox/discussions/18313) Looks like it can be fixed by reseting the dashboard
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#10611