I don’t upgrade very often so I don’t have the actual version where it broke - They worked a couple of weeks ago, but I have since upgraded 2 servers and migrated 1 other server and they all produce the same problem.
If I open a new tab and log into librenms, I can then go back to my custom dashboard server and refresh and the graph appears. But if I log out librenms it will go back to producing the error.
I found an old test install that is running
22.4.0-24-gc3cf52730
and it works as expected. Is there anyway for me to step through the release versions to see where it breaks? Doing this via git clone/pull (only familiar with the very basics of git)?
I know I might have to fix/update some dependencies manually after doing this.
You could use git bisect to find what commit broke it. If you are on latest commit you can do something like:
$ git bisect start
$ git bisect bad
$ git bisect good 22.4.0
Which will basically checkout a commit and ask you if it’s good or bad (working or broken)
You reply with git bisect good or git bisect bad until there is no commit left to test.