No logs + no query timeline usually points to a service initialization failure or a config incompatibility introduced in 4.4.6 — check if any config file format changed between versions, even a small schema difference can silently kill the logging pipeline.
If you need 4.3.26 specifically, it’s worth checking the official release archive or GitHub tags — many projects keep older binaries available. If not publicly hosted, Docker Hub sometimes has legacy image tags still available.
Before downgrading fully, try clearing cache and resetting to default config on 4.4.6 — sometimes a corrupted config from a previous version carries over and causes silent failures on upgrade. Driving Directions
It’s also worth opening a bug report with your environment details — silent failure with zero logs is exactly the kind of issue maintainers need to know about.
