Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server Error then login with superuser Account #18314

Closed
deeconwastaken opened this issue Jan 7, 2025 · 7 comments · Fixed by #18315
Closed

Server Error then login with superuser Account #18314

deeconwastaken opened this issue Jan 7, 2025 · 7 comments · Fixed by #18315
Assignees
Labels
severity: high Completely breaks certain functions, or substantially degrades performance application-wide status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@deeconwastaken
Copy link

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

@deeconwastaken deeconwastaken added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Jan 7, 2025
@christianhennen
Copy link

Same here, with any local or LDAP user: #18313

@tobiasge
Copy link
Member

tobiasge commented 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: #18315

@christianhennen
Copy link

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

@TheGuardianLight
Copy link

TheGuardianLight commented Jan 7, 2025

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

@TheGuardianLight
Copy link

How did you manage to avoid this issue ?

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

@hexa2k9
Copy link

hexa2k9 commented 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
        }
    }
    [...]

@deeconwastaken
Copy link
Author

#18313

Looks like it can be fixed by reseting the dashboard

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation severity: high Completely breaks certain functions, or substantially degrades performance application-wide and removed status: needs triage This issue is awaiting triage by a maintainer labels Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity: high Completely breaks certain functions, or substantially degrades performance application-wide status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants