I love your parallel between car maintenance and coding, and I have repeated it many times myself. I think changing a tire is a reasonable thing to expect every driver to be able to do. Likewise, I think understanding SSL errors is the kind of thing every computer user should be able to do. Not code, necessarily, but understand something about this system you trust with most of your life.
Understanding that the computer is a stupid, un-magical machine which obeys only (and exactly!) the instructions you give it is somewhat of a prerequisite for successfully writing computer programs. (Not exactly true, but it's very helpful.)
Understanding that the computer is non-magical also means that your computer users may be more likely to understand how to troubleshoot errors ("Was it something I did, or something out of my control?").
Coding doesn't teach you that. I have programmers that write commercial software opening tickets to change their shell prompt, or to enable VNC on a Linux build server because they 'can't be expected to learn how these systems work, they're programmers.'
What you want people to learn is basic system maintenance and troubleshooting.
It helps a lot in a general sense, being able to reason through how a system might work can give you a lot more confidence in figuring out where to start on a problem.
Of course when it comes to very specific issues it is always nice to have the luxury of opening a ticket and letting somebody who can do it 1/10th the time fix it for you.
