-
-
Notifications
You must be signed in to change notification settings - Fork 918
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
NetBox container 4.1.0 (or newer) SSL crypto error on startup #1349
Comments
similar error certbot/certbot#10044 |
Have a similar issue on one of my hosts, and I'm unsure as to why. I have 1 dev environment and 3 prod environments running the same image. Works on dev, works on 2 prod environments. Third prod environment throws this error, despite the build being identical. EDIT: Builds were not identical. FIPS mode was enabled on the third host throwing the errors, but disabled on the other prod units. Disabling FIPS mode allows the container to start. |
I had a similar issue, but I also loaded some custom ROOT CAs and apparently there was a newline missing when concatenating the certs. Maybe it helps. |
A workaround is to set the environment variable ...
extraEnvs:
- name: OPENSSL_FORCE_FIPS_MODE
value: "0"
worker:
extraEnvs:
- name: OPENSSL_FORCE_FIPS_MODE
value: "0" |
I am also attaching a work in progress Dockerfile that runs rootless NetBox on Rocky Linux 9 (unable to use RHEL UBI since it lacks the |
Huge save for me thank you a bunch for this. |
Current Behavior
I get the following error starting NetBox on docker using tag v4.1.0 or newer (running on Kubernetes). Image tag v4.0.11 or older works without issue.
Expected Behavior
Container successfully runs
Docker Compose Version
kubernetes 1.30.5 helm chart version netbox-5.0.0-beta.139
Azure Linux with FIPS enabled
Docker Version
The git Revision
n/a
The git Status
Startup Command
n/a
NetBox Logs
Content of docker-compose.override.yml
n/a
The text was updated successfully, but these errors were encountered: