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

Error IPV6 launch Netbox version v3.4.1 #7487

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

Originally created by @chrisho95 on GitHub (Jan 10, 2023).

NetBox version

v3.4.1

Python version

3.10

Steps to Reproduce

When I launch Netbox version 3.4.1 with docker-compose, I have the following error coming up.

2023/01/10 13:50:17 [notice] 7#7 process 14 exited with code 0
2023/01/10 13:50:17 [info] 16#16 router started
2023/01/10 13:50:17 [info] 16#16 OpenSSL 3.0.2 15 Mar 2022, 30000020
âï¸ Applying configuration from /etc/unit/nginx-unit.json
2023/01/10 13:50:18 [alert] 7#7 socket("[::]:8080") failed (97: Address family not supported by protocol)
2023/01/10 13:50:18 [alert] 16#16 failed to apply new conf
â ï¸ Could no load Unit configuration
2023/01/10 13:50:18 [notice] 7#7 process 12 exited with code 1
2023/01/10 13:50:18 [notice] 7#7 process 15 exited with code 0
2023/01/10 13:50:18 [notice] 7#7 process 16 exited with code 0

The "nginx-unit.json" file has a new session in the file:

"listeners": {
"0.0.0.0:8080": {
"pass": "routes"
},
"[::]:8080": {
"pass": "routes"
}
},

When I remove the IPV6 part, Netbox launches correctly.

"listeners": {
"0.0.0.0:8080": {
"pass": "routes"
}
},

I would like to not use IPV6 IPs but don't modify the file "nginx-unit.json".

BR,

Chris.

Expected Behavior

The launch of netbox is going well.

Observed Behavior

2023/01/10 13:50:17 [notice] 7#7 process 14 exited with code 0
2023/01/10 13:50:17 [info] 16#16 router started
2023/01/10 13:50:17 [info] 16#16 OpenSSL 3.0.2 15 Mar 2022, 30000020
âï¸ Applying configuration from /etc/unit/nginx-unit.json
2023/01/10 13:50:18 [alert] 7#7 socket("[::]:8080") failed (97: Address family not supported by protocol)
2023/01/10 13:50:18 [alert] 16#16 failed to apply new conf
â ï¸ Could no load Unit configuration
2023/01/10 13:50:18 [notice] 7#7 process 12 exited with code 1
2023/01/10 13:50:18 [notice] 7#7 process 15 exited with code 0
2023/01/10 13:50:18 [notice] 7#7 process 16 exited with code 0

Originally created by @chrisho95 on GitHub (Jan 10, 2023). ### NetBox version v3.4.1 ### Python version 3.10 ### Steps to Reproduce When I launch Netbox version 3.4.1 with docker-compose, I have the following error coming up. 2023/01/10 13:50:17 [notice] 7#7 process 14 exited with code 0 2023/01/10 13:50:17 [info] 16#16 router started 2023/01/10 13:50:17 [info] 16#16 OpenSSL 3.0.2 15 Mar 2022, 30000020 âï¸ Applying configuration from /etc/unit/nginx-unit.json **2023/01/10 13:50:18 [alert] 7#7 socket(\"[::]:8080\") failed (97: Address family not supported by protocol)** 2023/01/10 13:50:18 [alert] 16#16 failed to apply new conf â ï¸ Could no load Unit configuration 2023/01/10 13:50:18 [notice] 7#7 process 12 exited with code 1 2023/01/10 13:50:18 [notice] 7#7 process 15 exited with code 0 2023/01/10 13:50:18 [notice] 7#7 process 16 exited with code 0 The "nginx-unit.json" file has a new session in the file: **"listeners": { "0.0.0.0:8080": { "pass": "routes" }, "[::]:8080": { "pass": "routes" } },** When I remove the IPV6 part, Netbox launches correctly. **"listeners": { "0.0.0.0:8080": { "pass": "routes" } },** I would like to not use IPV6 IPs but don't modify the file "nginx-unit.json". BR, Chris. ### Expected Behavior The launch of netbox is going well. ### Observed Behavior 2023/01/10 13:50:17 [notice] 7#7 process 14 exited with code 0 2023/01/10 13:50:17 [info] 16#16 router started 2023/01/10 13:50:17 [info] 16#16 OpenSSL 3.0.2 15 Mar 2022, 30000020 âï¸ Applying configuration from /etc/unit/nginx-unit.json **2023/01/10 13:50:18 [alert] 7#7 socket(\"[::]:8080\") failed (97: Address family not supported by protocol)** 2023/01/10 13:50:18 [alert] 16#16 failed to apply new conf â ï¸ Could no load Unit configuration 2023/01/10 13:50:18 [notice] 7#7 process 12 exited with code 1 2023/01/10 13:50:18 [notice] 7#7 process 15 exited with code 0 2023/01/10 13:50:18 [notice] 7#7 process 16 exited with code 0
adam closed this issue 2025-12-29 20:24:01 +01:00
adam commented 2025-12-29 20:24:02 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Jan 10, 2023):

Please check the netbox-docker repo instead.

https://github.com/netbox-community/netbox-docker

@kkthxbye-code commented on GitHub (Jan 10, 2023): Please check the netbox-docker repo instead. https://github.com/netbox-community/netbox-docker
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
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#7487
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?