As for advice, find a company hiring for full stack engineers and bill yourself as someone able to learn on the backend. The company also has to be one willing to take that chance. Do not get sucked into the debates of x vs y language, and be willing to adapt to what you're working with. If your credentials are strong, you may have more wiggle room to be opinionated.
Edit: Just to add, I also transitioned from frontend to fullstack, although now I'm in the hybrid land of engineering management with coding being a bonus tool for assisting with management. My company has helped multiple engineers with primarily frontend experience transition to fullstack work (or in the case of some, even exclusively backend work). I honestly think it's not worth fussing about languages, as those can be learned - even SQL. Understand your fundamentals, and make sure you present yourself as a flexible person willing to put in the time and effort to learn and you will likely succeed in a transition.
Also I recommend avoiding being desperate to switch when job searching in such a transition - few things smell worse than the stench of desperation, which will affect your pay & negotiating wiggle room.
And also, how much it will take to achieve some decent level (to be able to work as a middle dev)? I think with Python 1year should be fine, what about .Net?
Achieving an intermediate skill set in any language/platform will certainly take more than a year. The language itself takes very little time - but picking up maintainable (Clean Code, Pragmattic Programmer, etc) habits takes a good bit longer for most people. Python probably has more beginner resources available thanks to MOOCs and the like, but there's plenty of .NET intro sources as well.
But yeah, in terms of stable and proven solutions it is extremely safe place.
The differences between frontend & backend: frontend code tends to be more loosey-goosey, less robust. Generally the goal of the frontend coder is to write lots of features in a short amount of time. Backend development is more "slow", you still want lots of features, but they need to be robust and work correctly 99.99% of the time.
For that reason, I think the best way to think like a backend developer is pick a language that doesn't have dynamic objects (like Python). I'm not saying that Python can't work, I'm saying that using a static-type language will help you outgrow any sloppy thinking habits that people tend to get when they spend too much time in Javascript.
Hiring wise, Java is still a very in-demand skill. Tech wise, Java is an extremely stable and proven platform that will serve any project well. It's "boring" technology (which is a good thing). If you really want to change your thinking, then try to stop gravitating towards shiny things and instead use a "boring" platform.