You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running Netbox in a kubernetes cluster using the netboxcommunity/netbox image, and it's worked well for the last few months. When I tried to upgrade, I started getting "connection refused" errors for Redis. If I roll back to 2.11.9 it works perfectly.
I dug through the changelog and issues, and I see a few mentions of Redis, but I nothing appears to be directly related, but it appears the Redis library has been updated...which might indicate that cert validation is now enabled or something.
I dug around and found the INSECURE_SKIP_TLS_VERIFY setting in netbox, and tried setting it in my k8s environment, but that didn't resolve the issue. After doing some more digging, it looks like possibly the netboxcommunity/netbox image doesn't support setting that environment variable in the configuration file. For now I've rolled back to 2.11.9.
I'm running Netbox in a kubernetes cluster using the netboxcommunity/netbox image, and it's worked well for the last few months. When I tried to upgrade, I started getting "connection refused" errors for Redis. If I roll back to 2.11.9 it works perfectly.
I dug through the changelog and issues, and I see a few mentions of Redis, but I nothing appears to be directly related, but it appears the Redis library has been updated...which might indicate that cert validation is now enabled or something.
I dug around and found the INSECURE_SKIP_TLS_VERIFY setting in netbox, and tried setting it in my k8s environment, but that didn't resolve the issue. After doing some more digging, it looks like possibly the netboxcommunity/netbox image doesn't support setting that environment variable in the configuration file. For now I've rolled back to 2.11.9.
The text was updated successfully, but these errors were encountered: