It took me longer to learn Clojure than any other programming language, and I’d had a little Lisp experience beforehand (a gateway, of sorts, I guess).
I learn well from books and started with the Joy of Clojure, which might not be a good first book, but it kept my interest up to continue going deeper and deeper. But what really helped it click was doing almost all of the 4Clojure exercises (now at https://4clojure.oxal.org/)… and then doing them again. The second time through I was amazed at how much I’d learned – the solutions tended to be shorter, more functional… more beautiful. Looking at other solutions can help. As other respondents said, the functional paradigm shift is hard to get your head around, but once it gels, it changes everything.
Your mileage may certainly vary. One more aspect is using Clojure for professional development. Having gotten hooked on the language, I did somewhat of a career pivot and did eight years of professional Clojure development. It was a decidedly mixed bag (mostly because of the local corporate microclimates involved) and I’m currently taking a break from professional Clojure development, though I still use it for creative/hobby projects.
I offer that last bit of context because sometimes it’s not the language or the tooling but the environment that is getting in the way of learning and enthusiasm. I will say that, as a senior contributor, having one or two developers skilled enough to challenge you and to learn from can also be energizing (I’m looking at you, Ted 
).
Best of luck to you!