Do you start debugging by asking what the user is actually trying to build?

This hits way too close to home. I used to give textbook technical answers to client bugs, only to realize later that their entire architecture was completely different from what I assumed.

Giving the technically right solution for the wrong setup just creates more confusion. Now I try to make them explain their whole workflow first before writing a single line of code.

Have you found a good way to steer users away from asking the wrong technical questions in the first place?