Netbox does not connect to DB, no indication what is wrong #17804
-
Deployment TypeSelf-hosted Triage priorityN/A NetBox Versionv4.1.4 Python Version3.12 Steps to ReproduceI deploy netbox on kubernetes using the community helm chart 5.0.0-beta.128. It does not start and stuck in Enabled debugging, which shows the detailed stack. We are using an external redis and postgresdb but the stack does not indicate whether it's an issue with the connection or authentication or whatever... Expected BehaviorNo Error Observed Behavior
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
what plugins are you using? disable them one by one in requirement.txt and you can see which plugin caused the issue. |
Beta Was this translation helpful? Give feedback.
-
It looks like you have truncated the traceback, so you haven't shown the actual exception at the end. However, given these lines:
I would guess that the problem is down to how you've set HTTP_PROXIES in your configuration.py. This is a docker deployment so configuration.py is heavily customized - see here. There was a pull request in that area a few months ago. |
Beta Was this translation helpful? Give feedback.
[EDIT to replace what I wrote before]
It looks like netbox-chart completely replaces the configuration.py that netbox-docker provides, and injects settings like HTTP_PROXIES into a YAML file that it picks up.
So you should be able to use