The biggest issue with being a freelancing “back-end only” developer is that means whoever is hiring you will either have an existing project that needs updating in a specific place, or they will need to hire another person to handle the front-end while you work on the back-end.
Neither of which cases seems common or makes much sense business wise when you could just get a single “full-stack” person that does everything, even if they are worse at both ends.
There are also lots of jobs that are mostly only front-end (say build a static site for someone’s business, nothing fancy) which means freelancing in that realm is possible due to more jobs. This is less true for back-end work, which just turns more into “non-front-end related software development”.
Freelancing as a back-end dev, probably leans more into consulting where you are more of an “expert” that can get hired for a given project+company and work on that project for a while, effectively as an employee.
Regardless, as @kevinSmith said above, you gotta know your stuff, as the realm of back-end is inherently more risky as its job is to act as a “secure environment”. If you screw up security in some way, you could open up the application and your user’s data to attack. The front-end always has the back-end to act as the “last line of defense”. If the back-end gets compromised in any way or form, your basically screwed.
If you enjoy working on the back-end, then I suggest continue learning it but don’t focus on freelancing. Rather focus on getting a job at a company where you can do that work. Its less risk, means you get more training and back-up and can focus on the part you want to work in.
The front-end might be “flashy and cool”, but really its a single specific (popular) domain. Everything else can be “back-end”. From web servers, to operations, to systems, to cloud providers, to machine learning, etc etc, its all “back-end”.
Good luck, keep learning, keep building