hire a system-admin for better lookup and setup, as i don't know why it is not working for you and where you stuck
As soon as I replicate the error, I expose it here.
I have the error when I configure everything through phpmyadmin, it has its usefulness, so I did it there.
(I did it in other ways too but I was at the point that something had happened and I had to reverse everything.)
At the moment I'm going to prepare a vps for this, if it goes wrong, nothing happens there, because the other day I did it in a production one.
I will indicate step by step what has been done and with screenshots.
I think I can do it myself, I can't specify where I stayed because I made the mistake of doing it in one in production, as soon as I saw that the database was corrupt (and it was because of my mistake to delete some indexes that I shouldn't have deleted) The rush began and I had to reset everything.
I will use the replica with the phpmyadmin tool that it offers, but for example, phpmyadmin does not tell us when to execute START SLAVE, but I will do it that way.
I will expose, point by point, this time if, reached the error I will be able to stop because it will not be in a database in production, it will be its replica but in a test environment.