When I checked your site, it showed using LetsEncrypt for certs. In their recommendations, once cert files are acquired and site is responding, they recommend setting up a redirect so that any request ... http:// or https:// headed to your site is automagically changed to https://.
That's an extremely good idea these days considering more and more attacks via web are on the rise. Many site providers now offer a CDN (CloudFlare) which is both for caching and for protection. Many strongly suggest setting up a WAF (web application firewall) like mod_security that sits in front of any web based application ... WordPress, Joomla, and even Moodles could use the 'extra protection'.
Would strongly suggest *NOT* using option https for login only ... make your site 100% https and be done with it.
The httpsreplace tool I think was designed for moodle sites that had originally been set up using http:// ... there fore all *internal* links inside of Moodle would use the CFG variable for the site (http://youresite/ to build/concactate ALL internal links. The search then, if site was functioning as http://site/ should have been search for 'http://yoursite/' ... note the protocol in front and the 'trailing slash'. Replace with 'https://yoursite/' ... again ... note the protocol in front and the 'trailing slash'.
And a caution ... before your next attempt, make sure you have an SQL dump - date/time stamp the sql dump file names if site is functioning as http://. You could in-advertently have a messed up sql dump and restoring it could complicate the issue. Such that your ONLY alternative is to use a true text editor ... NOT Word or other like it ... but a *true* text editor (like nano on CentOS) to search for all links 'http://site/' and replace with 'https://site/' ... then use that raw edited sql file to import into a new DB for the moodle.
My $100.00 tip!
'SoS', Ken