starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Behavior change: After upgrading to 4.x from 3.x Netbox no longer allows unauthenticated GET against http://netbox.host/api/ #9851

New Issue
Closed
opened 2025-12-29 21:23:31 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:23:31 +01:00
Owner
Copy Link

Originally created by @LoneSnowMonkey on GitHub (Jun 15, 2024).

Deployment Type

Self-hosted

NetBox Version

v4.0.5

Python Version

3.10

Steps to Reproduce

curl https://netbox.host/api/

Expected Behavior

A expect to receive a list of various API endpoints. This is the behavior of my 3.7.3 server.

Observed Behavior

On server upgraded from same to 4.0.5 I now get {"detail":"Authentication credentials were not provided."}.

On one hand, it makes sense. On the other, its a change of behavior. This change has resulted in my ansible netbox modules failing since I upgraded to 4.0.5. I reverted to snapshot pending this being sorted out.

This goes pretty deep into the mechanics of things, so I am not sure how/when this 'broke' and what the appropriate resolution is. Should all requests made to Netbox include authentication header, even if it didn't need it in past? Is there something I can tweak in my nginx or a file somewhere in the installation to restore this behavior? I don't know this is beyond my skill and knowledge and I defer to far smarter folks. I have updated a ticket regarding this issue that someone else made on the netbox ansible modules project as well.

Thanks to everyone involved with the Netbox project, it's the beating heart of many things.

Originally created by @LoneSnowMonkey on GitHub (Jun 15, 2024). ### Deployment Type Self-hosted ### NetBox Version v4.0.5 ### Python Version 3.10 ### Steps to Reproduce `curl https://netbox.host/api/` ### Expected Behavior A expect to receive a list of various API endpoints. This is the behavior of my 3.7.3 server. ### Observed Behavior On server upgraded from same to 4.0.5 I now get `{"detail":"Authentication credentials were not provided."}`. On one hand, it makes sense. On the other, its a change of behavior. This change has resulted in my ansible netbox modules failing since I upgraded to 4.0.5. I reverted to snapshot pending this being sorted out. This goes pretty deep into the mechanics of things, so I am not sure how/when this 'broke' and what the appropriate resolution is. Should all requests made to Netbox include authentication header, even if it didn't need it in past? Is there something I can tweak in my nginx or a file somewhere in the installation to restore this behavior? I don't know this is beyond my skill and knowledge and I defer to far smarter folks. I have updated a ticket regarding this issue that someone else made on the netbox ansible modules project as well. Thanks to everyone involved with the Netbox project, it's the beating heart of many things.
adam added the type: bugstatus: duplicate labels 2025-12-29 21:23:31 +01:00
adam closed this issue 2025-12-29 21:23:32 +01:00
adam commented 2025-12-29 21:23:32 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 17, 2024):

Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #16295 for further discussion.

@jeremystretch commented on GitHub (Jun 17, 2024): Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #16295 for further discussion.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: duplicate type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#9851
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?